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

571 lines
27 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
# cross-compile on a DOS/Win32/OS2/Linux 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 = .
VPATH = .;$(srcdir)/output;$(srcdir)/lib
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)
INTERNAL_CFLAGS = -I$(srcdir) -I. -DHAVE_CONFIG_H
ALL_CFLAGS = $(BUILD_CFLAGS) $(INTERNAL_CFLAGS)
LD = *wlink
LDEBUG =
LDFLAGS = op quiet $(%TARGET_LFLAGS) $(LDEBUG)
LIBS =
Unbreak building in a separate object directory Fix bitrot in building in a separate object directory. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 04:20:01 +08:00
PERL = perl -I$(srcdir)/perllib -I$(srcdir)
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 = 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
# 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!
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
NASM = asm/nasm.$(O) &
asm/float.$(O) &
asm/directiv.$(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/stdscan.$(O) &
asm/strfunc.$(O) asm/tokhash.$(O) &
asm/segalloc.$(O) &
asm/preproc-nop.$(O) &
asm/rdstrnum.$(O) &
&
macros/macros.$(O) &
&
backend: move wrapper for legacy output functions to a library routine Move the wrapper for legacy output into a library routine so the backends can be ported one at a time. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-09-25 00:46:47 +08:00
output/outform.$(O) output/outlib.$(O) output/legacy.$(O) &
output/nulldbg.$(O) output/nullout.$(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
output/outbin.$(O) output/outaout.$(O) output/outcoff.$(O) &
out: Elf -- Merge Elf32, Elfx32 and Elf64 into single file There is a bunch of common code here so merge them all into one file. Unmergable parts are wrapped with is_elf() helpers. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2016-04-10 22:37:11 +08:00
output/outelf.$(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
output/outobj.$(O) output/outas86.$(O) output/outrdf2.$(O) &
outmacho: rename outmac.c to outmacho.c We already have outmacho.mac, so name this file outmacho.c. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-02-13 13:18:12 +08:00
output/outdbg.$(O) output/outieee.$(O) output/outmacho.$(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
output/codeview.$(O)
NDISASM = disasm/ndisasm.$(O) disasm/disasm.$(O) disasm/sync.$(O)
Makefiles: use actual archive managers 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>
2016-03-08 18:06:39 +08:00
lib: split library into stdlib and nasmlib; header handling fixes Split lib/ into nasmlib/ (for nasm-specific functions) and stdlib/ (for replacements for C library functions which may be missing.) Rename the ersatz inttypes.h to nasmint.h so we can use a simple test in compiler.h instead of dealing with include path magic. Remove tests in configure.in for ancient missing functions (which will break the build anyway.) Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-09 04:14:55 +08:00
LIBOBJ = stdlib/snprintf.$(O) stdlib/vsnprintf.$(O) stdlib/strlcpy.$(O) &
nasmlib: break up nasmlib.c into logical components nasmlib.c had basically turned into a garbage bin of various functions with very little in common. Break it up into logical components for isolation and manageability. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-05-25 20:42:47 +08:00
stdlib/strnlen.$(O) &
nasmlib/ver.$(O) &
nasmlib/crc64.$(O) nasmlib/malloc.$(O) &
nasmlib/error.$(O) nasmlib/md5c.$(O) nasmlib/string.$(O) &
nasmlib/file.$(O) nasmlib/ilog2.$(O) &
nasmlib/realpath.$(O) nasmlib/filename.$(O) nasmlib/srcfile.$(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
nasmlib/zerobuf.$(O) nasmlib/readnum.$(O) nasmlib/bsi.$(O) &
nasmlib/rbtree.$(O) nasmlib/hashtbl.$(O) &
nasmlib/raa.$(O) nasmlib/saa.$(O) &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
nasmlib/strlist.$(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
common/common.$(O) &
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)
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
@set TARGET_CFLAGS=-bt=DOS -I"$(%WATCOM)/h"
@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
@set TARGET_CFLAGS=-bt=NT -I"$(%WATCOM)/h" -I"$(%WATCOM)/h/nt"
@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
BR3411280: Fix incorrect compiler option for OS/2 target in Open Watcom makefile For OS2 target the -bt option should be set accordingly. Signed-off-by: Jiri Malak <malak.jiri@gmail.com> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-09-21 01:37:06 +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
@set TARGET_CFLAGS=-bt=LINUX -I"$(%WATCOM)/lh"
@set TARGET_LFLAGS=sys linux
@%make all
all: config.h perlreq nasm$(X) ndisasm$(X) .SYMBOLIC
# 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
nasm$(X): $(NASM)
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
$(LD) $(LDFLAGS) name nasm$(X) file {$(NASM)} $(LIBS)
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
ndisasm$(X): $(NDISASM)
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
$(LD) $(LDFLAGS) name ndisasm$(X) file {$(NDISASM)} $(LIBS)
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 automagically generated from a single
# instruction-table file by a Perl script. They're distributed,
# though, so it isn't necessary to have Perl just to recompile NASM
# from the distribution.
iflag: Start using new instruction flags engine Here we start using instruction flags generator. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2013-11-10 02:16:11 +08:00
insns.pl: insns-iflags.pl
iflag.c iflag.h: insns.dat insns.pl
$(PERL) $(srcdir)/insns.pl -t $(srcdir)/insns.dat
Generate a byte array instead of using strings for the byte codes Generate a byte array instead of using C compiler strings for the byte codes. This has a few advantages: - No need to special-case zero due to broken C compilers. - Only insns.pl only ever reads the string, so we can invent our own syntax. - Compaction. - We can give it the proper, unsigned type.
2008-05-13 02:00:50 +08:00
insnsb.c: insns.dat insns.pl
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
$(PERL) $(srcdir)/insns.pl -b $(srcdir)/insns.dat
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
insnsa.c: insns.dat insns.pl
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
$(PERL) $(srcdir)/insns.pl -a $(srcdir)/insns.dat
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
insnsd.c: insns.dat insns.pl
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
$(PERL) $(srcdir)/insns.pl -d $(srcdir)/insns.dat
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
insnsi.h: insns.dat insns.pl
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
$(PERL) $(srcdir)/insns.pl -i $(srcdir)/insns.dat
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
insnsn.c: insns.dat insns.pl
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
$(PERL) $(srcdir)/insns.pl -n $(srcdir)/insns.dat
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: 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
$(PERL) $(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: 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
$(PERL) $(srcdir)/version.pl mac < $(srcdir)/version > version.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
# 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: 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
macros.c: macros.pl standard.mac version.mac macros/*.mac output/*.mac
$(PERL) $<
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.
regs.c: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl c $(srcdir)/regs.dat > regs.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
regflags.c: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl fc $(srcdir)/regs.dat > regflags.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
regdis.c: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl dc $(srcdir)/regs.dat > regdis.c
Avoid #including .c files; instead compile as separate units Don't #include .c files, even if they are auto-generated; instead compile them as separate compilation units and let the linker do its job.
2008-05-21 05:21:29 +08:00
regdis.h: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl dh $(srcdir)/regs.dat > regdis.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
regvals.c: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl vc $(srcdir)/regs.dat > regvals.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
regs.h: regs.dat regs.pl
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
$(PERL) $(srcdir)/regs.pl h $(srcdir)/regs.dat > 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
tokhash.c: insns.dat regs.dat tokens.dat tokhash.pl perllib/phash.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
$(PERL) $(srcdir)/tokhash.pl c $(srcdir)/insns.dat $(srcdir)/regs.dat &
$(srcdir)/tokens.dat > 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
tokens.h: insns.dat regs.dat tokens.dat tokhash.pl perllib/phash.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
$(PERL) $(srcdir)/tokhash.pl h $(srcdir)/insns.dat $(srcdir)/regs.dat &
$(srcdir)/tokens.dat > 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
pptok.h: pptok.dat pptok.pl perllib/phash.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
$(PERL) $(srcdir)/pptok.pl h $(srcdir)/pptok.dat pptok.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
pptok.c: pptok.dat pptok.pl perllib/phash.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
$(PERL) $(srcdir)/pptok.pl c $(srcdir)/pptok.dat pptok.c
pptok.ph: pptok.dat pptok.pl perllib/phash.ph
$(PERL) $(srcdir)/pptok.pl ph $(srcdir)/pptok.dat pptok.ph
# Directives hash
directiv.h: directiv.dat directiv.pl perllib/phash.ph
$(PERL) $(srcdir)/directiv.pl h $(srcdir)/directiv.dat directiv.h
directiv.c: directiv.dat directiv.pl perllib/phash.ph
$(PERL) $(srcdir)/directiv.pl c $(srcdir)/directiv.dat directiv.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
# This target generates all files that require perl.
# This allows easier generation of distribution (see dist target).
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
PERLREQ = pptok.ph macros.c insnsb.c insnsa.c insnsd.c insnsi.h insnsn.c &
regs.c regs.h regflags.c regdis.c regdis.h regvals.c &
tokhash.c tokens.h pptok.h pptok.c &
directiv.c directiv.h &
iflag: Start using new instruction flags engine Here we start using instruction flags generator. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2013-11-10 02:16:11 +08:00
version.h version.mac &
iflag.c iflag.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
perlreq: $(PERLREQ) .SYMBOLIC
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
rm -f lib/*.$(O) lib/*.s lib/*.i
rm -f output/*.$(O) output/*.s output/*.i
rm -f config.h config.log config.status
rm -f nasm$(X) ndisasm$(X)
# 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
rm -f output/*~ output/*.bak
rm -f test/*.lst test/*.bin test/*.$(O) test/*.bin
# -del /s autom4te*.cache
# 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: 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 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
config.h: Mkfiles/openwcom.mak
@echo Creating $@
@%create $@
@%append $@ $#define HAVE_DECL_STRCASECMP 1
@%append $@ $#define HAVE_DECL_STRICMP 1
@%append $@ $#define HAVE_DECL_STRLCPY 1
@%append $@ $#define HAVE_DECL_STRNCASECMP 1
@%append $@ $#define HAVE_DECL_STRNICMP 1
@%append $@ $#define HAVE_INTTYPES_H 1
@%append $@ $#define HAVE_LIMITS_H 1
@%append $@ $#define HAVE_MEMORY_H 1
@%append $@ $#define HAVE_SNPRINTF 1
@%append $@ $#define HAVE_STDBOOL_H 1
@%append $@ $#define HAVE_STDINT_H 1
@%append $@ $#define HAVE_STDLIB_H 1
@%append $@ $#define HAVE_STRCASECMP 1
@%append $@ $#define HAVE_STRCSPN 1
@%append $@ $#define HAVE_STRICMP 1
@%append $@ $#define HAVE_STRINGS_H 1
@%append $@ $#define HAVE_STRING_H 1
@%append $@ $#define HAVE_STRLCPY 1
@%append $@ $#define HAVE_STRNCASECMP 1
@%append $@ $#define HAVE_STRNICMP 1
@%append $@ $#define HAVE_STRSPN 1
@%append $@ $#define HAVE_SYS_STAT_H 1
@%append $@ $#define HAVE_SYS_TYPES_H 1
@%append $@ $#define HAVE_UNISTD_H 1
@%append $@ $#define HAVE_VSNPRINTF 1
@%append $@ $#define STDC_HEADERS 1
#
# This build dependencies in *ALL* makefiles. Partially for that reason,
# it's expected to be invoked manually.
#
alldeps: perlreq .SYMBOLIC
$(PERL) syncfiles.pl Makefile.in Mkfiles/openwcom.mak
$(PERL) mkdep.pl -M Makefile.in Mkfiles/openwcom.mak -- . output 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
#-- Magic hints to mkdep.pl --#
# @object-ending: ".$(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
# @path-separator: "/"
# @exclude: ""
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 --#
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/assemble.$(O): asm/assemble.c asm/assemble.h asm/directiv.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/listing.h asm/pptok.h asm/preproc.h asm/tokens.h config/config.h &
config/msvc.h config/unknown.h include/compiler.h include/disp8.h &
include/iflag.h include/insns.h include/nasm.h include/nasmint.h &
include/nasmlib.h include/opflags.h include/strlist.h include/tables.h &
x86/iflaggen.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/directiv.$(O): asm/directiv.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/hashtbl.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/eval.$(O): asm/eval.c asm/directiv.h asm/eval.h asm/float.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/labels.h include/nasm.h include/nasmint.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/nasmlib.h include/opflags.h include/strlist.h include/tables.h &
x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/exprlib.$(O): asm/exprlib.c asm/directiv.h asm/pptok.h asm/preproc.h &
config/config.h config/msvc.h config/unknown.h include/compiler.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/strlist.h include/tables.h x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/float.$(O): asm/float.c asm/directiv.h asm/float.h asm/pptok.h &
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
asm/labels.$(O): asm/labels.c asm/directiv.h asm/pptok.h asm/preproc.h &
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/hashtbl.h include/labels.h include/nasm.h include/nasmint.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/nasmlib.h include/opflags.h include/strlist.h include/tables.h &
x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/listing.$(O): asm/listing.c asm/directiv.h asm/listing.h asm/pptok.h &
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/nasm.$(O): asm/nasm.c asm/assemble.h asm/directiv.h asm/eval.h &
asm/float.h asm/listing.h asm/parser.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/stdscan.h asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/insns.h include/labels.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/raa.h include/saa.h include/strlist.h include/tables.h &
include/ver.h output/outform.h x86/iflaggen.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/parser.$(O): asm/parser.c asm/directiv.h asm/eval.h asm/float.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/parser.h asm/pptok.h asm/preproc.h asm/stdscan.h asm/tokens.h &
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/iflag.h include/insns.h include/nasm.h include/nasmint.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/nasmlib.h include/opflags.h include/strlist.h include/tables.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
x86/iflaggen.h x86/insnsi.h x86/regs.h
asm/pptok.$(O): asm/pptok.c asm/pptok.h asm/preproc.h config/config.h &
config/msvc.h config/unknown.h include/compiler.h include/hashtbl.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
include/nasmint.h include/nasmlib.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc-nop.$(O): asm/preproc-nop.c asm/directiv.h asm/listing.h &
asm/pptok.h asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
asm/preproc.$(O): asm/preproc.c asm/directiv.h asm/eval.h asm/listing.h &
asm/pptok.h asm/preproc.h asm/quote.h asm/stdscan.h asm/tokens.h &
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/hashtbl.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
asm/quote.$(O): asm/quote.c asm/quote.h config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/rdstrnum.$(O): asm/rdstrnum.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/strlist.h include/tables.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/segalloc.$(O): asm/segalloc.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/insns.h include/nasm.h &
include/nasmint.h include/nasmlib.h include/opflags.h include/strlist.h &
include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
asm/stdscan.$(O): asm/stdscan.c asm/directiv.h asm/pptok.h asm/preproc.h &
asm/quote.h asm/stdscan.h asm/tokens.h config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/iflag.h include/insns.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/strlist.h include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/strfunc.$(O): asm/strfunc.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/strlist.h include/tables.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
asm/tokhash.$(O): asm/tokhash.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/stdscan.h asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/hashtbl.h include/iflag.h include/insns.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/strlist.h include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
common/common.$(O): common/common.c asm/directiv.h asm/pptok.h asm/preproc.h &
asm/tokens.h config/config.h config/msvc.h config/unknown.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
include/compiler.h include/iflag.h include/insns.h include/nasm.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/nasmint.h include/nasmlib.h include/opflags.h include/strlist.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
disasm/disasm.$(O): disasm/disasm.c asm/directiv.h asm/pptok.h asm/preproc.h &
asm/tokens.h config/config.h config/msvc.h config/unknown.h disasm/disasm.h &
disasm/sync.h include/compiler.h include/disp8.h include/iflag.h &
include/insns.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/iflaggen.h &
x86/insnsi.h x86/regdis.h x86/regs.h
disasm/ndisasm.$(O): disasm/ndisasm.c asm/directiv.h asm/pptok.h &
asm/preproc.h asm/tokens.h config/config.h config/msvc.h config/unknown.h &
disasm/disasm.h disasm/sync.h include/compiler.h include/iflag.h &
include/insns.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h include/ver.h &
x86/iflaggen.h x86/insnsi.h x86/regs.h
disasm/sync.$(O): disasm/sync.c config/config.h config/msvc.h &
config/unknown.h disasm/sync.h include/compiler.h include/nasmint.h &
include/nasmlib.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
macros/macros.$(O): macros/macros.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/hashtbl.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h output/outform.h &
x86/insnsi.h x86/regs.h
nasmlib/bsi.$(O): nasmlib/bsi.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/crc64.$(O): nasmlib/crc64.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/hashtbl.h include/nasmint.h &
include/nasmlib.h
nasmlib/error.$(O): nasmlib/error.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/file.$(O): nasmlib/file.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/filename.$(O): nasmlib/filename.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
nasmlib/hashtbl.$(O): nasmlib/hashtbl.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/hashtbl.h include/nasm.h include/nasmint.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/nasmlib.h include/opflags.h include/strlist.h include/tables.h &
x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
nasmlib/ilog2.$(O): nasmlib/ilog2.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/malloc.$(O): nasmlib/malloc.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/md5c.$(O): nasmlib/md5c.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/md5.h include/nasmint.h
nasmlib/raa.$(O): nasmlib/raa.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h &
include/raa.h
nasmlib/rbtree.$(O): nasmlib/rbtree.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/rbtree.h
nasmlib/readnum.$(O): nasmlib/readnum.c asm/directiv.h asm/pptok.h &
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
nasmlib/realpath.$(O): nasmlib/realpath.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/saa.$(O): nasmlib/saa.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h &
include/saa.h
nasmlib/srcfile.$(O): nasmlib/srcfile.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/hashtbl.h include/nasmint.h &
include/nasmlib.h
nasmlib/string.$(O): nasmlib/string.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
nasmlib/strlist.$(O): nasmlib/strlist.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h &
include/strlist.h
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
nasmlib/ver.$(O): nasmlib/ver.c include/ver.h version.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
nasmlib/zerobuf.$(O): nasmlib/zerobuf.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/codeview.$(O): output/codeview.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/hashtbl.h include/md5.h include/nasm.h &
include/nasmint.h include/nasmlib.h include/opflags.h include/saa.h &
include/strlist.h include/tables.h output/outlib.h output/pecoff.h &
version.h x86/insnsi.h x86/regs.h
backend: move wrapper for legacy output functions to a library routine Move the wrapper for legacy output into a library routine so the backends can be ported one at a time. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-09-25 00:46:47 +08:00
output/legacy.$(O): output/legacy.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-15 06:09:52 +08:00
include/strlist.h include/tables.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/nulldbg.$(O): output/nulldbg.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h output/outlib.h &
x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/nullout.$(O): output/nullout.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h output/outlib.h &
x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outaout.$(O): output/outaout.c asm/directiv.h asm/eval.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h asm/stdscan.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/raa.h include/saa.h include/strlist.h &
include/tables.h output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outas86.$(O): output/outas86.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/raa.h include/saa.h include/strlist.h &
include/tables.h output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outbin.$(O): output/outbin.c asm/directiv.h asm/eval.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h asm/stdscan.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/labels.h include/nasm.h include/nasmint.h &
include/nasmlib.h include/opflags.h include/saa.h include/strlist.h &
include/tables.h output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outcoff.$(O): output/outcoff.c asm/directiv.h asm/eval.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/raa.h include/saa.h include/strlist.h &
include/tables.h output/outform.h output/outlib.h output/pecoff.h &
x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outdbg.$(O): output/outdbg.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/strlist.h include/tables.h output/outform.h output/outlib.h &
x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outelf.$(O): output/outelf.c asm/directiv.h asm/eval.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h asm/stdscan.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/raa.h include/rbtree.h include/saa.h &
include/strlist.h include/tables.h include/ver.h output/dwarf.h &
output/elf.h output/outelf.h output/outform.h output/outlib.h &
output/stabs.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outform.$(O): output/outform.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h output/outform.h &
x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outieee.$(O): output/outieee.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h include/ver.h &
output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outlib.$(O): output/outlib.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/strlist.h include/tables.h output/outlib.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
output/outmacho.$(O): output/outmacho.c asm/directiv.h asm/pptok.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/raa.h include/rbtree.h include/saa.h &
Factor out common string list handling code Simplify the preprocessor code by factoring out the common string list handling code. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-10-04 16:12:28 +08:00
include/strlist.h include/tables.h output/outform.h output/outlib.h &
x86/insnsi.h x86/regs.h
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
output/outobj.$(O): output/outobj.c asm/directiv.h asm/eval.h asm/pptok.h &
asm/preproc.h asm/stdscan.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h include/ver.h &
output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
output/outrdf2.$(O): output/outrdf2.c asm/directiv.h asm/pptok.h &
asm/preproc.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/rdoff.h include/saa.h include/strlist.h &
include/tables.h output/outform.h output/outlib.h x86/insnsi.h x86/regs.h
stdlib/snprintf.$(O): stdlib/snprintf.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
stdlib/strlcpy.$(O): stdlib/strlcpy.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h
stdlib/strnlen.$(O): stdlib/strnlen.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h
stdlib/vsnprintf.$(O): stdlib/vsnprintf.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/nasmlib.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
x86/disp8.$(O): x86/disp8.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/disp8.h include/nasm.h include/nasmint.h include/nasmlib.h &
include/opflags.h include/strlist.h include/tables.h x86/insnsi.h &
x86/regs.h
x86/iflag.$(O): x86/iflag.c config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/nasmint.h x86/iflaggen.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
x86/insnsa.$(O): x86/insnsa.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/insns.h include/nasm.h &
include/nasmint.h include/nasmlib.h include/opflags.h include/strlist.h &
include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
x86/insnsb.$(O): x86/insnsb.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/insns.h include/nasm.h &
include/nasmint.h include/nasmlib.h include/opflags.h include/strlist.h &
include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
x86/insnsd.$(O): x86/insnsd.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
asm/tokens.h config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/iflag.h include/insns.h include/nasm.h &
include/nasmint.h include/nasmlib.h include/opflags.h include/strlist.h &
include/tables.h x86/iflaggen.h x86/insnsi.h x86/regs.h
x86/insnsn.$(O): x86/insnsn.c config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasmint.h include/tables.h x86/insnsi.h
Run make alldeps Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-08-17 05:48:54 +08:00
x86/regdis.$(O): x86/regdis.c x86/regdis.h x86/regs.h
x86/regflags.$(O): x86/regflags.c asm/directiv.h asm/pptok.h asm/preproc.h &
alldeps: handle uses of full pathnames, e.g. "config/config.h" Sometimes we really want to use an extended pathname for an include file, for documentation purposes; e.g. "config/config.h". This makes alldeps handle that case correctly (and also adds the config/ directory to directories scanned by alldeps). It is unclear if this will work correctly if there are include files with the same name in different directories, but we currently do not have any case like that. Reported-by: anonymous coward <nasm64developer@users.sf.net> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-10-07 05:08:31 +08:00
config/config.h config/msvc.h config/unknown.h include/compiler.h &
include/nasm.h include/nasmint.h include/nasmlib.h include/opflags.h &
include/strlist.h include/tables.h x86/insnsi.h x86/regs.h
x86/regs.$(O): x86/regs.c config/config.h config/msvc.h config/unknown.h &
include/compiler.h include/nasmint.h include/tables.h x86/insnsi.h
x86/regvals.$(O): x86/regvals.c config/config.h config/msvc.h &
config/unknown.h include/compiler.h include/nasmint.h include/tables.h &
x86/insnsi.h
Reference in New Issue Copy Permalink