Starting with release 4.0 UWIN source is available for download.
To build UWIN from the source you must first download and install
the UWIN 4.0 (or newer) binary
uwin-base
and
uwin-dev
packages.
Pick a package root directory$PACKAGEROOT.
If you have administrative privileges then
PACKAGEROOT=/usr
will be fine.
Change directory to$PACKAGEROOT
and
download the
uwin
source package tarball into the
lib/package/tgz
directory.
Read the source package:
package read
Build the binaries from the source:
package make
All generated files will be placed in the
INSTALLROOT=$PACKAGEROOT/arch/win32.i386
directory tree.
posix.dll
will be installed in
$INSTALLROOT/sys.
In order to install/sys/posix.dll
from
$INSTALLROOT/sys/posix.dll
you must stop all UWIN processes (e.g., run /etc/stop_uwin).
Also, be sure to save a copy of the previous
posix.dll;
a botched
posix.dll
could potentially and completely disable UWIN.
Once the initialpackage make
completes you can run
nmake(1)
from any subdirectory in the
$INSTALLROOT/src
tree.
package make
essentially sets up the
PACKAGEROOT,
INSTALLROOT,
PATH,
and
VPATH
environment variables and runs
nmake install cc-
from the
$INSTALLROOT/src
directory.
If you want to build just one component:
export VPATH=$INSTALLROOT:$PACKAGEROOT
export CDPATH=:..:$INSTALLROOT/src/cmd:$INSTALLROOT/src/lib:$INSTALLROOT/src/uwin
cd component # e.g., libposix
nmake install # or all or foo.o
Do we think recursive make is harmful?No
-- not if you use the right
make.
nmake(1)
scans the makefiles rooted at the current directory and
determines the proper recursive makefile build order.
Any
ast,
graphviz,
or
ast nmake
based package tarball can be read into
$PACKAGEROOT/src;
the next
nmake
invocation will build the new package components in the proper order.