Changes between Version 184 and Version 185 of BuildInstructions

Timestamp:

Jul 30, 2012, 2:35:08 AM (12 years ago)

Author:

historic_bruno

Comment:

--

BuildInstructions

@@ -66 +66 @@
 The Visual Studio project/solution files are automatically generated from the source files:
 
- * Run `build/workspaces/update-workspaces.bat`.
+ * Run [source:/ps/trunk/build/workspaces/update-workspaces.bat build/workspaces/update-workspaces.bat].
  * Open `build/workspaces/vc2010/pyrogenesis.sln`. (Use the `vc2005` directory for VC++ 2005 or the `vc2008` directory for VC++ 2008.)
 
@@ -75 +75 @@
 
 === Building Atlas ===
-If you also wish to test the [wiki:Atlas_User%27s_Guide Atlas Scenario Editor] or [wiki:Actor_Editor Actor Editor] tools, you will need to download and build the [http://www.wxwidgets.org/ wxWidgets] library separately (see `libraries\wxwidgets\README.txt` for details), then supply the `--atlas` option when running `update-workspaces.bat`. Atlas projects will now be included when you open `pyrogenesis.sln` in Visual C++.
+If you also wish to test the [wiki:Atlas_User%27s_Guide Atlas Scenario Editor] or [wiki:Actor_Editor Actor Editor] tools, you will need to download and build the [http://www.wxwidgets.org/ wxWidgets] library separately (see [source:/ps/trunk/libraries/wxwidgets/README.txt libraries/wxwidgets/README.txt] for details), then supply the `--atlas` option when running `update-workspaces.bat`. Atlas projects will now be included when you open `pyrogenesis.sln` in Visual C++.
 
 === Running ===
@@ -117 +117 @@
  * wxWidgets (packages are probably called wxgtk)
 To use shared system libraries instead of bundled copies (default) of libraries (pass the flag `--with-system-$COMPONENT` to `update-workspaces.sh` to use the non-bundled copy):
- * ENet 1.3 (`--with-system-enet`)
+ * [http://enet.bespin.org/ ENet 1.3] (`--with-system-enet`)
  * [https://developer.mozilla.org/en/SpiderMonkey/1.8.5 SpiderMonkey 1.8.5] (`--with-system-mozjs185`)
  * [http://code.google.com/p/nvidia-texture-tools NVTT] (`--with-system-nvtt`)
@@ -322 +322 @@
  * 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/premake4.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 [source:/ps/trunk/build/premake/premake4.lua 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`
@@ -381 +381 @@
 
 == Known problems and solutions ==
+ * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Arch Linux or Slackware), edit the file [source:/ps/trunk/build/premake/extern_libs4.lua build/premake/extern_libs4.lua] and remove the `-mt` suffix from the Boost `unix_name` definitions, then run `update-workspaces.sh` again.
+
  * If you get linker errors like '''`multiple definition of '(anonymous namespace)::_1'`''', particularly when using GCC 4.1, try running `./update-workspaces.sh --without-pch` and then `cd gcc; make clean` and rebuild.
 
- * 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/premake4.lua`
-
- * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Arch Linux or Slackware), edit the file [source:/ps/trunk/build/premake/extern_libs4.lua build/premake/extern_libs4.lua] and remove the `-mt` suffix from the Boost `unix_name` definitions, then run `update-workspaces.sh` again.
+ * 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 [source:/ps/trunk/build/premake/premake4.lua build/premake/premake4.lua]
 
  * 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