Aren/haiku
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a29a8f98ed
haiku/3rdparty/docker/bootstrap
History
Alexander von Gluck IV c5287be1f3 3rdparty/bootstrap: kill any running bootstrap containers before rm 
Change-Id: Id36226f121d4a75adc4799ae6cd8cddff2149b10
2018-11-20 14:53:13 -06: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 missing pkg-config for ICU 2018-11-04 09:13:24 -06:00
Makefile 3rdparty/bootstrap: kill any running bootstrap containers before rm 2018-11-20 14:53:13 -06:00
prep.sh
README.md docker/bootstrap: Make README.md a bit more detailed 2018-11-04 09:05:15 -06:00

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 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, make enter will quickly let you do so.
  2. profit!