4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .Nd information on how to build the system
36 system and its applications are contained in three different directories,
42 These directories may be initially empty or non-existent until updated with
50 sources, which is loosely defined as the things required to rebuild
51 the system to a useful state.
54 contains the source for the system documentation, excluding the manual
58 contains a tree that provides a consistent interface for building and
59 installing third party applications.
60 For more information about the ports build process, see
65 command is used in each of these directories to build and install the
66 things in that directory.
69 command in any directory or
70 subdirectory of those directories has the same effect as issuing the
71 same command in all subdirectories of that directory.
72 With no target specified, the things in that directory are just built.
74 A source tree is allowed to be read-only.
77 objects are usually built in a separate object directory hierarchy
78 specified by the environment variable
79 .Va MAKEOBJDIRPREFIX ,
85 For a given source directory, its canonical object directory
87 .Pa ${MAKEOBJDIRPREFIX}${.CURDIR}
93 .Pa /usr/obj${.CURDIR}
94 if this variable is not set.
95 Cross-builds set the object directory as described in the
100 The build may be controlled by defining
102 variables described in the
104 section below, and by the variables documented in
107 The following list provides the names and actions for the targets
108 supported by the build system:
109 .Bl -tag -width ".Cm cleandepend"
111 Remove any files created during the build process.
114 .Pa ${.OBJDIR}/${DEPENDFILE}
119 Remove the canonical object directory if it exists, or perform
120 actions equivalent to
121 .Dq Li "make clean cleandepend"
123 This target will also remove an
129 It is advisable to run
130 .Dq Li "make cleandir"
131 twice: the first invocation will remove the canonical object directory
132 and the second one will clean up
135 Generate a list of build dependencies in file
136 .Pa ${.OBJDIR}/${DEPENDFILE} .
138 Install the results of the build to the appropriate location in the
139 installation directory hierarchy specified in variable
142 Create the canonical object directory associated with the current
145 Create a symbolic link to the canonical object directory in
148 Generate a tags file using the program specified in the
152 The build system supports
158 The other supported targets under directory
161 .Bl -tag -width ".Cm distributeworld"
163 Spawn an interactive shell with environment variables set up for
164 cross-building the system.
165 The target architecture needs to be specified with
172 This target is only useful after a complete cross-toolchain including
173 the compiler, linker, assembler, headers and libraries has been
178 Build everything but the kernel, configure files in
182 The actual build location prefix used is
183 .Pa ${MAKEOBJDIRPREFIX}${.CURDIR}
184 for native builds, and
185 .Pa ${MAKEOBJDIRPREFIX}/${TARGET}${.CURDIR}
186 for cross builds and native builds with variable
187 .Va CROSS_BUILD_TESTING
190 Attempt to clean up targets built by a preceding
193 .It Cm distributeworld
194 Distribute everything compiled by a preceding
197 Files are placed in the directory hierarchy specified by
201 This target is used while building a release; see
204 Install everything built by a preceding
206 step into the directory hierarchy pointed to by
211 If installing onto an NFS file system and running
215 option, make sure that
217 is running on both client and server.
220 on how to make it start at boot time.
222 Create the build toolchain needed to build the rest of the system.
223 For cross-architecture builds, this step creates a cross-toolchain.
225 For each architecture,
230 for all kernels for that architecture,
233 This command takes a long time.
235 Get updated sources as configured in
238 Execute the same targets as
240 In addition print a summary of all failed targets at the end and
241 exit with an error if there were any.
243 Create a build toolchain for each architecture supported by the build system.
246 Kernel specific build targets in
249 .Bl -tag -width ".Cm reinstallkernel"
251 Rebuild the kernel and the kernel modules.
253 Install the kernel and the kernel modules to directory
254 .Pa ${DESTDIR}/boot/kernel ,
255 renaming any pre-existing directory with this name to
257 if it contained the currently running kernel.
258 The target directory under
260 may be modified using the
271 .It Cm kernel-toolchain
272 Rebuild the tools needed for kernel compilation.
273 Use this if you did not do a
276 .It Cm reinstallkernel
277 Reinstall the kernel and the kernel modules, overwriting the contents
278 of the target directory.
281 target, the target directory can be specified using the
287 Convenience targets for cleaning up the install destination directory
291 .Bl -tag -width ".Cm delete-old-libs"
293 Print a list of old files and directories in the system.
295 Delete obsolete base system files and directories interactively.
297 .Li -DBATCH_DELETE_OLD_FILES
298 is specified at the command line, the delete operation will be
305 should be set as with
306 .Dq Li "make installworld" .
307 .It Cm delete-old-libs
308 Delete obsolete base system libraries interactively.
309 This target should only be used if no 3rd party software uses these
312 .Li -DBATCH_DELETE_OLD_FILES
313 is specified at the command line, the delete operation will be
320 should be set as with
321 .Dq Li "make installworld" .
324 Variables that influence all builds include:
325 .Bl -tag -width ".Va MAKEOBJDIRPREFIX"
327 Defines a set of debugging flags that will be used to build all userland
336 targets install binaries from the current
339 so that debugging information is retained in the installed binaries.
341 The directory hierarchy prefix where built objects will be installed.
344 defaults to the empty string.
345 .It Va MAKEOBJDIRPREFIX
346 Defines the prefix for directory names in the tree of built objects.
350 This variable should only be set in the environment and not via
354 If defined, compiler warnings will not cause the build to halt,
355 even if the makefile says otherwise.
358 Additionally, builds in
360 are influenced by the following
363 .Bl -tag -width ".Va SUBDIR_OVERRIDE"
365 Overrides which kernel to build and install for the various kernel
370 If set, the build target
374 .Va NO_KERNELCONFIG ,
378 When set to a value other than
382 is set to the value of
385 If set, this variable supplies a list of additional directories to
386 build, relative to the root of the source tree.
388 A list of ports with kernel modules that should be built and installed
394 .Bd -literal -offset indent
395 make PORTS_MODULES=emulators/kqemu-kmod kernel
397 .It Va SUBDIR_OVERRIDE
398 Override the default list of sub-directories and only build the
399 sub-directory named in this variable.
400 This variable is useful when debugging failed builds.
401 .Bd -literal -offset indent
402 make some-target SUBDIR_OVERRIDE=foo/bar
405 The target hardware platform.
406 This is analogous to the
409 This is necessary to cross-build some target architectures.
410 For example, cross-building for PC98 machines requires
411 .Va TARGET_ARCH Ns = Ns Li i386
413 .Va TARGET Ns = Ns Li pc98 .
416 defaults to the current hardware platform.
418 The target machine processor architecture.
419 This is analogous to the
422 Set this to cross-build for a different architecture.
425 defaults to the current machine architecture, unless
427 is also set, in which case it defaults to the appropriate
428 value for that platform.
429 Typically, one only needs to set
433 Builds under directory
435 are also influenced by defining one or more of the following symbols,
440 .Bl -tag -width ".Va -DNO_KERNELDEPEND"
442 If set, the build targets that clean parts of the object tree use the
448 If set, no object tree files are cleaned at all.
455 is set no kernel objects are cleaned either.
457 If set, the build process does not run the DTrace CTF conversion tools
460 If set, the build does not descend into the
462 subdirectory (i.e., manpages, locale data files, timezone data files and
465 files will not be rebuild from their sources).
466 .It Va NO_KERNELCLEAN
467 If set, the build process does not run
472 .It Va NO_KERNELCONFIG
473 If set, the build process does not run
478 .It Va NO_KERNELDEPEND
479 If set, the build process does not run
485 If set, the build process does not run
491 If set, the update process does not update the source of the
493 documentation as part of the
496 .It Va NO_PORTSUPDATE
497 If set, the update process does not update the Ports tree as part of the
502 Builds under directory
504 are influenced by the following
507 .Bl -tag -width ".Va DOC_LANG"
509 If set, restricts the documentation build to the language subdirectories
510 specified as its content.
511 The default action is to build documentation for all languages.
516 target are influenced by the following
519 .Bl -tag -width ".Va MAKE_JUST_KERNELS"
521 Pass the value of this variable to each
523 invocation used to build worlds and kernels.
524 This can be used to enable multiple jobs within a single architecture's build
525 while still building each architecture serially.
526 .It Va MAKE_JUST_KERNELS
527 Only build kernels for each supported architecture.
528 .It Va MAKE_JUST_WORLDS
529 Only build worlds for each supported architecture.
530 .It Va UNIVERSE_TARGET
531 Execute the specified
533 target for each supported architecture instead of the default action of
534 building a world and one or more kernels.
537 .Bl -tag -width ".Pa /usr/share/examples/etc/make.conf" -compact
538 .It Pa /usr/doc/Makefile
539 .It Pa /usr/doc/share/mk/doc.project.mk
540 .It Pa /usr/ports/Mk/bsd.port.mk
541 .It Pa /usr/ports/Mk/bsd.sites.mk
542 .It Pa /usr/share/examples/etc/make.conf
543 .It Pa /usr/src/Makefile
544 .It Pa /usr/src/Makefile.inc1
549 method of updating your system from the latest sources, please see the
554 The following sequence of commands can be used to cross-build the
555 system for the sparc64 architecture on an i386 host:
556 .Bd -literal -offset indent
558 make TARGET=sparc64 buildworld
559 make TARGET=sparc64 DESTDIR=/clients/sparc64 installworld
576 .An Mike W. Meyer Aq mwm@mired.org .