Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/tools/Makefile

20 lines
443 B
Makefile
Raw Normal View History

Build the cross-dbsym.
2001-11-09 18:07:25 +03:00
# $NetBSD: Makefile,v 1.15 2001/11/09 15:07:25 thorpej Exp $
Bootstrap toolchain framework, first pass.
2001-08-14 15:01:55 +04:00
Add lorder to TOOLDIR host tools. Only descend into directories if USE_NEW_TOOLCHAIN is set (allows top level Makefile to use "-m ${.CURDIR}/share/mk" to get the "correct" <bsd.own.mk> when descending into src/tools/Makefile).
2001-09-22 08:15:19 +04:00
.include <bsd.own.mk>
* Always use the makewrapper when starting a build phase. * Set stuff mostly in the environment, not on make(1)'s command line. This is needed for MACHINE and MACHINE_ARCH (noted by bjh21), and keeps the mk.conf-overriding-env behavior (suggested by several people). * Use MAKEFLAGS to make the wrapper script more readable. * When prepping objdir in tools for the default TOOLDIR value, just make that objdir; leave the recursive "make obj" for later.
2001-11-02 08:07:22 +03:00
.if !defined(NOSUBDIR)
Make mtree a host tool and use it when appropriate.
2001-10-09 09:19:03 +04:00
SUBDIR= binstall .WAIT gencat mkdep mtree rpcgen tsort \
- Create a real cpp binary. - Set CC properly in environment for mkdep and lint. - Add compile_et to TOOLDIR host tools.
2001-09-22 03:00:35 +04:00
yacc .WAIT lex .WAIT \
Add asn1_compile as a host tool.
2001-10-25 11:45:13 +04:00
asn1_compile compile_et config lint lint1 lint2 lorder \
Pull in mdsetimage to the tools builds. (XXX - using libbfd here would probably be preferrable long term).
2001-10-22 03:10:46 +04:00
toolchain .WAIT texinfo crunchgen msgc menuc mklocale \
Build the cross-dbsym.
2001-11-09 18:07:25 +03:00
mdsetimage dbsym
* Always use the makewrapper when starting a build phase. * Set stuff mostly in the environment, not on make(1)'s command line. This is needed for MACHINE and MACHINE_ARCH (noted by bjh21), and keeps the mk.conf-overriding-env behavior (suggested by several people). * Use MAKEFLAGS to make the wrapper script more readable. * When prepping objdir in tools for the default TOOLDIR value, just make that objdir; leave the recursive "make obj" for later.
2001-11-02 08:07:22 +03:00
.endif
Bootstrap toolchain framework, first pass.
2001-08-14 15:01:55 +04:00
Recurse properly; just add "build" to TARGETS (fixes reported problem where "make clean" doesn't work at the src/tools level).
2001-10-04 20:33:05 +04:00
TARGETS+= build
Bootstrap toolchain framework, first pass.
2001-08-14 15:01:55 +04:00
.include <bsd.subdir.mk>
* Always descend into "tools" regardless of USETOOLS setting. Instead, just don't build the tools if USETOOLS!=yes. This permits objdirs to be created even when USETOOLS=no. * Clean up use of "-m" by specifying it to .MAKEFLAGS: if needed.
2001-10-31 04:20:09 +03:00
.include <bsd.obj.mk>
* Create a variable HOST_OSTYPE that represents the host build environment, using `uname -s`-`uname -r`-`uname -p || uname -m`. This can be overridden in mk.conf or the environment, and is used by host tools to ensure that build hosts do not clobber each other. * Now that there's an objdir in src/tools, make a default TOOLDIR by creating "tools.${HOST_OSTYPE}" in the objdir (if it exists) of src/tools. This means that TOOLDIR is no longer required to be set in a build, though it still may be set manually if desired. * Set MKTOOLS to "yes" by default, since the default TOOLDIR is now located in a known mutable location. This may still be set manually if desired.
2001-10-31 20:46:08 +03:00
cleantools:
rm -r -f tools.${HOST_OSTYPE}