GSoC/GCI Archive
Google Code-in 2013 Haiku

***BONUS*** Get Boost to build as completely as possible on Haiku Part 2 ***BONUS***

completed by: Adrián Arroyo Calle

mentors: Urias McCullough, scottmc, Barrett, mmu_man

This task requires updating a .recipe file to allow Haikuporter to build from source code the most recent version of the listed package.  You will need a working nightly installation of Haiku built after hrev46308, this could be on real hardware or in a VM, and haikuporter which can be installed by following the install instructions at HaikuPorts.  Part 1 of this task was to write a recipe to build Boost and it got deep into the build, but Boost is HUGE and there's a few build issues that will need to be worked around/patched/skipped in order to get the majority of Boost building.  So this follow up task is to continue that patching/skipped until Boost is mostly building on Haiku.

Some knowledge of C, C++, git and/or bash may or may not be required in order to complete this task.  Knowledge of the GNU autotools and/or cmake may also be helpful.  The package may or may not require some patching to get it to work on Haiku.  For these cases don't be afraid to ask for help.  Many compile issues can be figured out by reading through the various wiki pages at HaikuPorts.  Also google (or other web search engine) may be of help in finding solutions to build issues that you may run into, irc channel #haiku on freenode might also be of help.  Be sure to follow the correct format for creating your .recipe file, including the license and copyright entries.

This tasks requires a working .recipe file to be submitted as proof of completion, be sure to test your .recipe file before submitting, this is done by using haikuporter to build it into an .hpkg file.  You can inspect the .hpkg by locating it in your haikuports/packages directory after it gets built, double clicking it should open up expander, in expander check the show files check box and it will show what's in the .hpkg file.

Boost is under dev-libs in the haikuports tree
Also, issues raised on the haikuports-svn mailing list should be addressed, see: