haiku/3rdparty/docker/bootstrap
Alexander von Gluck IV 7a180033de docker/bootstrap: Fix sysroot stage variable
Change-Id: Icb7d83fd60d85a107601012f906ed7bf63f0eb61
2019-04-03 20:47:12 -05:00
..
bootstrap.sh docker/bootstrap: Add --debug to get better haikuporter debug output 2018-11-04 08:37:54 -06:00
crosstools.sh
Dockerfile docker/bootstrap: Add vim/nano to assist in bootstrap 2019-03-19 13:33:12 -05:00
haikuports_build.sh bootstrap: Add some tools to test bootstrap steps 2019-02-15 11:27:04 -06:00
haikuports_chroot.sh docker/bootstrap: Fix sysroot stage variable 2019-04-03 20:47:12 -05:00
Makefile 3rdparty/bootstrap: kill any running bootstrap containers before rm 2018-11-20 14:53:13 -06:00
prep.sh
README.md bootstrap: Add some tools to test bootstrap steps 2019-02-15 11:27:04 -06:00

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 init

  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!