Version 4 (modified by 7 years ago) ( diff ) | ,
---|
Building on OS/2-based platforms
(Without modifying a thing in the sources as of 2017-12)
Ingredients
To build eFTE2 on ArcaOS, OS/2, or eCS you will need:
- A subversion client. Paul Smedley's SVN port, still at version 1.7.21 as of December 2017, works for me.
- The source code for eFTE2. It is available here at Netlabs
- Some text editor. I use eFTE2 itself.
- Open Watcom 1.9 or newer. Check http://www.openwatcom.org/. We have a newer beta here at Netlabs. This builds the EXE files.
- PMPrintF at %PMPRINTFDIR% or the default U:\PMPrintF. This adds some debugging stuff to the EXEs.
- A working Perl environment. I installed mine, a RPM packaged version, with ANPM. This will create .map files for the EXEs.
- MapXQS from ExceptQ 7.1 by Steven H. Levine. This will create .XQS files from the .map ones to further help debugging.
- LxLite from the same place, or Hobbes (but I use Steve's one for this project). This will cute the size of linear OS/2 EXE (LX) files roughly in half.
It might be possible to build eFTE2 with other tools, but I'd rather devote time to Get Shit Done™. The Perl requirement almost drove me off, for reasons unrelated to this project. Contact me through the mailing list and we can find out together.
What to do
Once you have all of the above up and running, the process is as simple as ChDiring to trunk/src in your local copy of the SVN source, and issuing the command "wmake". This defaults to the first target in the makefile, which will generate efte.exe, and eftepm.exe, along with their .map and .xqs symbol files.
Or you can start fiddling with your makefile, other targets, etc.
Building on other platforms (Win32)
This is work in progress. To be updated as I find out myself -- I would rather get one version running as I need to first ;)