version 1.29, 2003/02/08 10:00:33 |
version 1.32, 2003/05/10 07:15:53 |
|
|
Default: Empty string if USETOOLS is ``yes''; unset other- |
Default: Empty string if USETOOLS is ``yes''; unset other- |
wise. |
wise. |
|
|
|
Note: build.sh will provide a default of destdir.MACHINE (in |
|
the top-level .OBJDIR) unless run in `expert' mode |
|
|
MAKECONF The name of the make(1) configuration file. Only settable in |
MAKECONF The name of the make(1) configuration file. Only settable in |
the process environment. |
the process environment. |
|
|
|
|
|
|
Default: Unset. |
Default: Unset. |
|
|
|
Note: build.sh will provide a default of releasedir (in |
|
the top-level .OBJDIR) unless run in `expert' mode |
|
|
UPDATE If set, then in addition to the effects described for |
UPDATE If set, then in addition to the effects described for |
UPDATE above, this implies the effects of NOCLEANDIR |
UPDATE above, this implies the effects of NOCLEANDIR |
(i.e., ``make cleandir'' is avoided). |
(i.e., ``make cleandir'' is avoided). |
|
|
distribution'' (as ``make build'' does not install all of |
distribution'' (as ``make build'' does not install all of |
the required files). |
the required files). |
|
|
|
sourcesets Create source sets of the source tree into |
|
RELEASEDIR/source/sets. |
|
|
release Do a ``make distribution'', build kernels, distribution me- |
release Do a ``make distribution'', build kernels, distribution me- |
dia, and install sets (this as per ``make sets''), and then |
dia, and install sets (this as per ``make sets''), and then |
package the system into a standard release layout as de- |
package the system into a standard release layout as de- |
|
|
|
|
sets Perform ``make sets''. |
sets Perform ``make sets''. |
|
|
|
sourcesets Perform ``make sourcesets''. |
|
|
The following command line options alter the behaviour of the above oper- |
The following command line options alter the behaviour of the above oper- |
ations: The following command line options alter the behaviour of the |
ations: The following command line options alter the behaviour of the |
build.sh operations described above: |
build.sh operations described above: |
|
|
Build a new toolchain, and use the new toolchain to configure and |
Build a new toolchain, and use the new toolchain to configure and |
build a new GENERIC kernel. |
build a new GENERIC kernel. |
|
|
2. ./build.sh -U -D /path/to/destdir distribution |
2. ./build.sh -U distribution |
|
|
Using unprivileged mode, build a complete distribution in |
Using unprivileged mode, build a complete distribution to a DESTDIR |
/path/to/destdir. |
directory that build.sh selects (and will display). |
|
|
3. # ./build.sh -U -D /path/to/destdir install=/ |
3. # ./build.sh -U install=/ |
|
|
As root, install to / the distribution that was built by example 2. |
As root, install to / the distribution that was built by example 2. |
Even though this is run as root, -U is required so that the permis- |
Even though this is run as root, -U is required so that the permis- |
sions stored in /path/to/destdir/METALOG are correctly applied to |
sions stored in DESTDIR/METALOG are correctly applied to the files |
the files as they're copied to /. |
as they're copied to /. |
|
|
4. ./build.sh -U -u -D /path/to/destdir -R /path/to/releasedir release |
4. ./build.sh -U -u release |
|
|
Using unprivileged mode, build a complete release in |
Using unprivileged mode, build a complete release to DESTDIR and |
/path/to/dir/releasedir. UPDATE (-u) is set to prevent the ``make |
RELEASEDIR directories that build.sh selects (and will display). |
cleandir'', so that if this is run after example 2, it doesn't need |
UPDATE (-u) is set to prevent the ``make cleandir'', so that if this |
to redo that portion of the release build. |
is run after example 2, it doesn't need to redo that portion of the |
|
release build. |
|
|
OBSOLETE VARIABLES |
OBSOLETE VARIABLES |
NBUILDJOBS Use the make(1) option -j, instead. |
NBUILDJOBS Use the make(1) option -j, instead. |
|
|
BUGS |
BUGS |
A few platforms are not yet using this build system. |
A few platforms are not yet using this build system. |
|
|
NetBSD February 8, 2003 10 |
NetBSD May 10, 2003 10 |