I haven’t actually got as far as doing a full build of Haiku yet because my Haiku box seems to have given up mid way though building an x86-64 anyboot image, after spending hours building the toolchain.
I used this page as my guide to building Haiku:
I wanted to build Haiku for x64 under Haiku x64 so I ended up referring to this page:
That page says I need to run:
mkdir generated.x86_64; cd generated.x86_64 ../configure --cross-tools-source ../../buildtools --build-cross-tools x86_64
./configure --cross-tools-source ../buildtools --build-cross-tools x86_64
Running these two commands can easy take well over an hour each on an average (i5 class) laptop or PC. It might be a good idea to give an idea of the expected build/execution times relative to a certain class of CPU for each command on this page.
Is it really necessary to build a cross-compilation toolchain when you are trying to build Haiku x64 under Haiku x64? Are there not packages in the HaikuDepot for providing the OS build toolchain?
That same page only mentions two jam build targets, a nighly anyboot or a raw disk image. I would suspect that both these options build the entirety of Haiku inc. gcc (again!), its kernel, desktop, toolkits and all of the default userland apps. How long does it take an average i5 or i7 class CPU to do a full build of Haiku?
Are there other jam build targets to just build a minimal subset of Haiku for example just enough to run tracker?