i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated to reflect the current building process.

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@228 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Ingo Weinhold
2002-07-14 22:10:54 +00:00
parent 022fa24472
commit cd29a30864
1 changed files with 23 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ReadMe
+23 -8
View File
@@ -2,11 +2,13 @@ Building
-------- --------
The build system uses Jam/MR (http://www.perforce.com/jam/jam.html). The build system uses Jam/MR (http://www.perforce.com/jam/jam.html).
A BeOS executable of Jam 2.3.1 is available at: A BeOS executable of Jam 2.4 is available at:
http://open-beos.sf.net/misc/jam.zip http://open-beos.sf.net/misc/jam.zip
Unzip the executable and copy it to /boot/home/config/bin. Unzip the executable and copy it to /boot/home/config/bin.
The Jam source code is also included in the source tree. You can as well cd
into "src/tools/jam" and run "make" to obtain an executable.
To build the whole source tree, launch a Terminal, cd into the openbeos root To build the whole source tree, launch a Terminal, cd into the openbeos root
directory and just type: directory and just type:
@@ -28,27 +30,40 @@ Running
------- -------
If the build went fine, a file named floppy.x86 had been created in the If the build went fine, a file named floppy.x86 had been created in the
root directory of the source tree. What you want to do now, is to boot from target specific objects directory (objects/x86.R1 for x86 machines).
this floppy image. Therefore you either write the image onto a real floppy What you want to do now, is to boot from this floppy image. Therefore you
disk and restart you computer, or you write it onto a "virtual floppy disk" either write the image onto a real floppy disk and restart you computer, or
emulated by a x86 PC emulator and just start this emulator. you write it onto a "virtual floppy disk" emulated by a x86 PC emulator and
just start this emulator.
1. Real Floppy 1. Real Floppy
Put in the disk and type in the source tree's root dir: Put in the disk and type in the source tree's root dir:
$ dd if=floppy.x86 of=/dev/disk/floppy/raw bs=18k $ dd if=objects/x86.R1/floppy.x86 of=/dev/disk/floppy/raw bs=18k
2. Emulated Floppy (Bochs) 2. Emulated Floppy (Bochs)
Type: Type:
$ dd if=floppy.x86 of=<floppy image> bs=18k $ dd if=objects/x86.R1/floppy.x86 of=<floppy image> bs=18k
where <floppy image> has to be replaced with the filename of the floppy where <floppy image> has to be replaced with the filename of the floppy
image Bochs has been told to use (e.g. /tmp/obos.img). image Bochs has been told to use (e.g. /tmp/obos.img).
For both cases there is also an simpler way:
$ jam installfloppy
This builds the floppy image, if it is not up to date, and writes it to a
previously specified location. Therefore you must tell configure where this
location is:
$ ./configure --floppy /dev/disk/floppy/raw
Ananlogously for the emulated floppy.
Bochs Bochs
----- -----
@@ -93,7 +108,7 @@ ips: 2000000
Now put the OBOS boot image onto you "virtual" floppy and start Bochs: Now put the OBOS boot image onto you "virtual" floppy and start Bochs:
$ cd <OBOS sources directory> $ cd <OBOS sources directory>
$ dd if=floppy.x86 of=/tmp/obos.img bs=18k $ jam installfloppy
$ cd /boot/apps/BeBochs1.4 $ cd /boot/apps/BeBochs1.4
$ ./bochs $ ./bochs