This cross environment consists of a set of "tricks" to insulate as
much as possible the ongoing port of KDE to OpenServer from:

  differences between Gnu and SCO compile environments

  changes within the OS itself during its development cycle


Note that the first item appears to be lessening over time, presumably
as the port of KDE to Solaris using the Sun native compiler matures
and influences the main KDE tree.  With the release of OpenServer 6,
the second item is no longer a problem.  So it is very likely this
cross environment will no longer be a part of future releases of KDE.


What are the tricks?

KDE relies on the fact that the Gnu compiler is not so fussy about
using reserved keywords in class member names.  Confusion results when
an SCO include file thinks (correctly) that it may take liberties with
the keyword to do some compatibility magic, but this has a side effect
of a "#define" changing the KDE class member name.  The files in the
"include" directory consist mainly of an #undef for the keyword
(thereby solving the name conflict) and the definition of a
corresponding inline function to do the same task.

There is also a version of xtree that contains explicit char casts in
it to insulate the compiler from wondering about similar qchar
entities from Qt.

The socketpair() definition in socket.h was made to return the same
value as expected on Gnu/Linux.


The CC, cc, and ar commands are filters that massage their input
slightly then call the real version in /usr/ccs/bin. The massaging
consists of:

  - calling the prelinker before linking a program

  - enforcing a consistent RPATH for all binaries

  - add extra "-L dir" constructs for shared libraries called without
    the usual "-l foo" convention.


The cross environment also includes skunkware versions of gmake,
md5sum, and patch (renamed as gnupatch).


