2005-04-21 16:53:53 +02:00
|
|
|
# Makefile for the kernel image.
|
2011-04-27 15:00:52 +02:00
|
|
|
.include <bsd.own.mk>
|
|
|
|
.include "nbsd.config"
|
2005-08-23 14:53:35 +02:00
|
|
|
|
2011-06-24 17:20:25 +02:00
|
|
|
.include <bsd.own.mk>
|
2012-06-26 11:31:30 +02:00
|
|
|
.include <bsd.sys.mk>
|
2011-06-24 17:20:25 +02:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
u=/usr
|
|
|
|
MDEC= /usr/mdec
|
2011-04-21 15:20:55 +02:00
|
|
|
GEN_FILES= *.bak image kernel *.iso *.iso.gz cdfdimage rootimage src
|
2005-04-21 16:53:53 +02:00
|
|
|
|
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
|
|
|
# LSC detect where were built the objects files
|
2012-11-01 22:55:12 +01:00
|
|
|
PROGROOT:= ..
|
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
|
|
|
.if "${MAKEOBJDIR:S,${.CURDIR},,}" != ""
|
|
|
|
PROGROOT:= ${MAKEOBJDIR:S,releasetools,,}
|
|
|
|
.endif
|
|
|
|
|
2005-08-23 14:53:35 +02:00
|
|
|
# Specify the programs that are part of the system image.
|
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
|
|
|
KERNEL= ${PROGROOT}/kernel/kernel
|
2012-01-30 13:27:23 +01:00
|
|
|
# PROGRAMS are in the order they should be loaded by boot
|
2013-01-13 17:20:11 +01:00
|
|
|
PROGRAMS+= ${PROGROOT}/servers/ds/ds
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/rs/rs
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/pm/pm
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/sched/sched
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/vfs/vfs
|
|
|
|
PROGRAMS+= ${PROGROOT}/drivers/memory/memory
|
|
|
|
PROGRAMS+= ${PROGROOT}/drivers/log/log
|
|
|
|
PROGRAMS+= ${PROGROOT}/drivers/tty/tty
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/mfs/mfs
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/vm/vm
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/pfs/pfs
|
|
|
|
PROGRAMS+= ${PROGROOT}/servers/init/init
|
2005-08-03 18:06:35 +02:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
usage:
|
|
|
|
@echo " " >&2
|
2005-05-02 16:30:04 +02:00
|
|
|
@echo "Master Makefile to create new MINIX configuration." >& 2
|
|
|
|
@echo "Root privileges are required." >&2
|
|
|
|
@echo " " >&2
|
2005-04-21 16:53:53 +02:00
|
|
|
@echo "Usage:" >&2
|
2005-05-19 11:36:44 +02:00
|
|
|
@echo " make includes # Install include files" >&2
|
2005-07-26 14:51:35 +02:00
|
|
|
@echo " make depend # Generate dependency files" >&2
|
2005-08-23 14:53:35 +02:00
|
|
|
@echo " make services # Compile and install all services" >&2
|
2005-05-04 11:30:49 +02:00
|
|
|
@echo " make install # Make image, and install to hard disk" >&2
|
2005-04-21 16:53:53 +02:00
|
|
|
@echo " make hdboot # Make image, and install to hard disk" >&2
|
|
|
|
@echo " make bootable # Make hard disk bootable" >&2
|
2011-04-27 15:00:52 +02:00
|
|
|
@echo " make nbsd_fetch # Download current NetBSD reference sources" >&2
|
|
|
|
@echo " make nbsd_diff # Update minix-port.patch in NetBSD sources" >&2
|
2005-04-21 16:53:53 +02:00
|
|
|
@echo " make clean # Remove all compiler results, except libs" >&2
|
|
|
|
@echo " " >&2
|
|
|
|
@echo "To create a fresh MINIX configuration, try:" >&2
|
2005-08-23 14:53:35 +02:00
|
|
|
@echo " make clean install # new boot image" >&2
|
2005-04-21 16:53:53 +02:00
|
|
|
@echo " " >&2
|
|
|
|
|
2012-05-01 15:04:26 +02:00
|
|
|
all: services
|
2006-03-13 09:47:05 +01:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
# rebuild the program or system libraries
|
2005-05-19 11:36:44 +02:00
|
|
|
includes:
|
2013-04-05 14:22:46 +02:00
|
|
|
${MAKE} -C ../ includes
|
|
|
|
|
|
|
|
libraries: includes
|
|
|
|
${MAKE} -C ../ do-lib
|
2005-05-19 11:36:44 +02:00
|
|
|
|
2011-04-21 15:20:55 +02:00
|
|
|
depend: includes .gitignore
|
2013-04-05 14:22:46 +02:00
|
|
|
${MAKE} -C ../ depend
|
2005-06-24 18:25:12 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
kernel: libraries
|
|
|
|
${MAKE} -C ../kernel
|
2011-04-21 15:20:55 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
servers: libraries
|
|
|
|
${MAKE} -C ../servers all install
|
2010-08-26 21:54:49 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
drivers: libraries servers
|
|
|
|
${MAKE} -C ../drivers all install
|
2010-08-26 21:54:49 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
services: kernel servers drivers
|
2010-08-26 21:54:49 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
.gitignore: Makefile
|
|
|
|
echo ${GEN_FILES} | tr ' ' '\n' >.gitignore
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
# make bootable and place system images
|
|
|
|
bootable:
|
2012-11-23 21:35:59 +01:00
|
|
|
exec su root mkboot bootable ${DESTDIR}
|
2005-04-21 16:53:53 +02:00
|
|
|
|
2013-04-05 14:22:46 +02:00
|
|
|
hdboot install: services .WAIT do-hdboot
|
2012-11-15 13:53:52 +01:00
|
|
|
|
|
|
|
do-hdboot:
|
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
|
|
|
@rm -rf ${DESTDIR}/boot/minix/.temp/
|
2012-06-26 11:31:30 +02:00
|
|
|
${INSTALL_DIR} ${DESTDIR}/boot/minix/.temp
|
2012-01-30 13:27:23 +01:00
|
|
|
# mod_0 is used to make alphabetical order equal to the boot order
|
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
|
|
|
@n=0; \
|
2012-01-30 13:27:23 +01:00
|
|
|
for i in ${PROGRAMS}; \
|
|
|
|
do \
|
2012-06-25 11:15:27 +02:00
|
|
|
n=`expr $$n + 1`; \
|
2012-01-30 13:27:23 +01:00
|
|
|
[ "$$n" -ge 10 ] && prefix="mod" || prefix="mod0"; \
|
2012-05-07 13:38:39 +02:00
|
|
|
newname="${DESTDIR}/boot/minix/.temp/$${prefix}$${n}_`basename $$i`"; \
|
2012-06-26 11:31:30 +02:00
|
|
|
${INSTALL} $$i $$newname; \
|
2012-01-30 13:27:23 +01:00
|
|
|
done
|
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
|
|
|
@cp ${PROGROOT}/kernel/kernel ${DESTDIR}/boot/minix/.temp/
|
2012-10-26 15:22:39 +02:00
|
|
|
@if [ "${MKINSTALLBOOT:Uno}" != "no" ] ; then \
|
2012-07-05 17:32:15 +02:00
|
|
|
${STRIP} -s ${DESTDIR}/boot/minix/.temp/* ; \
|
|
|
|
gzip ${DESTDIR}/boot/minix/.temp/mod* ; \
|
2012-11-23 21:35:59 +01:00
|
|
|
${HOST_SH} mkboot hdboot ${DESTDIR}; \
|
2012-06-26 11:31:30 +02:00
|
|
|
${HOST_SH} ../commands/update_bootcfg/update_bootcfg.sh;\
|
2012-06-15 16:13:12 +02:00
|
|
|
else \
|
|
|
|
${INSTALL_DIR} ${DESTDIR}/multiboot; \
|
2012-06-26 11:31:30 +02:00
|
|
|
${INSTALL} ${DESTDIR}/boot/minix/.temp/* ${DESTDIR}/multiboot; \
|
2012-06-15 16:13:12 +02:00
|
|
|
fi
|
2005-04-21 16:53:53 +02:00
|
|
|
|
2011-04-27 15:00:52 +02:00
|
|
|
# download and update NetBSD reference sources.
|
|
|
|
nbsd_fetch:
|
2011-12-14 01:14:11 +01:00
|
|
|
export CVS_RSH=ssh; \
|
2012-12-03 15:06:12 +01:00
|
|
|
export OLDPWD=`pwd`; \
|
2011-12-14 01:14:11 +01:00
|
|
|
echo "retrieving hierarchies from ${NBSD_CVSROOT}"; \
|
2012-03-13 02:07:22 +01:00
|
|
|
IFS=,; \
|
2012-12-03 15:06:12 +01:00
|
|
|
cd ..; \
|
|
|
|
cat releasetools/nbsd_ports | grep -v '^#' | while read port ; \
|
2012-03-13 02:07:22 +01:00
|
|
|
do set $$port; \
|
|
|
|
date=$$1; minixpath=$$2; origpath=$$3; \
|
|
|
|
if [ $$# -lt 3 ]; then origpath=$$2; fi; \
|
|
|
|
echo "retrieving $$origpath .."; \
|
2012-12-03 15:06:12 +01:00
|
|
|
cvs -q -d ${NBSD_CVSROOT} co -N -D "$$date UTC" -d nbsdsrc "src/$$origpath" ; \
|
|
|
|
done; \
|
|
|
|
cd $${OLDPWD};
|
2011-04-27 15:00:52 +02:00
|
|
|
|
|
|
|
nbsd_diff:
|
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
|
|
|
find .. -name minix-port.patch | xargs rm
|
2012-03-13 02:07:22 +01:00
|
|
|
cat nbsd_ports | grep -v '^#' | \
|
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
|
|
|
( cd .. && awk -F, '{ minixpath=$$2; origpath=$$3; if(NF < 3) { origpath=$$2; } system("sh releasetools/nbsd_diff.sh " \
|
2012-03-13 02:07:22 +01:00
|
|
|
"nbsdsrc/src/"origpath" "minixpath" "minixpath"/minix-port.patch");}' )
|
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
|
|
|
find .. -name minix-port.patch | xargs wc -l | sort -n
|
2011-04-27 15:00:52 +02:00
|
|
|
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
# clean up compile results
|
|
|
|
clean:
|
2013-04-05 14:22:46 +02:00
|
|
|
${MAKE} -C ../lib $@
|
|
|
|
${MAKE} -C ../kernel $@
|
|
|
|
${MAKE} -C ../servers $@
|
|
|
|
${MAKE} -C ../drivers $@
|
|
|
|
rm -rf ${GEN_FILES}
|
|
|
|
|
|
|
|
cleandir:
|
|
|
|
${MAKE} -C ../lib $@
|
|
|
|
${MAKE} -C ../kernel $@
|
|
|
|
${MAKE} -C ../servers $@
|
|
|
|
${MAKE} -C ../drivers $@
|