mirror/nasm
2
0
Fork 0
mirror of https://github.com/netwide-assembler/nasm.git synced 2024-12-27 09:29:06 +08:00
Code Issues Packages Projects Releases Wiki Activity
4b5b737d49
nasm/Mkfiles/openwcom.mak

337 lines
11 KiB
Makefile
Raw Normal View History

Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# -*- makefile -*-
#
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# Makefile for building NASM using OpenWatcom
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
# cross-compile on a DOS/Win32/OS2 platform host
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
#
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
top_srcdir = .
srcdir = .
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
VPATH = $(srcdir)\asm;$(srcdir)\x86;asm;x86;$(srcdir)\macros;macros;$(srcdir)\output;$(srcdir)\lib;$(srcdir)\common;$(srcdir)\stdlib;$(srcdir)\nasmlib;$(srcdir)\disasm
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
prefix = C:\Program Files\NASM
exec_prefix = $(prefix)
bindir = $(prefix)\bin
mandir = $(prefix)\man
CC = *wcl386
DEBUG =
CFLAGS = -zq -6 -ox -wx -ze -fpi $(DEBUG)
BUILD_CFLAGS = $(CFLAGS) $(%TARGET_CFLAGS)
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
INTERNAL_CFLAGS = -I$(srcdir) -I. -I$(srcdir)\include -I$(srcdir)\x86 -Ix86 -I$(srcdir)\asm -Iasm -I$(srcdir)\disasm -I$(srcdir)\output
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
ALL_CFLAGS = $(BUILD_CFLAGS) $(INTERNAL_CFLAGS)
LD = *wlink
LDEBUG =
LDFLAGS = op quiet $(%TARGET_LFLAGS) $(LDEBUG)
LIBS =
STRIP = wstrip
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
Mkfiles: harmonize how perl and (if available) makensis is run Use the same macros to run Perl and makensis across all Makefiles. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:23:31 +08:00
PERL = perl
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
PERLFLAGS = -I$(srcdir)\perllib -I$(srcdir)
Mkfiles: harmonize how perl and (if available) makensis is run Use the same macros to run Perl and makensis across all Makefiles. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:23:31 +08:00
RUNPERL = $(PERL) $(PERLFLAGS)
MAKENSIS = makensis
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# Binary suffixes
O = obj
X = .exe
# WMAKE errors out if a suffix is declared more than once, including
# its own built-in declarations. Thus, we need to explicitly clear the list
# first. Also, WMAKE only allows implicit rules that point "to the left"
# in this list!
.SUFFIXES:
.SUFFIXES: .man .1 .$(O) .i .c
# Needed to find C files anywhere but in the current directory
.c : $(VPATH)
.c.$(O):
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
@set INCLUDE=
$(CC) -c $(ALL_CFLAGS) -fo=$^@ $[@
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
syncfiles: use #-- ... --# for consistency with mkdep.pl mkdep.pl already used #-- ... --# (two dashes) whereas syncfiles.pl was using #--- ... ---# (three dashes). Change syncfiles.pl to match mkdep.pl.
2008-06-16 14:50:50 +08:00
#-- Begin File Lists --#
Script to automagically synchronize the object file lists Add a script to automagically synchronize the list of object files between the various Makefiles.
2008-06-16 07:54:29 +08:00
# Edit in Makefile.in, not here!
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
NASM = asm\nasm.$(O)
NDISASM = disasm\ndisasm.$(O)
Makefile: move all non-main objects into libnasm.a There is no fundamental reason for all objects that don't contain a main() function to not be part of libnasm.a; this allows the linker to do its job optimally, especially in the presence of debugging code which may not be needed under normal conditions. If we do end up with function name conflicts the library might have to be split, but it would be better to simply avoid that case. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 10:08:21 +08:00
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
LIBOBJ = stdlib\snprintf.$(O) stdlib\vsnprintf.$(O) stdlib\strlcpy.$(O) &
stdlib\strnlen.$(O) stdlib\strrchrnul.$(O) &
Eliminate filename length restrictions, remote ofmt->filename() Get rid of remaining dependencies on FILENAME_MAX, which ought to have been removed a long time ago. Remove ofmt->filename(); all implementations pretty much do the same thing and there is absolutely no reason to duplicate that functionality all over the place. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-12-21 05:33:49 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
nasmlib\ver.$(O) &
nasmlib\crc64.$(O) nasmlib\malloc.$(O) &
nasmlib\md5c.$(O) nasmlib\string.$(O) &
nasmlib\file.$(O) nasmlib\mmap.$(O) nasmlib\ilog2.$(O) &
nasmlib\realpath.$(O) nasmlib\path.$(O) &
nasmlib\filename.$(O) nasmlib\srcfile.$(O) &
nasmlib\zerobuf.$(O) nasmlib\readnum.$(O) nasmlib\bsi.$(O) &
nasmlib\rbtree.$(O) nasmlib\hashtbl.$(O) &
nasmlib\raa.$(O) nasmlib\saa.$(O) &
nasmlib\strlist.$(O) &
nasmlib\perfhash.$(O) nasmlib\badenum.$(O) &
Eliminate filename length restrictions, remote ofmt->filename() Get rid of remaining dependencies on FILENAME_MAX, which ought to have been removed a long time ago. Remove ofmt->filename(); all implementations pretty much do the same thing and there is absolutely no reason to duplicate that functionality all over the place. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-12-21 05:33:49 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
common\common.$(O) &
Eliminate filename length restrictions, remote ofmt->filename() Get rid of remaining dependencies on FILENAME_MAX, which ought to have been removed a long time ago. Remove ofmt->filename(); all implementations pretty much do the same thing and there is absolutely no reason to duplicate that functionality all over the place. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-12-21 05:33:49 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
x86\insnsa.$(O) x86\insnsb.$(O) x86\insnsd.$(O) x86\insnsn.$(O) &
x86\regs.$(O) x86\regvals.$(O) x86\regflags.$(O) x86\regdis.$(O) &
x86\disp8.$(O) x86\iflag.$(O) &
Makefile: move all non-main objects into libnasm.a There is no fundamental reason for all objects that don't contain a main() function to not be part of libnasm.a; this allows the linker to do its job optimally, especially in the presence of debugging code which may not be needed under normal conditions. If we do end up with function name conflicts the library might have to be split, but it would be better to simply avoid that case. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 10:08:21 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
asm\error.$(O) &
asm\float.$(O) &
asm\directiv.$(O) asm\directbl.$(O) &
asm\pragma.$(O) &
asm\assemble.$(O) asm\labels.$(O) asm\parser.$(O) &
asm\preproc.$(O) asm\quote.$(O) asm\pptok.$(O) &
asm\listing.$(O) asm\eval.$(O) asm\exprlib.$(O) asm\exprdump.$(O) &
asm\stdscan.$(O) &
asm\strfunc.$(O) asm\tokhash.$(O) &
asm\segalloc.$(O) &
asm\preproc-nop.$(O) &
asm\rdstrnum.$(O) &
Reorganize the source code into subdirectories Make the source code easier to understand and keep track of by organizing it into subdirectories depending on the function. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-05-26 03:06:29 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
macros\macros.$(O) &
Reorganize the source code into subdirectories Make the source code easier to understand and keep track of by organizing it into subdirectories depending on the function. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-05-26 03:06:29 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
output\outform.$(O) output\outlib.$(O) output\legacy.$(O) &
output\strtbl.$(O) &
output\nulldbg.$(O) output\nullout.$(O) &
output\outbin.$(O) output\outaout.$(O) output\outcoff.$(O) &
output\outelf.$(O) &
output\outobj.$(O) output\outas86.$(O) output\outrdf2.$(O) &
output\outdbg.$(O) output\outieee.$(O) output\outmacho.$(O) &
output\codeview.$(O) &
Makefile: move all non-main objects into libnasm.a There is no fundamental reason for all objects that don't contain a main() function to not be part of libnasm.a; this allows the linker to do its job optimally, especially in the presence of debugging code which may not be needed under normal conditions. If we do end up with function name conflicts the library might have to be split, but it would be better to simply avoid that case. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 10:08:21 +08:00
&
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
disasm\disasm.$(O) disasm\sync.$(O)
make clean: clean up more things that ought to be Cleaning up hasn't really kept up to date with source code changes. Try make it better for now; this also ought to make it easier to do the corresponding cleaning in the *.mak files. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-03-01 17:23:00 +08:00
SUBDIRS = stdlib nasmlib output asm disasm x86 common macros
rdoff: move rdoff build into main Makefile to make it build on Windows NSIS packages rdoff, and we really want to be able to build the full NSIS package on an MSVC platform. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-07 08:24:03 +08:00
XSUBDIRS = test doc nsis rdoff
Makefile: don't store dependency information in git Make it possible to keep dependency information separate from the Makefiles, so we don't have to deal with it noisifying the git logs. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-11-02 04:48:17 +08:00
DEPDIRS = . include config x86 rdoff $(SUBDIRS)
syncfiles: use #-- ... --# for consistency with mkdep.pl mkdep.pl already used #-- ... --# (two dashes) whereas syncfiles.pl was using #--- ... ---# (three dashes). Change syncfiles.pl to match mkdep.pl.
2008-06-16 14:50:50 +08:00
#-- End File Lists --#
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
what: .SYMBOLIC
@echo Please build "dos", "win32", "os2" or "linux386"
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
dos: .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
@set TARGET_CFLAGS=-bt=DOS -I"$(%WATCOM)\h"
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
@set TARGET_LFLAGS=sys causeway
@%make all
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
win32: .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
@set TARGET_CFLAGS=-bt=NT -I"$(%WATCOM)\h" -I"$(%WATCOM)\h\nt"
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
@set TARGET_LFLAGS=sys nt
@%make all
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
os2: .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
@set TARGET_CFLAGS=-bt=OS2 -I"$(%WATCOM)\h" -I"$(%WATCOM)\h\os2"
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
@set TARGET_LFLAGS=sys os2v2
@%make all
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
linux386: .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
@set TARGET_CFLAGS=-bt=LINUX -I"$(%WATCOM)\lh"
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
@set TARGET_LFLAGS=sys linux
@%make all
Move canned OpenWatcom config to config/watcom.h. Move the canned OpenWatcom configuration file to config/watcom.h. Also exclude config/config.h from being a dependency for MSVC. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-20 04:23:04 +08:00
all: perlreq nasm$(X) ndisasm$(X) .SYMBOLIC
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# cd rdoff && $(MAKE) all
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: further fixes to build with OpenWatcom WMAKE Further fixes for OpenWatcom/WMAKE (BR 3392383). Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 15:01:14 +08:00
NASMLIB = nasm.lib
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
openwcom.mak: further fixes to build with OpenWatcom WMAKE Further fixes for OpenWatcom/WMAKE (BR 3392383). Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 15:01:14 +08:00
nasm$(X): $(NASM) $(NASMLIB)
$(LD) $(LDFLAGS) name nasm$(X) libr {$(NASMLIB) $(LIBS)} file {$(NASM)}
ndisasm$(X): $(NDISASM) $(LIBOBJ)
$(LD) $(LDFLAGS) name ndisasm$(X) libr {$(NASMLIB) $(LIBS)} file {$(NDISASM)}
nasm.lib: $(LIBOBJ)
wlib -q -b -n $@ $(LIBOBJ)
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
#-- Begin Generated File Rules --#
# Edit in Makefile.in, not here!
# These source files are automagically generated from data files using
# Perl scripts. They're distributed, though, so it isn't necessary to
# have Perl just to recompile NASM from the distribution.
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
# Perl-generated source files
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
PERLREQ = x86\insnsb.c x86\insnsa.c x86\insnsd.c x86\insnsi.h x86\insnsn.c &
x86\regs.c x86\regs.h x86\regflags.c x86\regdis.c x86\regdis.h &
x86\regvals.c asm\tokhash.c asm\tokens.h asm\pptok.h asm\pptok.c &
x86\iflag.c x86\iflaggen.h &
macros\macros.c &
asm\pptok.ph asm\directbl.c asm\directiv.h &
version.h version.mac version.mak nsis\version.nsh
INSDEP = x86\insns.dat x86\insns.pl x86\insns-iflags.ph
x86\iflag.c: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -fc &
$(srcdir)\x86\insns.dat x86\iflag.c
x86\iflaggen.h: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -fh &
$(srcdir)\x86\insns.dat x86\iflaggen.h
x86\insnsb.c: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -b &
$(srcdir)\x86\insns.dat x86\insnsb.c
x86\insnsa.c: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -a &
$(srcdir)\x86\insns.dat x86\insnsa.c
x86\insnsd.c: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -d &
$(srcdir)\x86\insns.dat x86\insnsd.c
x86\insnsi.h: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -i &
$(srcdir)\x86\insns.dat x86\insnsi.h
x86\insnsn.c: $(INSDEP)
$(RUNPERL) $(srcdir)\x86\insns.pl -n &
$(srcdir)\x86\insns.dat x86\insnsn.c
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# These files contains all the standard macros that are derived from
# the version number.
version.h: version version.pl
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
$(RUNPERL) $(srcdir)\version.pl h < $(srcdir)\version > version.h
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
version.mac: version version.pl
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
$(RUNPERL) $(srcdir)\version.pl mac < $(srcdir)\version > version.mac
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
version.sed: version version.pl
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
$(RUNPERL) $(srcdir)\version.pl sed < $(srcdir)\version > version.sed
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
version.mak: version version.pl
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
$(RUNPERL) $(srcdir)\version.pl make < $(srcdir)\version > version.mak
nsis\version.nsh: version version.pl
$(RUNPERL) $(srcdir)\version.pl nsis < $(srcdir)\version > nsis\version.nsh
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# This source file is generated from the standard macros file
# `standard.mac' by another Perl script. Again, it's part of the
# standard distribution.
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
macros\macros.c: macros\macros.pl asm\pptok.ph version.mac &
$(srcdir)\macros\*.mac $(srcdir)\output\*.mac
$(RUNPERL) $(srcdir)\macros\macros.pl version.mac &
$(srcdir)\macros\*.mac $(srcdir)\output\*.mac
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# These source files are generated from regs.dat by yet another
# perl script.
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
x86\regs.c: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl c &
$(srcdir)\x86\regs.dat > x86\regs.c
x86\regflags.c: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl fc &
$(srcdir)\x86\regs.dat > x86\regflags.c
x86\regdis.c: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl dc &
$(srcdir)\x86\regs.dat > x86\regdis.c
x86\regdis.h: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl dh &
$(srcdir)\x86\regs.dat > x86\regdis.h
x86\regvals.c: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl vc &
$(srcdir)\x86\regs.dat > x86\regvals.c
x86\regs.h: x86\regs.dat x86\regs.pl
$(RUNPERL) $(srcdir)\x86\regs.pl h &
$(srcdir)\x86\regs.dat > x86\regs.h
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# Assembler token hash
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
asm\tokhash.c: x86\insns.dat x86\regs.dat asm\tokens.dat asm\tokhash.pl &
perllib\phash.ph
$(RUNPERL) $(srcdir)\asm\tokhash.pl c &
$(srcdir)\x86\insns.dat $(srcdir)\x86\regs.dat &
$(srcdir)\asm\tokens.dat > asm\tokhash.c
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# Assembler token metadata
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
asm\tokens.h: x86\insns.dat x86\regs.dat asm\tokens.dat asm\tokhash.pl &
perllib\phash.ph
$(RUNPERL) $(srcdir)\asm\tokhash.pl h &
$(srcdir)\x86\insns.dat $(srcdir)\x86\regs.dat &
$(srcdir)\asm\tokens.dat > asm\tokens.h
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# Preprocessor token hash
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
asm\pptok.h: asm\pptok.dat asm\pptok.pl perllib\phash.ph
$(RUNPERL) $(srcdir)\asm\pptok.pl h &
$(srcdir)\asm\pptok.dat asm\pptok.h
asm\pptok.c: asm\pptok.dat asm\pptok.pl perllib\phash.ph
$(RUNPERL) $(srcdir)\asm\pptok.pl c &
$(srcdir)\asm\pptok.dat asm\pptok.c
asm\pptok.ph: asm\pptok.dat asm\pptok.pl perllib\phash.ph
$(RUNPERL) $(srcdir)\asm\pptok.pl ph &
$(srcdir)\asm\pptok.dat asm\pptok.ph
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# Directives hash
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
asm\directiv.h: asm\directiv.dat nasmlib\perfhash.pl perllib\phash.ph
$(RUNPERL) $(srcdir)\nasmlib\perfhash.pl h &
$(srcdir)\asm\directiv.dat asm\directiv.h
asm\directbl.c: asm\directiv.dat nasmlib\perfhash.pl perllib\phash.ph
$(RUNPERL) $(srcdir)\nasmlib\perfhash.pl c &
$(srcdir)\asm\directiv.dat asm\directbl.c
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
#-- End Generated File Rules --#
BR 3392397: WMAKE uses a nonstandard syntax for phony targets The standard syntax for a phony target in Make is: target: <dependencies> .PHONY: target ... however, Watcom WMAKE seems to use target: <dependencies> .SYMBOLIC and furthermore, seems to *require* it. Therefore, remove the "perlreq" target from the automatically distributed region and move it into the specific region; it should not need to change anyway since the PERLREQ list itself is still synced. If it was only a matter of the .SYMBOLIC versus .PHONY token it would be easy enough to change that in syncfiles.pl, but this syntax change is big enough that it doesn't make enough sense to worry about. Reported-by: sezero <sezero@users.sourceforge.net> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-06 12:24:55 +08:00
perlreq: $(PERLREQ) .SYMBOLIC
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
#-- Begin NSIS Rules --#
# Edit in Makefile.in, not here!
# NSIS is not built except by explicit request, as it only applies to
# Windows platforms
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
nsis\arch.nsh: nsis\getpearch.pl nasm$(X)
$(PERL) $(srcdir)\nsis\getpearch.pl nasm$(X) > nsis\arch.nsh
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
# Should only be done after "make everything".
# The use of redirection here keeps makensis from moving the cwd to the
# source directory.
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
nsis: nsis\nasm.nsi nsis\arch.nsh nsis\version.nsh
$(MAKENSIS) -Dsrcdir="$(srcdir)" -Dobjdir="$(objdir)" - < nsis\nasm.nsi
Makefiles: distribute file generation rules via syncfiles.pl Distribute the file generation rules to auxiliary Makefiles via syncfiles.pl. These rules are OS- and Make-dialect-generic enough that our mangling script handles them well enough. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2017-04-04 02:13:29 +08:00
#-- End NSIS Rules --#
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
clean: .SYMBOLIC
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
rm -f *.$(O) *.s *.i
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
rm -f asm\*.$(O) asm\*.s asm\*.i
rm -f x86\*.$(O) x86\*.s x86\*.i
rm -f lib\*.$(O) lib\*.s lib\*.i
rm -f macros\*.$(O) macros\*.s macros\*.i
rm -f output\*.$(O) output\*.s output\*.i
rm -f common\*.$(O) common\*.s common\*.i
rm -f stdlib\*.$(O) stdlib\*.s stdlib\*.i
rm -f nasmlib\*.$(O) nasmlib\*.s nasmlib\*.i
rm -f disasm\*.$(O) disasm\*.s disasm\*.i
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
rm -f config.h config.log config.status
openwcom.mak: further fixes to build with OpenWatcom WMAKE Further fixes for OpenWatcom/WMAKE (BR 3392383). Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2017-03-01 15:01:14 +08:00
rm -f nasm$(X) ndisasm$(X) $(NASMLIB)
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# cd rdoff && $(MAKE) clean
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
distclean: clean .SYMBOLIC
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
rm -f config.h config.log config.status
rm -f Makefile *~ *.bak *.lst *.bin
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
rm -f output\*~ output\*.bak
rm -f test\*.lst test\*.bin test\*.$(O) test\*.bin
# -del \s autom4te*.cache
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# cd rdoff && $(MAKE) distclean
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
cleaner: clean .SYMBOLIC
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
rm -f $(PERLREQ)
rm -f *.man
rm -f nasm.spec
# cd doc && $(MAKE) clean
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
spotless: distclean cleaner .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
rm -f doc\Makefile doc\*~ doc\*.bak
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
strip: .SYMBOLIC
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
$(STRIP) *.exe
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
rdf:
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# cd rdoff && $(MAKE)
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
doc:
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
# cd doc && $(MAKE) all
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
everything: all doc rdf
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
#
# This build dependencies in *ALL* makefiles. Partially for that reason,
# it's expected to be invoked manually.
#
alldeps: perlreq .SYMBOLIC
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
$(PERL) syncfiles.pl Makefile.in Mkfiles\openwcom.mak
$(PERL) mkdep.pl -M Makefile.in Mkfiles\openwcom.mak -- . output lib
openwcom.mak: Update to use features from newer WMAKE Change the OpenWatcom WMAKE Makefile to use the facilities available in WMAKE to support cross-compilation properly. See BR 3079573.
2011-03-16 06:37:30 +08:00
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
#-- Magic hints to mkdep.pl --#
# @object-ending: ".$(O)"
openwcom.mak: use \ as path separators Apparently OS/2 really wants \ as path separators, and that is really the main target for OpenWatcom these days, so change the path separator in this Makefile. For building on Linux we'd be better off with a GNU Makefile anyway, but what is the point, really... Reported-by: Andy Willis <abwillis1@gmail.com> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2018-02-23 07:01:28 +08:00
# @path-separator: "\"
Move canned OpenWatcom config to config/watcom.h. Move the canned OpenWatcom configuration file to config/watcom.h. Also exclude config/config.h from being a dependency for MSVC. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-20 04:23:04 +08:00
# @exclude: "config/config.h"
Add Makefile for OpenWatcom (DOS, OS/2 or Win32 output) Add a Makefile for OpenWatcom using WMAKE. This is a horrible version of Make, but since it's bundled with OpenWatcom it is probably better to stick to it. It has the nice property that it can produce DOS, Win32 or OS/2 binaries. This Makefile currently assumes that it is hosted on a system where pathname separators are backslashes. For cross-compiling using OpenWatcom on a Linux system it is probably better to write a separate Makefile using GNU make to invoke Watcom.
2007-09-27 10:57:07 +08:00
# @continuation: "&"
#-- Everything below is generated by mkdep.pl - do not edit --#
Reference in New Issue Copy Permalink