From ccc65716b6a5d1a07b66ae427d55745b6807e9e7 Mon Sep 17 00:00:00 2001 From: Mikko Rasa Date: Thu, 30 Aug 2018 14:13:00 +0300 Subject: [PATCH] Slight updates to Readme --- Readme.txt | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/Readme.txt b/Readme.txt index eaff771..16def7c 100644 --- a/Readme.txt +++ b/Readme.txt @@ -34,11 +34,10 @@ builds, cross-compilation and pkg-config integration. 2. Building Builder -Builder is normally built using itself. However, if you just downloaded the -source and don't yet have a Builder binary, how is that possible? To resolve -this problem, there's a script called bootstrap.sh in the Builder main -directory. Before running it, make sure you have the following libraries -available: +Builder is normally built using itself. This creates a conundrum if you just +downloaded the source and don't yet have a Builder binary. To resolve the +problem, there's a script called bootstrap.sh in the Builder main directory. +Before running it, make sure you have the following libraries available: MSP libraries: core datafile @@ -47,10 +46,9 @@ Others: sigc++-2.0 You should be able to get the MSP libraries from the same place you got Builder itself from. Since they are also normally built with Builder, the script will need to have their sources available. By default, it will look at -the parent directory of builder. You can change this by setting the LIBPATH -evironment variable for the script. If everything goes well, the script will -build a builder-stage1 binary and then proceed to build a normal version with -it. +the parent directory of builder. You can change this with the --libpath +parameter for the script. If everything goes well, the script will build a +builder-stage1 binary and then proceed to build a normal version with it. ------------------------------------------------------------------------------- -- 2.45.2