1 .\" Copyright (c) 2002 Murray Stokely <murray@FreeBSD.org>
2 .\" All rights reserved.
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 "release building infrastructure"
35 provides a complete build environment suitable for users to make
39 All of the tools necessary to build a release are available from the
41 source code repository in
43 A complete release can actually be built with only a single command,
44 including the creation of ISO images suitable for burning to CD-ROM,
45 memory stick images, and an FTP install directory.
46 This command is aptly named
47 .Dq Li "make release" .
49 For some users, it may be desirable to provide an absolutely clean
50 build environment, with no local modifications to the source tree or to
52 and with clean checkouts of specific versions of the doc, src, and ports
54 For this purpose, a script
55 .Pq Pa src/release/release.sh
56 is provided to automate these checkouts and then execute
61 Before attempting to build a release, the user is expected to be
62 familiar with the contents of
64 and should have experience upgrading systems from source.
66 The release build process requires that
68 be populated with the output of
69 .Dq Li "make buildworld"
71 .Dq Li "make buildkernel" .
72 This is necessary to provide the object files for the release or, when
75 so that the object files for a complete system can be installed into a clean
79 If the target release build is for a different architecture or machine type,
84 variables must be used.
87 variables for more information.
89 The release procedure on some architectures may also require that the
91 (memory disk) device driver be present in the kernel
92 .Pq either by being compiled in or available as a module .
94 This document does not cover source code management, quality
95 assurance, or other aspects of the release engineering process.
96 .Sh CLEAN RELEASE GENERATION
99 are produced in a totally clean environment to
100 ensure consistency between the versions of the src, ports, and doc trees
101 and to avoid contamination from the host system
102 .Po such as local patches, changes
107 This is accomplished using the wrapper script
108 .Pa src/release/release.sh .
111 .Op Fl c Ar release.conf
122 .Dq Li "make buildworld"
124 .Dq Li "make installworld"
129 .Dq Li "make release"
132 environment and places the result in
137 configuration file supports the following variables:
140 The directory within which the release will be built.
141 .It Va CHROOT_MAKEENV
144 arguments to pass through, which directly affect the
145 tuning of the build chroot.
149 host used to check out the various trees.
151 .Pa svn://svn.FreeeBSD.org .
171 The target machine type for cross-building a release.
173 The target machine architecture for cross-building a release.
175 For the supported list of
179 combinations, consult the output of
184 The target kernel configuration to use.
189 entries may be specified.
193 to use for the release build.
196 to prevent polluting the release with local system changes.
200 to use for the release build.
203 to prevent polluting the release with local system changes.
205 Additional flags to pass to
208 Additional flags to pass to
213 Defaults to setting the number of
217 to the number of CPUs available on a SMP-capable system.
219 Additional flags to pass to
224 Defaults to setting the number of
228 to half the number of CPUs available on a SMP-capable system.
230 Set to a non-empty value to skip the
237 distribution package from being created.
239 Set to a non-empty value to skip the
246 distribution package from being created.
247 Setting this also sets
250 Set to a non-empty value to include the
254 The command run to obtain the source trees.
256 .Qq Cm svn checkout .
257 .It Va CHROOTBUILD_SKIP
265 build environment setup are skipped.
266 This is intended solely for cases where the
268 userland are provided by alternate means.
273 variables are relevant only to release builds for embedded systems:
276 Set to a non-null value to enable functionality for embedded device
278 .Pq This option is considered highly experimental.
289 must also be defined.
290 When the build environment is created,
292 runs a separate build script located in an architecture-specific
294 .Pa src/release/${XDEV}/ .
296 Set to the list of any ports that are required for the target device
301 port is built by default.
303 Set to the source URL for the Crochet build tool.
305 Set to the subversion branch from
311 Set to the source URL of u-boot, if required.
313 Set to the subversion branch from
319 Set to the target directory within
322 .Va ${UBOOTSRC}/${UBOOTBRANCH} .
326 .Pq Pa src/release/Makefile
328 Most developers will only be concerned with the
333 .\" XXX: Some sort of introduction to this list? All the others have one.
334 .Bl -tag -width ".Cm packagesystem"
336 Meta-target to build all release media and distributions applicable to this
339 Copy all produced release media to
342 Builds installation CD-ROM images. On some systems, this may require that
345 .Pq Pa sysutils/cdrtools
346 and possibly that the
348 (memory disk) device driver be present in the kernel
349 (either by being compiled in or available as a module). This target
350 produces files called
356 Builds installation DVD-ROM images.
359 (memory disk) device driver be present in the kernel
360 (either by being compiled in or available as a module).
361 This target produces the
365 Builds an installation memory stick image named
367 Not applicable on all platforms. Requires that the
370 device driver be present in the kernel
371 .Pq either by being compiled in or available as a module .
375 with the exception that the installation distribution sets
378 Creates a directory named
380 containing the distribution files used in network installations
381 and suitable for upload to an FTP mirror.
384 Major subtargets called by targets above:
385 .Bl -tag -width ".Cm packagesystem"
387 Generates all the distribution archives
388 .Pq base, kernel, ports, doc
389 applicable on this platform.
391 Builds a bootable installation system containing all the distribution files
394 target, and suitable for imaging by the
401 Builds the release documentation.
402 This includes the release notes,
403 hardware guide, and installation instructions.
404 Other documentation, such as the Handbook,
412 .Bl -tag -width ".Ev TARGET_ARCH"
414 Optional base name for generated media images
415 .Pq e.g., FreeBSD-9.0-RC2-amd64 .
416 Defaults to the output of
417 .Ic `uname -s`-`uname -r`-`uname -p`
420 Location of a directory containing the src tree.
421 By default, the directory
422 above the one containing the makefile
425 Location of a directory containing the ports tree.
428 If it is unset or cannot be found, ports will not be included in the release.
430 Location of a directory containing the doc tree.
433 If it is unset or cannot be found, most documentation will not be included in
438 If defined, the Ports Collection will be omitted from the release.
440 If set, do not include system source code in the release.
442 If defined, the XML-based documentation from the
444 Documentation Project will not be built.
447 distribution will still be created with the minimal documentation set
451 The target hardware platform.
452 This is analogous to the
455 This is necessary to cross-build some target architectures.
456 For example, cross-building for PC98 machines requires
457 .Va TARGET_ARCH Ns = Ns Li i386
459 .Va TARGET Ns = Ns Li pc98 .
462 defaults to the current hardware platform.
464 The target machine processor architecture.
465 This is analogous to the
468 Set this to cross-build for a different architecture.
471 defaults to the current machine architecture, unless
473 is also set, in which case it defaults to the appropriate
474 value for that platform.
475 Typically, one only needs to set
480 .It Pa /usr/doc/Makefile
481 .It Pa /usr/doc/share/mk/doc.project.mk
482 .It Pa /usr/ports/Mk/bsd.port.mk
483 .It Pa /usr/ports/Mk/bsd.sites.mk
484 .It Pa /usr/share/examples/etc/make.conf
485 .It Pa /usr/src/Makefile
486 .It Pa /usr/src/Makefile.inc1
487 .It Pa /usr/src/release/Makefile
488 .It Pa /usr/src/release/release.sh
489 .It Pa /usr/src/release/release.conf.sample
492 The following sequence of commands can be used to build a
493 .Dq "-CURRENT snapshot":
494 .Bd -literal -offset indent
496 svn co svn://svn.freebsd.org/base/head src
498 make buildworld buildkernel
501 make install DESTDIR=/var/freebsd-snapshot
504 After running these commands, all produced distribution files (tarballs
505 for FTP, CD-ROM images, etc.) are available in the
506 .Pa /var/freebsd-snapshot
509 The following sequence of commands can be used to build a
510 .Dq "-CURRENT snapshot"
511 in a clean environment, including ports and documentation:
512 .Bd -literal -offset indent
517 Optionally, a configuration file can be used customize the release build,
518 such as the subversion revision to use, the branch of the subversion tree for
523 .Bd -literal -offset indent
525 sh release.sh -c $HOME/release.conf
528 After running these commands, all prepared release files are available in the
531 The target directory can be changed by specifying the
539 .Xr svn 1 Pq Pa ports/devel/subversion ,
549 .%T "FreeBSD Release Engineering"
550 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/
553 .%T "FreeBSD Release Engineering of Third Party Packages"
554 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/
557 .%T "FreeBSD Developers' Handbook"
558 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/
563 used a manual checklist, compiled by
565 to produce a release.
566 Apart from being incomplete, the list put a lot of specific demands on
567 available file systems and was quite torturous to execute.
571 release engineering effort, significant
572 effort was spent getting
573 .Pa src/release/Makefile
574 into a shape where it could at least automate most of the tediousness
575 of building a release in a sterile environment.
580 .Pa src/release/Makefile
581 was overhauled and the wrapper script
582 .Pa src/release/generate-release.sh
583 introduced to support the introduction of a new installer.
588 .Pa src/release/release.sh
589 was introduced to support per-build configuration files.
590 .Pa src/release/release.sh
591 is heavily based on the
592 .Pa src/release/generate-release.sh
595 At near 1000 revisions spread over multiple branches, the
598 .Pa src/release/Makefile
599 contains a vivid historical record of some
600 of the hardships release engineers go through.
602 .Pa src/release/Makefile
603 was originally written by
608 .An Poul-Henning Kamp .
610 This manual page was originally written by
611 .An Murray Stokely Aq murray@FreeBSD.org .
614 .An Nathan Whitehorn Aq nwhitehorn@FreeBSD.org
616 .Fa generate-release.sh
621 It was later updated by
622 .An Glen Barber Aq gjb@FreeBSD.org