651b44e211
as with user-land programs, include files are installed by each directory
in the tree that has includes to install. (This allows more flexibility
as to what gets installed, makes 'partial installs' easier, and gives us
more options as to which machines' includes get installed at any given
time.) The old SYS_INCLUDES={symlinks,copies} behaviours are _both_
still supported, though at least one bug in the 'symlinks' case is
fixed by this change. Include files can't be build before installation,
so directories that have includes as targets (e.g. dev/pci) have to move
those targets into a different Makefile.
30 lines
745 B
Makefile
30 lines
745 B
Makefile
# $NetBSD: Makefile,v 1.5 1998/06/12 23:22:33 cgd Exp $
|
|
|
|
# Makefile for arm32 tags file and boot blocks
|
|
|
|
TARM32= ../arm32/tags
|
|
SARM32= ../arm32/arm32/*.[ch] ../arm32/include/*.h \
|
|
../arm32/dev/*.[ch] ../arm32/podulebus/*.[ch] ../arm32/mainbus/*.[ch]
|
|
AARM32= ../arm32/arm32/*.s
|
|
|
|
# Directories in which to place tags links
|
|
DARM32= dev mainbus podulebus include
|
|
|
|
.include "../../kern/Make.tags.inc"
|
|
|
|
tags:
|
|
-ctags -wdtf ${TARM32} ${SARM32} ${COMM}
|
|
egrep "^ENTRY(.*)|^ALTENTRY(.*)" ${AARM32} | \
|
|
sed "s;\([^:]*\):\([^(]*\)(\([^, )]*\)\(.*\);\3 \1 /^\2(\3\4$$/;" \
|
|
>> ${TARM32}
|
|
sort -o ${TARM32} ${TARM32}
|
|
|
|
links:
|
|
-for i in ${DARM32}; do \
|
|
cd $$i && rm -f tags; ln -s ../tags tags; done
|
|
|
|
|
|
SUBDIR= include
|
|
|
|
.include <bsd.subdir.mk>
|