Haiku/haiku
Haiku/haiku
1
0
Fork 0
mirror of https://review.haiku-os.org/haiku synced 2024-11-23 07:18:40 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Small update.

Browse Source 
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31272 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Stephan Aßmus 2009-06-27 17:07:13 +00:00
parent 93b6484548
commit 7f3664f88e
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
ReadMe
View File

@ -31,11 +31,11 @@ Where "TARGET" is the target platform that the compiled code should run on:
* bone
* dano (also for Zeta)
The configure script generates a file named "BuildConfig" in the "build"
directory. 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 (see below).
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.
The configure script generates a file named "BuildConfig" in the
"generated/build" directory. 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 (see below). 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.
Building
@ -88,7 +88,7 @@ Under Unix/Linux, and BeOS you can use cdrecord to create a CD with:
cdrecord dev=x,y,z -v -eject -dao -data generated/haiku-cd.iso
Here x,y,z is the device number as found with cdrecord -scanbus, it can also
Here x,y,z is the device number as found with cdrecord -scanbus, it can also
be a device path on Linux.
Building Components