Changes between Version 100 and Version 101 of BuildInstructions


Ignore:
Timestamp:
Oct 3, 2010, 11:36:02 PM (14 years ago)
Author:
Philip Taylor
Comment:

improve formatting

Legend:

Unmodified
Added
Removed
Modified
  • BuildInstructions

    v100 v101  
    7777   * CMake
    7878   * ''Optionally'': [http://code.google.com/p/nvidia-texture-tools NVTT] (pass the flag `--with-system-nvtt` to `update-workspaces.sh` to use the installed version; otherwise we'll automatically use a bundled copy of the library)
    79 
    80  * For '''Ubuntu''' or '''Debian''' (at least unstable and testing) the following might help:
     79   * For '''Ubuntu''' or '''Debian''' (at least unstable and testing) the following might help:
    8180 {{{
    8281#!html
     
    8584</pre>
    8685}}}
    87 
    88  * For '''Mandriva''' (tested with 2009.1):
    89  {{{
     86   * For '''Mandriva''' (tested with 2009.1):
     87     {{{
    9088#!html
    9189<pre class="wiki" style="white-space: pre-wrap">
     
    9391</pre>
    9492}}}
    95  No ENet package is available, so [http://enet.bespin.org/Installation.html install it from source].
    96 
    97  * For '''Fedora''' (tested with 13):
     93     No ENet package is available, so [http://enet.bespin.org/Installation.html install it from source].
     94   * For '''Fedora''' (tested with 13):
    9895 {{{
    9996#!html
     
    103100}}}
    104101
    105  * `svn co http://svn.wildfiregames.com/public/ps/trunk/`
    106  * `cd trunk/build/workspaces`
    107  * `./update-workspaces.sh` (if you update to a later version of the code from SVN, you should run this again each time)
    108  * `cd gcc`
    109  * `make CONFIG=Release -j3` (where `3` is the number of parallel builds to run, and could perhaps be one plus the number of CPU cores available)
    110    * '''Note''': Parallel building can cause errors due to race conditions. Run a "make clean" and try just "make" if you encounter problems.
    111    * The Release mode builds are more optimised, are harder to debug. Use `CONFIG=Debug` (and run `pyrogenesis_dbg`) if you are developing engine code that needs debugging.
     102 * Download and compile the code with:
     103 {{{
     104svn co http://svn.wildfiregames.com/public/ps/trunk/
     105cd trunk/build/workspaces
     106./update-workspaces.sh
     107cd gcc
     108make CONFIG=Release -j3
     109}}}
     110 "`-j3`" gives the number of parallel builds to run, and should typically be one plus the number of CPU cores available.
     111 * The Release mode builds are more optimised, are harder to debug. Use `CONFIG=Debug` (and run `pyrogenesis_dbg`) if you need better debugging support.
    112112 * If you encounter any build errors, look for an existing bug report or report a new bug. Also check the [#Knownproblemsandsolutions known problems section] below.
    113  * `cd ../../../binaries/system`
    114  * Optionally, run the automated tests to verify that everything works as expected: `./test`
    115  * Run the game: `./pyrogenesis`
    116  * Optionally, run the map editor: `./pyrogenesis -editor`
     113 * Run the automated tests to verify that everything works as expected, then run the game:
     114 {{{
     115cd ../../../binaries/system
     116./test
     117./pyrogenesis
     118}}}
     119
     120 * If you have already compiled the game from SVN and want to update to the latest version:
     121 {{{
     122cd trunk
     123svn up
     124cd build/workspaces
     125./update-workspaces.sh
     126cd gcc
     127make CONFIG=Release clean
     128make CONFIG=Release -j3
     129}}}
    117130
    118131=== OS X ===