You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,12 @@
2
2
3
3
## This fork
4
4
5
-
I'm trying to faithfully rebuild the original, cleaning up the tree, removing and re-generating as many of the generated files as possible.
5
+
I'm trying to produce a working build close to the original, without changing anything apart
6
+
from fixing severe bugs that would prevent it from running. The source tree is supposed to
7
+
contain just the files required for the build, while everything that can be generated at
8
+
build time, will be, as opposed to carrying the pre-processed intermediate files in the
9
+
repository. Also, the pre-processing and code generation tools themselves should be built
10
+
from source.
6
11
7
12
Used build tools:
8
13
@@ -13,7 +18,15 @@ Used build tools:
13
18
* pklite 1.15
14
19
15
20
### Status
16
-
This builds a combined, packed and obfuscated executable similar to the original. A full run of the demo works fine. However, it seems that the released source code is in an earlier state than the final release. Non-essential features like specifying on the command line where to start running or even prematurely exiting in response to a key press do not work as reliably as in the real release.
21
+
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.
17
27
18
28
### How to build
19
-
Use nmake on the top-level makefile. No sane dependency tracking is in place, so always rebuilding from a clean working directory is the way to go. I build under Windows XP which seems to leak DOS memory. I have to restart the build three times to have it complete.
29
+
30
+
Use nmake on the top-level makefile. No sane dependency tracking is in place, so always
31
+
rebuilding from a clean working directory is the way to go. I build under Windows XP, which
32
+
seems to leak DOS memory. I have to restart the build twice to have it complete.
0 commit comments