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,
46 sources, which is loosely defined as the things required to rebuild
47 the system to a useful state.
50 contains the source for the system documentation, excluding the manual
54 contains a tree that provides a consistent interface for building and
55 installing third party applications.
56 For more information about the ports build process, see
61 command is used in each of these directories to build and install the
62 things in that directory.
65 command in any directory or
66 subdirectory of those directories has the same effect as issuing the
67 same command in all subdirectories of that directory.
68 With no target specified, the things in that directory are just built.
70 A source tree is allowed to be read-only.
73 objects are usually built in a separate object directory hierarchy
74 specified by the environment variable
75 .Va MAKEOBJDIRPREFIX ,
81 For a given source directory, its canonical object directory
83 .Pa ${MAKEOBJDIRPREFIX}${.CURDIR}
89 .Pa /usr/obj${.CURDIR}
90 if this variable is not set.
91 Cross-builds set the object directory as described in the
96 The build may be controlled by defining
98 variables described in the
100 section below, and by the variables documented in
103 The following list provides the names and actions for the targets
104 supported by the build system:
105 .Bl -tag -width ".Cm cleandepend"
107 Remove any files created during the build process.
110 .Pa ${.OBJDIR}/${DEPENDFILE}
115 Remove the canonical object directory if it exists, or perform
116 actions equivalent to
117 .Dq Li "make clean cleandepend"
119 This target will also remove an
125 It is advisable to run
126 .Dq Li "make cleandir"
127 twice: the first invocation will remove the canonical object directory
128 and the second one will clean up
131 Generate a list of build dependencies in file
132 .Pa ${.OBJDIR}/${DEPENDFILE} .
134 Install the results of the build to the appropriate location in the
135 installation directory hierarchy specified in variable
138 Create the canonical object directory associated with the current
141 Create a symbolic link to the canonical object directory in
144 Generate a tags file using the program specified in the
148 The build system supports
154 The other supported targets under directory
157 .Bl -tag -width ".Cm distributeworld"
159 Spawn an interactive shell with environment variables set up for
160 cross-building the system.
161 The target architecture needs to be specified with
168 This target is only useful after a complete cross-toolchain including
169 the compiler, linker, assembler, headers and libraries has been
174 Build everything but the kernel, configure files in
178 The actual build location prefix used is
179 .Pa ${MAKEOBJDIRPREFIX}${.CURDIR}
180 for native builds, and
181 .Pa ${MAKEOBJDIRPREFIX}/${TARGET}${.CURDIR}
182 for cross builds and native builds with variable
183 .Va CROSS_BUILD_TESTING
186 Attempt to clean up targets built by a preceding
189 .It Cm distributeworld
190 Distribute everything compiled by a preceding
193 Files are placed in the directory hierarchy specified by
197 This target is used while building a release; see
200 Archive the results of
201 .Cm distributeworld ,
202 placing the results in
204 This target is used while building a release; see
207 Install everything built by a preceding
209 step into the directory hierarchy pointed to by
214 If installing onto an NFS file system and running
218 option, make sure that
220 is running on both client and server.
223 on how to make it start at boot time.
225 Create the build toolchain needed to build the rest of the system.
226 For cross-architecture builds, this step creates a cross-toolchain.
228 For each architecture,
233 for all kernels for that architecture,
236 This command takes a long time.
238 Get updated sources as configured in
241 Print a list of supported
245 pairs for world and kernel targets.
247 Execute the same targets as
249 In addition print a summary of all failed targets at the end and
250 exit with an error if there were any.
252 Create a build toolchain for each architecture supported by the build system.
255 Kernel specific build targets in
258 .Bl -tag -width ".Cm distributekernel"
260 Rebuild the kernel and the kernel modules.
262 Install the kernel and the kernel modules to directory
263 .Pa ${DESTDIR}/boot/kernel ,
264 renaming any pre-existing directory with this name to
266 if it contained the currently running kernel.
267 The target directory under
269 may be modified using the
275 .It Cm distributekernel
276 Install the kernel to the directory
277 .Pa ${DISTDIR}/kernel/boot/kernel .
278 This target is used while building a release; see
281 Archive the results of
282 .Cm distributekernel ,
283 placing the results in
285 This target is used while building a release; see
292 .It Cm kernel-toolchain
293 Rebuild the tools needed for kernel compilation.
294 Use this if you did not do a
297 .It Cm reinstallkernel
298 Reinstall the kernel and the kernel modules, overwriting the contents
299 of the target directory.
302 target, the target directory can be specified using the
308 Convenience targets for cleaning up the install destination directory
312 .Bl -tag -width ".Cm delete-old-libs"
314 Print a list of old files and directories in the system.
316 Delete obsolete base system files and directories interactively.
318 .Li -DBATCH_DELETE_OLD_FILES
319 is specified at the command line, the delete operation will be
326 should be set as with
327 .Dq Li "make installworld" .
328 .It Cm delete-old-libs
329 Delete obsolete base system libraries interactively.
330 This target should only be used if no 3rd party software uses these
333 .Li -DBATCH_DELETE_OLD_FILES
334 is specified at the command line, the delete operation will be
341 should be set as with
342 .Dq Li "make installworld" .
345 Variables that influence all builds include:
346 .Bl -tag -width ".Va MAKEOBJDIRPREFIX"
348 Defines a set of debugging flags that will be used to build all userland
357 targets install binaries from the current
360 so that debugging information is retained in the installed binaries.
362 The directory hierarchy prefix where built objects will be installed.
365 defaults to the empty string.
366 .It Va MAKEOBJDIRPREFIX
367 Defines the prefix for directory names in the tree of built objects.
371 This variable should only be set in the environment and not via
375 If defined, compiler warnings will not cause the build to halt,
376 even if the makefile says otherwise.
378 If defined, the build process will run the DTrace CTF conversion
379 tools on built objects.
380 Please note that this WITH_ option is handled differently than all
381 other WITH_ options (there is no
385 in the build system).
388 Additionally, builds in
390 are influenced by the following
393 .Bl -tag -width ".Va SUBDIR_OVERRIDE"
395 Overrides which kernel to build and install for the various kernel
400 If set, the build target
404 .Va NO_KERNELCONFIG ,
408 When set to a value other than
412 is set to the value of
415 If set, this variable supplies a list of additional directories to
416 build, relative to the root of the source tree.
417 .It Va SUBDIR_OVERRIDE
418 Override the default list of sub-directories and only build the
419 sub-directory named in this variable.
420 This variable is useful when debugging failed builds.
421 .Bd -literal -offset indent
422 make some-target SUBDIR_OVERRIDE=foo/bar
425 The target hardware platform.
426 This is analogous to the
429 This is necessary to cross-build some target architectures.
430 For example, cross-building for PC98 machines requires
431 .Va TARGET_ARCH Ns = Ns Li i386
433 .Va TARGET Ns = Ns Li pc98 .
436 defaults to the current hardware platform.
438 The target machine processor architecture.
439 This is analogous to the
442 Set this to cross-build for a different architecture.
445 defaults to the current machine architecture, unless
447 is also set, in which case it defaults to the appropriate
448 value for that platform.
449 Typically, one only needs to set
453 Builds under directory
455 are also influenced by defining one or more of the following symbols,
460 .Bl -tag -width ".Va -DNO_KERNELDEPEND"
462 If set, the build targets that clean parts of the object tree use the
468 If set, no object tree files are cleaned at all.
475 is set no kernel objects are cleaned either.
477 If set, the build process does not run the DTrace CTF conversion tools
480 If set, the build does not descend into the
482 subdirectory (i.e. manpages, locale data files, timezone data files and
485 files will not be rebuild from their sources).
486 .It Va NO_KERNELCLEAN
487 If set, the build process does not run
492 .It Va NO_KERNELCONFIG
493 If set, the build process does not run
498 .It Va NO_KERNELDEPEND
499 If set, the build process does not run
505 If set, the build process does not run
511 If set, the update process does not update the source of the
513 documentation as part of the
516 .It Va NO_PORTSUPDATE
517 If set, the update process does not update the Ports tree as part of the
521 If set, the update process does not update the www tree as part of the
526 Builds under directory
528 are influenced by the following
531 .Bl -tag -width ".Va DOC_LANG"
533 If set, restricts the documentation build to the language subdirectories
534 specified as its content.
535 The default action is to build documentation for all languages.
540 target are influenced by the following
543 .Bl -tag -width ".Va MAKE_JUST_KERNELS"
545 Pass the value of this variable to each
547 invocation used to build worlds and kernels.
548 This can be used to enable multiple jobs within a single architecture's build
549 while still building each architecture serially.
550 .It Va MAKE_JUST_KERNELS
551 Only build kernels for each supported architecture.
552 .It Va MAKE_JUST_WORLDS
553 Only build worlds for each supported architecture.
554 .It Va UNIVERSE_TARGET
555 Execute the specified
557 target for each supported architecture instead of the default action of
558 building a world and one or more kernels.
561 .Bl -tag -width ".Pa /usr/share/examples/etc/make.conf" -compact
562 .It Pa /usr/doc/Makefile
563 .It Pa /usr/doc/share/mk/doc.project.mk
564 .It Pa /usr/ports/Mk/bsd.port.mk
565 .It Pa /usr/ports/Mk/bsd.sites.mk
566 .It Pa /usr/share/examples/etc/make.conf
567 .It Pa /usr/src/Makefile
568 .It Pa /usr/src/Makefile.inc1
573 method of updating your system from the latest sources, please see the
578 The following sequence of commands can be used to cross-build the
579 system for the sparc64 architecture on an i386 host:
580 .Bd -literal -offset indent
582 make TARGET=sparc64 buildworld
583 make TARGET=sparc64 DESTDIR=/clients/sparc64 installworld
598 .An Mike W. Meyer Aq mwm@mired.org .