This is an implementation of POSIX make.
It should build on most modernish Unix-style systems:
-
It comes with its own makefile, naturally, but if you don't have a
make
binary already the commandcc -o make *.c
should get you started. -
Command line options may not work properly due to differences in how
getopt(3)
is reset. AdjustGETOPT_RESET()
in make.h for your platform, if necessary.
Microsoft Windows users will find pdpmake
included in the
BusyBox for Windows binaries.
Download an appropriate binary for your system and rename it make.exe
or
pdpmake.exe
. BusyBox for Windows includes a Unix shell and many utilities.
These can be used in Makefiles without any further setup.
The default configuration enables extensions: some from a future POSIX standard and some that are non-POSIX. Generally these extensions are compatible with GNU make:
- double-colon rules
-include
to ignore missing include files- include files are created if required
ifdef
/ifndef
/ifeq
/ifneq
/else
/endif
conditionalslib.a(mem1.o mem2.o...)
syntax for archive members:=
/::=
/:::=
/+=
/?=
/!=
macro assignments- macro expansions can be nested
- chained inference rules
*
/?
/[]
wildcards for filenames in target rules$(SRC:%.c=%.o)
pattern macro expansions- special handling of
MAKE
macro $^
and$+
internal macros- the
$<
and$*
internal macros are valid for target rules - skip duplicate entries in
$?
.PHONY
special target-C directory
and-j maxjobs
command line options#
doesn't start a comment in macro expansions or build commands#
may be escaped with a backslash- macro definitions and targets can be mixed on the command line
- the
CURDIR
macro is set to the current directory on start up
When extensions are enabled adding the .POSIX
target to your makefile
will disable them. Other versions of make tend to allow extensions even
in POSIX mode.
Setting the environment variable PDPMAKE_POSIXLY_CORRECT
(its value
doesn't matter) or giving the --posix
option as the first on the
command line also turn off extensions.