Cleanup Watcom compilation, setup, as recommended by @jmalak, and remove old sarcastic remarks that have outlived their usefulness.

[jmalak]

Please what is purpose of linux-ow.sh and owenv.sh script files?
I don't understand why it has complete messy INCLUDE environment variable.
Why OW tools setup is for 32-bit Windows if you compile for different targets?
It results in following wrong message in shell scripts

"# why is this even necessary? why does dumbshit Watcom insist on including the WINNT headers for Windows 3.1 builds?"

It is caused by previous wrong OW setup.
in other files <os>_INCLUDE variables are used and wrongly combined with INCLUDE variable.

Such OW setup can cause some hiden mistakes etc.

You should handle cross-compilation one way only, don't mix multiple mechanism.

• full handling by <os>_INCLUDE and INCLUDE variables
• full handling by command line -I option

By example OW build system is fully cross-compilation system and it uses "full handling by command line -I options" for flexibility.
It requires to ignore all ..INCLUDE variables, it is ensured by using -x compiler option.
I thing for your project you could use aproach with <os>_INCLUDE and INCLUDE variables

[joncampbell123]

That's a mess from 10+ years ago that probably needs to be cleaned up, yes.

All I cared about when I started DOSLIB in 2008 was making it work, not necessarily cleanly. The makefile system eventually came around through hacks in it's current form by 2012.

[joncampbell123]

At the time I had Open Watcom 1.8, then Open Watcom 1.9.

[joncampbell123]

My primary development environment with Open Watcom is on 64-bit Linux. It was on 32-bit Linux when I started, but I eventually made the jump to 64-bit and stuck with it.

[jmalak]

I understand, but this cross-compilation stuff is-not changed by OW any way.
It is same as for WATCOM 11.x

[jmalak]

generaly you should have configured OW for host system and next switch compilation anvironment for target system appropriate way

[joncampbell123]

linux-ow.sh was made so that DOSLIB can compile without having to first source the Watcom environment script.

owenv.sh was made for @sparky4 so that "Project 16" can use DOSLIB as well.

[jmalak]

I am involving into it due to @sparky4 has repeated problems with building by OW
I can prepare some fix to handle it proper way for your review

[joncampbell123]

@jmalak Sounds good to me. I'll remove the sarcastic remarks on my end.

[jmalak]

no problem with notes, we need to fix source of problem

[jmalak]

I think that linux-ow.sh can be removed at all
Only proper setup of OW for host is necessary before start of doslib build

[joncampbell123]

linux-ow is not just the OW environment, it also contains the build target list handling.

There are also functions in there to locate a 32-bit GCC 7.1.0 for an experimental project to compile Windows 3.1 .386 / .VXD drivers using GCC + wlink.

[joncampbell123]

However if you mean the script code to set WATCOM variables should be removed, I'm fine with that.

[jmalak]

then name is little confusing

[joncampbell123]

There are also stubs in linux-ow.sh from long ago when I allowed the compile steps to ALSO regenerate BAT files that could be used to compile DOSLIB from a pure MS-DOS system directly. Those were hard to maintain so they were removed.