cc147f79e4
There is no reason to not use an archive manager to build our executables. If there really are systems which don't have any kind of archive manager, we can simply link all the objects. This also drops any use of configure to detect library objects. Instead just use HAVE_* and let the archive manager delete them. A lot of additional functions could be declared library functions and reorganized. ***FIX*** Mkfiles/*.mak have not yet been updated. Signed-off-by: H. Peter Anvin <hpa@zytor.com> |
||
---|---|---|
.. | ||
msvc.mak | ||
netware.mak | ||
openwcom.mak | ||
owlinux.mak | ||
README |
These are pre-created Makefiles for various platforms, use them if GNU autoconf/automake packages are not supported on your system. The Makefiles are: Filename Target Compiler Tested with --------------------------------------------------------------------------- msvc.mak Win32 MS Visual C++ Visual C++ Express 2005 For building on a Win32 host using Microsoft Visual C++. Usage: nmake /f Mkfiles/msvc.mak Filename Target Compiler Tested with --------------------------------------------------------------------------- openwcom.mak DOS,Win32,OS/2 OpenWatcom C OpenWatcom 1.7 (Win32) For building on a DOS, OS/2 or Win32 host using OpenWatcom. OpenWatcom can be downloaded from http://www.openwatcom.org/. Usage: wmake /f Mkfiles/<filename> <target> <target> is dos, win32, or os2. Filename Target Compiler Tested with --------------------------------------------------------------------------- owlinux.mak DOS,Win32,OS/2 OpenWatcom C OpenWatcom 1.6rc2 (Linux) For building on a Linux host using OpenWatcom for Linux. Usage: make -f Mkfiles/<filename> <target> <target> is dos, win32, or os2. Filename Target Compiler Tested with --------------------------------------------------------------------------- netware.mak NetWare Cross-GCC Cross-GCC 3.2.3 (Linux, Win32) For building on a Linux or Win32 host using Cross-GCC for Linux/Win32. Usage: make -f Mkfiles/netware.mak