2012-03-31 20:24:03 +02:00
|
|
|
# $NetBSD: Makefile,v 1.1 2009/05/08 17:28:01 christos Exp $
|
|
|
|
|
|
|
|
|
|
.include <bsd.own.mk>
|
|
|
|
|
.include <bsd.sys.mk>
|
|
|
|
|
|
|
|
|
|
.include "../Makefile.inc"
|
|
|
|
|
|
|
|
|
|
.if ${MKSHARE} != "no"
|
|
|
|
|
FILESDIR= ${MFILESDIR}
|
|
|
|
|
FILES= ${MFILES}
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
PROG= file
|
2012-10-26 15:22:39 +02:00
|
|
|
.if defined(__MINIX)
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
LDADD+= -L../lib
|
2012-10-26 15:22:39 +02:00
|
|
|
.endif
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
LDADD+= -lmagic -lz
|
2012-03-31 20:24:03 +02:00
|
|
|
DPADD+= ${LIBMAGIC} ${LIBZ}
|
|
|
|
|
MAN= file.1 magic.5
|
|
|
|
|
|
|
|
|
|
CLEANFILES+= magic.mgc
|
|
|
|
|
.if ${MKSHARE} != "no"
|
|
|
|
|
realall: file magic.mgc
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.if ${MKSHARE} != "no"
|
2012-05-02 13:23:57 +02:00
|
|
|
magic.mgc: ${TOOL_MKMAGIC}
|
2012-03-31 20:24:03 +02:00
|
|
|
${_MKTARGET_CREATE}
|
2012-05-02 13:23:57 +02:00
|
|
|
${TOOL_MKMAGIC} -C -m ${DIST}/magic/magdir
|
2012-03-31 20:24:03 +02:00
|
|
|
@mv magdir.mgc ${.TARGET}
|
|
|
|
|
|
|
|
|
|
.else
|
|
|
|
|
magic.mgc:
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.include <bsd.prog.mk>
|
