Aren/haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1f569db086
haiku/3rdparty/docker/bootstrap
History
Alexander von Gluck IV 42f51416eb docker/bootstrap: ensure work volume exec, fix dependencies 
Change-Id: I8b8d3a2f3b5a09063b183dc355407908cc2640f6
Reviewed-on: https://review.haiku-os.org/c/haiku/+/2763
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2020-05-21 14:03:24 +00:00
..
bootstrap.sh
crosstools.sh
Dockerfile docker/bootstrap: ensure work volume exec, fix dependencies 2020-05-21 14:03:24 +00:00
Dockerfile.fedora docker/bootstrap: ensure work volume exec, fix dependencies 2020-05-21 14:03:24 +00:00
haikuports_build.sh
haikuports_chroot.sh
Makefile docker/bootstrap: ensure work volume exec, fix dependencies 2020-05-21 14:03:24 +00:00
prep.sh
README.md

README.md

Haiku bootstrap in a container

The Haiku bootstrap process is highly dependant on what tools are installed on the host machine. Bootstraped haikuporter builds can pick up on things like the locally installed clang vs the gcc toolchain we are providing.

By running bootstrap within a container, we can better isolate the process from the end users host and create more-reproduceable bootstrap builds.

This is designed for GCC bootstraps. In theory if Haiku changed to clang, the need for a crosstools toolchain is removed... however the clang work is too early to know exactly how this process will work.

Requirements

  1. docker
  2. make
  3. An internet connection

Process

  1. Build the docker container

make

  1. Check out the required sources

make prep

  1. Build the crosstools (gcc only) for your target architecture

TARGET_ARCH=arm make crosstools

  1. Begin the bootstrap (building Haiku + the required bootstrap hpkgs)

TARGET_ARCH=arm make bootstrap

  1. If you need to enter the build environment, TARGET_ARCH=arm make enter will quickly let you do so.
  2. profit!