Changes between Version 6 and Version 7 of Obsolete/MovedToTree/PackageManagement/Bootstrapping

Timestamp:

Jun 26, 2014, 11:24:54 AM (10 years ago)

Author:

zooey

Comment:

--

Obsolete/MovedToTree/PackageManagement/Bootstrapping

@@ -37 +37 @@
  * Instead of "bootstrap-raw" the build profile "bootstrap-vmware" can be used as well. You can also define your own build profile, e.g. for building to a partition. As long as its name starts with "bootstrap-" that will result in a bootstrap Haiku.
  * `haikuporter` also supports the "-j<number>" option to specify the number of jobs to use. Even on real hardware this step will nevertheless take a long time.
+ * The jam variable HAIKU_PORTER_EXTRA_OPTIONS can be defined to any options that should be passed to `haikuporter` (`--debug` is handy for showing python strack traces, for instance).
 
 
@@ -51 +52 @@
  * Once all third-party packages required for it have been built, a more complete "haiku_cross_devel_sysroot_<arch>.hpkg" is built. It is used to cross-compile the remaining third-party packages.
 
-The rigged source packages (and regular source packages) are built via `haikuporter` from the regular haikuports repository checkout. haikuports contains build recipes for a lot of software. Which source packages should be built is determined by the build system by checking what packages are needed for a regular "alpha-raw" image.
+The rigged source packages (and regular source packages) are built via `haikuporter` from the regular haikuports repository checkout. haikuports contains build recipes for a lot of software. Which source packages should be built is determined by the build system by checking what packages are needed for the target build profile used by the bootstrap process. This defaults to "minimum-raw", but it can be changed by setting the jam variable "HAIKU_BOOTSTRAP_SOURCES_PROFILE" (i.e. `jam -sHAIKU_BOOTSTRAP_SOURCES_PROFILE=@release-raw -q @bootstrap-raw` will include source packages for all packages needed by release image).