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.
345 (memory disk) device driver be present in the kernel
346 (either by being compiled in or available as a module).
347 This target produces files called
353 Builds installation DVD-ROM images.
356 (memory disk) device driver be present in the kernel
357 (either by being compiled in or available as a module).
358 This target produces the
362 Builds an installation memory stick image named
364 Not applicable on all platforms.
368 device driver be present in the kernel
369 .Pq either by being compiled in or available as a module .
373 with the exception that the installation distribution sets
376 Creates a directory named
378 containing the distribution files used in network installations
379 and suitable for upload to an FTP mirror.
382 Major subtargets called by targets above:
383 .Bl -tag -width ".Cm packagesystem"
385 Generates all the distribution archives
386 .Pq base, kernel, ports, doc
387 applicable on this platform.
389 Builds a bootable installation system containing all the distribution files
392 target, and suitable for imaging by the
399 Builds the release documentation.
400 This includes the release notes,
401 hardware guide, and installation instructions.
402 Other documentation, such as the Handbook,
410 .Bl -tag -width ".Ev TARGET_ARCH"
412 Optional base name for generated media images
413 .Pq e.g., FreeBSD-9.0-RC2-amd64 .
414 Defaults to the output of
415 .Ic `uname -s`-`uname -r`-`uname -p`
418 Location of a directory containing the src tree.
419 By default, the directory
420 above the one containing the makefile
423 Location of a directory containing the ports tree.
426 If it is unset or cannot be found, ports will not be included in the release.
428 Location of a directory containing the doc tree.
431 If it is unset or cannot be found, most documentation will not be included in
436 If defined, the Ports Collection will be omitted from the release.
438 If set, do not include system source code in the release.
440 If defined, the XML-based documentation from the
442 Documentation Project will not be built.
445 distribution will still be created with the minimal documentation set
449 The target hardware platform.
450 This is analogous to the
453 This is necessary to cross-build some target architectures.
454 For example, cross-building for PC98 machines requires
455 .Ev TARGET_ARCH Ns = Ns Li i386
457 .Ev TARGET Ns = Ns Li pc98 .
460 defaults to the current hardware platform.
462 The target machine processor architecture.
463 This is analogous to the
466 Set this to cross-build for a different architecture.
469 defaults to the current machine architecture, unless
471 is also set, in which case it defaults to the appropriate
472 value for that platform.
473 Typically, one only needs to set
477 .Bl -tag -compact -width Pa
478 .It Pa /usr/doc/Makefile
479 .It Pa /usr/doc/share/mk/doc.project.mk
480 .It Pa /usr/ports/Mk/bsd.port.mk
481 .It Pa /usr/ports/Mk/bsd.sites.mk
482 .It Pa /usr/share/examples/etc/make.conf
483 .It Pa /usr/src/Makefile
484 .It Pa /usr/src/Makefile.inc1
485 .It Pa /usr/src/release/Makefile
486 .It Pa /usr/src/release/release.sh
487 .It Pa /usr/src/release/release.conf.sample
490 The following sequence of commands can be used to build a
491 .Dq "-CURRENT snapshot":
492 .Bd -literal -offset indent
494 svn co svn://svn.freebsd.org/base/head src
496 make buildworld buildkernel
499 make install DESTDIR=/var/freebsd-snapshot
502 After running these commands, all produced distribution files (tarballs
503 for FTP, CD-ROM images, etc.) are available in the
504 .Pa /var/freebsd-snapshot
507 The following sequence of commands can be used to build a
508 .Dq "-CURRENT snapshot"
509 in a clean environment, including ports and documentation:
510 .Bd -literal -offset indent
515 Optionally, a configuration file can be used customize the release build,
516 such as the subversion revision to use, the branch of the subversion tree for
521 .Bd -literal -offset indent
523 sh release.sh -c $HOME/release.conf
526 After running these commands, all prepared release files are available in the
529 The target directory can be changed by specifying the
537 .Xr svn 1 Pq Pa ports/devel/subversion ,
547 .%T "FreeBSD Release Engineering"
548 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/
551 .%T "FreeBSD Release Engineering of Third Party Packages"
552 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng-packages/
555 .%T "FreeBSD Developers' Handbook"
556 .%U http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/
561 used a manual checklist, compiled by
563 to produce a release.
564 Apart from being incomplete, the list put a lot of specific demands on
565 available file systems and was quite torturous to execute.
569 release engineering effort, significant
570 effort was spent getting
571 .Pa src/release/Makefile
572 into a shape where it could at least automate most of the tediousness
573 of building a release in a sterile environment.
578 .Pa src/release/Makefile
579 was overhauled and the wrapper script
580 .Pa src/release/generate-release.sh
581 introduced to support the introduction of a new installer.
586 .Pa src/release/release.sh
587 was introduced to support per-build configuration files.
588 .Pa src/release/release.sh
589 is heavily based on the
590 .Pa src/release/generate-release.sh
593 At near 1000 revisions spread over multiple branches, the
596 .Pa src/release/Makefile
597 contains a vivid historical record of some
598 of the hardships release engineers go through.
600 .Pa src/release/Makefile
601 was originally written by
606 .An Poul-Henning Kamp .
608 This manual page was originally written by
609 .An Murray Stokely Aq murray@FreeBSD.org .
612 .An Nathan Whitehorn Aq nwhitehorn@FreeBSD.org
614 .Fa generate-release.sh
619 It was later updated by
620 .An Glen Barber Aq gjb@FreeBSD.org