@@ -9,6 +9,12 @@ build time, will be, as opposed to carrying the pre-processed intermediate files
9
9
repository. Also, the pre-processing and code generation tools themselves should be built
10
10
from source.
11
11
12
+ This builds a combined, packed and obfuscated executable similar to the original. A full run
13
+ of the demo works fine. However, it seems that the released source code is in an earlier
14
+ state than the final release. Non-essential features like specifying on the command line
15
+ where to start running or even prematurely exiting in response to a key press do not work as
16
+ reliably as in the real release.
17
+
12
18
Used build tools:
13
19
14
20
* Borland C++ 3.1
@@ -19,11 +25,11 @@ Used build tools:
19
25
20
26
### Status
21
27
22
- This builds a combined, packed and obfuscated executable similar to the original . A full run
23
- of the demo works fine. However, it seems that the released source code is in an earlier
24
- state than the final release. Non-essential features like specifying on the command line
25
- where to start running or even prematurely exiting in response to a key press do not work as
26
- reliably as in the real release .
28
+ I believe that there are no unused source files left in the tree . A few binary executables
29
+ are still left over, of which at least some had their source code in the repo previously. In
30
+ addition, there used to be extensive tooling and original data for the visu project (the 3D
31
+ scenes). It might be possible to generate the binary data files from these, and I might try
32
+ to tackle this project in the future .
27
33
28
34
### How to build
29
35
0 commit comments