Subj : how to
To   : Kai Richter
From : andrew clarke
Date : Fri Feb 05 2021 19:16:06

05 Feb 21 06:58, you wrote to Michael Pierce:

 KR> The entry point is the huskybse modul. The README is outdated.

 KR> https://github.com/huskyproject/huskybse/blob/master/README

 KR> But you will find useful information like a list of supported compilers
 KR> in

 KR> https://github.com/huskyproject/huskybse/blob/master/README.Makefiles

 KR> OS/2        EMX             makefile.emo
 KR> OS/2        EMX             makefile.emx
 KR> OS/2        IBM CSet        makefile.ibo
 KR> OS/2        Watcom C        makefile.wco
 KR> OS/2        High C          makefile.hco
 KR> OS/2        Borland C       makefile.bco

 KR> If your compiler doesn't work try another. ;-)

Most if not all of these makefiles are broken due to neglect.

It's a bit unfair to send users on a long adventure trying to track down which compiler actually successfully builds the project.

Also beware that the installers of older commercial OS/2 compilers (Borland, Metaware & C/Set) have a tendancy to break the boot sequence on OS/2 Warp 4.0 and above due to CONFIG.SYS modifications. The PATH ordering in CONFIG.SYS gets erroneously changed causing much older DLLs (eg. SOM.DLL) to be loaded by the Workplace Shell. This fails because of missing exports (or API changes) in the older DLLs, and the PC gets stuck in a boot loop.

Ideally whoever built this:

http://download.huskyproject.org/os2/husky-all-1.9-os2-libc066-20201211.zip

would chime in and tell us exactly what compiler they're using, and what their build process is.

--- GoldED+/BSD 1.1.5-b20180707
 * Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)

.