[openbeos] Re: building Haiku

Cian Duffy wrote:

And that would be why rc has a makefile as well....

Cian



It looks like you have to have rc built before you can do a 'make' on
jam. So if you don't have jam or a net connection you are doing
sneakernet to move the tools over. :-)


Build instructions update anyone? :-)

NOTE: the information in this file is tremendously outdated.
The preferred method to build Haiku (currently only possible on a BeOS machine)
is this (when you're in the "haiku" directory):
$ configure
$ makehdimage /Haiku

Where /Haiku is the (mounted) partition of where you want to install Haiku on.
If the parameter is omitted, the makehdimage currently creates a 60 MB Haiku image in this directory that you can use for Bochs, Qemu and other emulators to boot.
You need a Jam 2.5 build from our sources, and GCC 2.95.3 to be able to build Haiku successfully.

Go bug us to update this file for real!


Building
--------

The build system uses Jam/MR (http://www.perforce.com/jam/jam.html).
A BeOS executable of Jam 2.5rc3 is available at:
http://www.haiku-os.org/downloads.php?mode=download&id=10&mirror=0

Unzip the executable and copy it to /boot/home/config/bin.

If you are a build it yourself type and want to build jam from the sources included in the haiku tree you must first have built rc and jam.

To build rc cd into (path to haiku)/haiku/src/tools/rc and type
   $ make

The Jam source code is also included in the source tree. You can as well cd
into "haiku/src/tools/jam" and run "make" to obtain an executable.

The correct gcc version can be downloaded from BeBits at:
http://www.bebits.com/bob/18096/gcc-2.95.3-beos-041202.zip

Follow the instructions in the included readme file or you will have problems building the Haiku tree.

Building Haiku:
To build the whole source tree, launch a Terminal, cd into the haiku directory and just type:

 $ ./configure
 $ jam

The configure script generates a file named BuildConfig. As long as configure
is not modified (!), there is no need to call it again. That is for
re-building you only need to invoke Jam. If you don't update the source tree
very frequently, you may want to execute configure after each update just to
be on the safe side.

NOTE: If you have checked out the latest CVS version, it is not unlikely that
some parts of the tree won't build.



Other related posts: