An encouraging note beforehand: this is not difficult AT ALL -- "other stuff" (e.g. to learn what I needed) took me WAY longer than getting everything up and running.

Thus, it is all summarized here for your convenience, in case you don't have a dependable connection or the time to keep jumping from site to site to gather every necessary bit of information and try out every release or beta of every tool out there. If you stick to the stuff I link, you should have no problems.

Building on OS/2-based platforms

(Without modifying a thing in the sources as they were in December 2017)

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 January 2022, 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/. You can find a newer v2.0 betas ​here at Netlabs. Both 1.9 and 2.0 beta 1 worked for me (newer betas I haven't tested). This builds the EXE files.
• ​PMPrintF at %PMPRINTFDIR% or the default U:\PMPrintF. This aids with debugging the EXEs as you play witht the sources. As of 2022, I am still using v96.254 by Andreas Buchinger from 2017.
• A working Perl environment. I installed mine, a RPM packaged version, with ​ANPM. This will create .map files for the EXEs for debugging.
• IBM MapSym Version 4 (Symbol File Generator, 2001) from some OS/2 Toolkit (e.g. in eCS CD2). Will create .sym files for kernel debugging.
• MapXQS from ​ExceptQ 7.1+ by Steven H. Levine. This will create .XQS files from the .map ones to further help debugging.
• Steve's LxLite 1.35 from the same place. This will cut the size of linear OS/2 EXE (LX) files roughly in half. Our friends at ​BitWise Works GmbH also have a ​RPM-packaged, newer one that "has fixes included from several places (inluding all Steven fixes)". The latter should be installable via yum/rpm or ANPM.

It might be possible to build eFTE2 with other or newer tools, but I'd rather devote time to Get Shit Done™ first. 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.

How to mix

Once you have all of the above, the process is as simple as ChDiring to trunk/src in your local copy of the SVN source, and issuing the Open Watcomm command "wmake". This defaults to the first target in the makefile, which will generate efte.exe (the VIO executable), and eftepm.exe (the PM version), along with their .sym, .map, and .xqs symbol files.

You can build either of them individually with "wmake efte.exe" or "wmake eftepm.exe".

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, then build others ;)