Changes between Version 157 and Version 158 of BuildInstructions

Timestamp:

Feb 19, 2012, 7:48:00 PM (12 years ago)

Author:

leper

Comment:

Fixed a typo. Removed unnecessary (as it is the default) use of config=release. Updated the 'Known problems and solutions' section to reflect updates to the build system.

BuildInstructions

@@ -173 +173 @@
 ./update-workspaces.sh -j3
 cd gcc
-make config=release -j3
+make -j3
 }}}
 
  * '''-j3''' gives the number of parallel builds to run, and should typically be one plus the number of CPU cores available.
- * The '''Release''' mode builds are more optimised, but are harder to debug. Use `config=debug` (and run `pyrogenesis_dbg`) if you need better debugging support.
+ * The '''Release''' mode builds (which are the default) are more optimised, but are harder to debug. Use `make config=debug` (and run `pyrogenesis_dbg`) if you need better debugging support.
 
 If you encounter any build errors, review the [http://trac.wildfiregames.com/report existing bug reports], check the [#Knownproblemsandsolutions known problems section] or please file a [http://trac.wildfiregames.com/newticket new bug in the tracker].
@@ -210 +210 @@
 ./update-workspaces.sh
 cd gcc
-make config=release clean
-make config=release -j3
+make clean
+make -j3
 }}}
 
 If you just edited one source code file and want to rebuild, you can usually get away with:
 {{{
-make config=release -j3
+make -j3
 }}}
 
@@ -226 +226 @@
 ./update-workspaces.sh
 cd gcc
-make config=release -j3
-}}}
-If the `make` line gives errors, you may need to run `make config=release clean` before it. If the `update-workspaces.sh` gives errors, you may need to run `clean-workspaces.sh` before it.
+make -j3
+}}}
+If the `make` line gives errors, you may need to run `make clean` before it. If the `update-workspaces.sh` gives errors, you may need to run `clean-workspaces.sh` before it.
 
 == OS X ==
@@ -266 +266 @@
  * You may need to patch Apple's OpenAL (`/System/Library/Frameworks/OpenAL.Framework/Headers/alc.h`: replace all `ALCvoid` by `void`, except the first one which is a `typedef`). (GCC >=4.2 is stricter about parameters invalidly typedefed to void in C++.)
 
- * If you're under Tiger, you'll certainly have to edit `build/premake/premake.lua` to get rid of the `-fstack-protector-all` line: see the [#Knownproblemsandsolutions known problems section].
+ * If you're under Tiger, you'll certainly have to edit `build/premake/premake4.lua` to get rid of the `-fstack-protector-all` line: see the [#Knownproblemsandsolutions known problems section].
 
  * Then, restart the compilation starting from `./update-workspace.sh`
@@ -305 +305 @@
  * If you get linker errors like '''`/usr/bin/ld: Undefined symbols: ___stack_chk_fail, ___stack_chk_guard`''', this comes from using a libc that is not glibc >=2.4. Until this is detected by the build system, you can hack it by removing the "-fstack-protector-all" line (and the next line too if needed) from `build/premake/premake.lua`
 
- * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Slackware 13.37 and -current), edit the file `build/premake/extern_libs4.lua` and remove the `-mt` suffixes from the boost definitions in line 212, and then run `update-workspaces.sh` again. It should look like this:
-{{{
-unix_names = { "boost_signals", "boost_filesystem", "boost_system" },
-}}}
+ * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Slackware 13.37 and -current), edit the file `build/premake/extern_libs4.lua` and remove the `-mt` suffixes from the boost definitions in line 221 and line 230, and then run `update-workspaces.sh` again. It should look like
+{{{
+unix_names = { "boost_filesystem", "boost_system" },
+}}}
+   for line 221 and
+{{{
+unix_names = { "boost_signals" },
+}}}
+   for 230 respectively.
 
  * If !SpiderMonkey has compile errors during `update-workspace.sh`, throwing errors like '''`'r13' is not a member of 'JSC::X86Registers'`''', then you likely have a 32-bit userspace with a 64-bit kernel. Run