From 7f3664f88ee001b051c0b9af39296a02bfde52f4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20A=C3=9Fmus?= Date: Sat, 27 Jun 2009 17:07:13 +0000 Subject: [PATCH] Small update. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31272 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- ReadMe | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ReadMe b/ReadMe index 915e012400..5bf4fa894f 100644 --- a/ReadMe +++ b/ReadMe @@ -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