2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: README,v 1.13 2013/08/06 22:33:59 soren Exp $
|
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
|
|
|
|
|
|
|
|
the scripts should be run from the directory where they reside.
|
|
|
|
|
|
|
|
|
|
makeflist: output the list of files that should be in a
|
|
|
|
|
distribution, according to the contents of the
|
|
|
|
|
'lists' directory.
|
|
|
|
|
|
|
|
|
|
checkflist: check the file list (as internally generated
|
|
|
|
|
by makeflist) against the tree living in $DESTDIR.
|
|
|
|
|
(that tree should be made with 'make distribution'.)
|
|
|
|
|
|
|
|
|
|
maketars: make tarballs of the various sets in the distribution,
|
|
|
|
|
based on the contents of the lists, the tree in
|
|
|
|
|
$DESTDIR, and put the tarballs in $RELEASEDIR.
|
|
|
|
|
Note that this script _doesn't_ create the 'secr'
|
|
|
|
|
distribution, because (for now) it requires
|
|
|
|
|
manual intervention to get the binaries right...
|
|
|
|
|
(i'll add another script to create that dist, later.)
|
|
|
|
|
|
|
|
|
|
what's in 'lists':
|
|
|
|
|
|
|
|
|
|
lists describing file sets. There are two sets of lists per file
|
|
|
|
|
set: machine dependent and machine-independent files. (there's
|
|
|
|
|
also another file in the 'man' dir, which is used by the 'man'
|
|
|
|
|
and 'misc' sets, but that's explained later.)
|
|
|
|
|
|
|
|
|
|
There is one machine-independent file, named "mi". There are
|
|
|
|
|
N machine-dependent files (one per architecture), named "md.${ARCH}".
|
|
|
|
|
|
|
|
|
|
the sets are as follows:
|
|
|
|
|
|
|
|
|
|
base: the base binary set. excludes everything described
|
|
|
|
|
below.
|
|
|
|
|
|
|
|
|
|
comp: compiler tools. All of the tools relating to C, C++,
|
|
|
|
|
and FORTRAN (yes, there are two!) that are in the
|
|
|
|
|
tree. This includes includes, the linker, tool chain,
|
|
|
|
|
and the .a versions of the libraries. (obviously,
|
|
|
|
|
base includes ldd, ld.so, and the shared versions.
|
|
|
|
|
base also includes 'cpp', because that's used by X11.)
|
|
|
|
|
includes the man pages for all the binaries contained
|
|
|
|
|
within. Also, includes all library and system call
|
|
|
|
|
manual pages.
|
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
debug: Debugging libraries (_g.a/MKDEBUGLIB) and (.debug/MKDEBUG)
|
|
|
|
|
binaries.
|
|
|
|
|
|
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
|
|
|
etc: /etc, and associated files (/var/cron/tabs, /root,
|
|
|
|
|
etc.). things that shouldn't be blindly reinstalled
|
|
|
|
|
on an upgrade.
|
|
|
|
|
|
|
|
|
|
games: the games and their man pages.
|
|
|
|
|
|
|
|
|
|
man: all of the man pages for the system, except those
|
|
|
|
|
listed elsewhere (e.g. in comp, games, misc, text).
|
|
|
|
|
Includes machine-dependent man pages for this CPU.
|
|
|
|
|
|
|
|
|
|
misc: share/dict, share/doc, and the machine-dependent
|
|
|
|
|
man pages for other CPUs which happen to always
|
|
|
|
|
be installed.
|
|
|
|
|
|
|
|
|
|
modules: stand/${MACHINE}/${OSRELEASE}/modules kernel modules
|
|
|
|
|
|
|
|
|
|
tests: unit, regression, integration and stress tests for the
|
|
|
|
|
whole system.
|
|
|
|
|
|
|
|
|
|
text: text processing tools. groff and all of its friends.
|
|
|
|
|
includes man pages for all bins contained within.
|
|
|
|
|
|
|
|
|
|
Each set must contain "./etc/mtree/set.<set name>" within the mi
|
|
|
|
|
list. Failure to add this will break unprivileged builds.
|