From 39dd67f22f236d9f962657abe5b619f2b338f2fc Mon Sep 17 00:00:00 2001 From: Tom Tanner Date: Wed, 18 Mar 2015 14:16:04 +0000 Subject: Refactoring and cleanup. --- README.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'README.txt') diff --git a/README.txt b/README.txt index cbb571c3..7eafff83 100644 --- a/README.txt +++ b/README.txt @@ -243,7 +243,8 @@ Building with scons 2) Download QT4 (and/or QT5) from https://bitbucket.org/dirkbaechle/scons_qt4 and https://bitbucket.org/dirkbaechle/scons_qt5. Install as per instructions 3) Copy scons_configure_template.py to scons_configure.py. Edit to point to your - boost/python/zlib/7zip paths as appropriate + boost/python/zlib/7zip paths as appropriate (you can create an empty one if + you set up the params in qt creator) 4) Create build kits as follows: Custom Process step: Command: \Scripts\scons.bat @@ -259,6 +260,9 @@ Building with scons If you want to do parallel builds, add -j and a number to the arguments. However you may need to install pywin32 (but it seems to work OK for me). + -j 4 did the entire build in 2m 15s. scons uses -Z7 to store debugging + information in the .obj files which removes the issues with multiple + processes attempting to access one datafile. Note. If you want to build a sub project separately, it seems to be better to open the subproject, set that up with the scons kit and build that as a @@ -267,5 +271,3 @@ Building with scons Please note: the generated (runnable) output files end up in the build directory, in the '_ModOrganizer' subdirectory (not at the top level). Named like that so you can see it! - -This isn't complete by any means but.. -- cgit v1.3.1