haiku/3rdparty/docker/bootstrap
Alexander von Gluck IV 6f9861ccf7 docker/bootstrap: Add missing autopoint tools
Change-Id: I3dd3de1611f55d92b1f3c1edde28d4807a5aec8a
2019-12-09 13:45:14 -06:00
..
Dockerfile docker/bootstrap: Add missing autopoint tools 2019-12-09 13:45:14 -06:00
Dockerfile.fedora
Makefile docker/bootstrap: rename init to prep to be consistent 2019-12-09 13:45:14 -06:00
README.md docker/bootstrap: rename init to prep to be consistent 2019-12-09 13:45:14 -06:00
bootstrap.sh
crosstools.sh
haikuports_build.sh
haikuports_chroot.sh
prep.sh

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!