<p>This will checkout the source into a new subdirectory called "haiku". <b>Members</b> of Haiku should login with their BerliOS account to get commit access:</p>
<p>After the <b>initial checkout</b> (also in case not the entire tree was checked out successfully) you can fetch source code updates with the following command in your repository's root folder:</p>
<p>Download the <ahref="http://haiku.mlotz.ch/haiku_cross_compiler_bone_2.95.3-haiku-081024.zip">Haiku cross-compiler</a> and extract it to <spanclass="path">/boot</span> (for example by setting the <i>Destination</i> in Expander to just <spanclass="path">/boot</span>). Then you need to configure your tree to use this cross compiler. Go to the root folder of your checked out Haiku repository and invoke the configure script with the <spanclass="cli">--cross-tools-prefix</span> option like this:</p>
<p>Be careful to include all of the string up to and including the last dash, as all the cross compiler tools have this prefix (they are for example called <spanclass="cli">i586-pc-haiku-ar</span>). You need to specify this prefix everytime you run configure.</p>
<pstyle="text-indent: 15pt"><b>Note:</b><i>this will just build any target that is found in the tree. This is usually not that useful, as many parts might not build and are not required. So optionally, a target can be specified by adding a target name. For example, </i><spanclass="cli">jam app_server</span><i> will only build the </i><tt>app_server</tt><i> target. Normally though you will want to build an image or installation using the commands below. Add the </i><spanclass="cli">-a</span><i> option to rebuild the whole source or only the specified target in case </i><spanclass="cli">jam</span><i> didn't notice source changes.</i></p>