Menu
▾
▴
[Planeshift-cvs] SF.net SVN: planeshift: [328] trunk/docs/compiling.html
|
From: <ar...@us...> - 2007-12-01 12:04:06
|
Revision: 328
http://planeshift.svn.sourceforge.net/planeshift/?rev=328&view=rev
Author: aryhann
Date: 2007-12-01 03:42:25 -0800 (Sat, 01 Dec 2007)
Log Message:
-----------
Updated compiling guide with Rakhun's suggestion for building with Mingw and with the fixes for bugs #535 and #596
Modified Paths:
--------------
trunk/docs/compiling.html
Modified: trunk/docs/compiling.html
===================================================================
--- trunk/docs/compiling.html 2007-12-01 03:51:51 UTC (rev 327)
+++ trunk/docs/compiling.html 2007-12-01 11:42:25 UTC (rev 328)
@@ -17,7 +17,7 @@
var CAL3Drev_HEAD = "407"; // CAL3D_SOURCE_REV_HEAD
var csWinLibsVersion = "1.2_002"; // cs win32 libs version.
//Update date and author, to be changed everytime and updates occurred
- var UpdateDate = "18 Nov 2007"; //Date when the update occurred
+ var UpdateDate = "01 Dec 2007"; //Date when the update occurred
var UpdateAuthor = "Arianna Benigno"; //Author of the update
-->
</script>
@@ -434,12 +434,18 @@
Run the exe files in the order they were downloaded to install the compiler and unzip the conf/make utilities in c:\msys\1.0\. <br>
Then unzip the BinUtils to the c:\mingw directory.<br>
+Unzipping the tar.bz2 archives needs to be done through the MSYS
+command-line by changing directory with the cd command to where you
+downloaded the files. Then, run the following commands:
+<i class="command">tar -xjf msys-autoconf-2.59.tar.bz2 -C /c/msys/1.0<br>
+tar -xjf msys-automake-1.8.2.tar.bz2 -C /c/msys/1.0<br>
+tar -xzf binutils-2.16.91-20060119-1.tar.gz -C /c/MinGW</i><br>
This allows MSYS to setup the MinGW paths correctly.<br>
The installation program should also add an icon for MSYS to your start menu. <br>
Click the "MSYS" icon and it should open up a shell window. Type "exit" to close the shell window again.<br><br>
- Download the following dependencies from the same site, but do not install these yet. Their install instructions are included:<br>
- Create and place these dependencies into /usr/src. Also, create the /usr/local directory.<br><br>
+ Download the following dependencies from the same site, but do not install these yet. Their install instructions are included.<br>
+ From explorer, create and place these dependencies into C:\msys\1.0\src. Also, create the C:\msys\1.0\local directory.<br><br>
freetype-2.1.9-mingwPORT.tar.bz2 <br>
jpeg-6b-mingwPORT.tar.bz2<br>
@@ -449,6 +455,21 @@
The following dependencies use a scripted system to download and install them, built into their files.<br>
For the unanswered questions below, just press enter to accept the default (in parentheses).<br><br>
<b>Installing wget</b>
+ <p> The input listed by the mingwPORT.sh script assumes that there is a file
+called wget-1.9.1.tar.gz in /usr/src, but the file you do have is
+wget-1.9.1-mingwPORT.tar.bz2.<br>
+
+There seems to be two solutions to this problem, you can choose the one your prefer the most:<br>
+
+1)Download the file from
+<a href="ftp://ftp.gnu.org/gnu/wget/wget-1.9.1.tar.gz">here</a> and put it in
+/usr/src before running the mingwPORT.sh script<br>
+
+2)Just copy the prebuilt wget instead of compiling it instead of
+typing "mingwPORT.sh" (see the command list below) to run the script type "cp wget.exe /mingw/bin" and then
+continue as indicated.<br></p>
+
+
<p><div class="commandBox">
$ tar -jxvf wget-1.9.1-mingwPORT.tar.bz2<br>
$ cd wget-1.9.1/mingwPORT<br>
@@ -866,7 +887,7 @@
</p>
-h3>CS Windows Libraries</h3>
+<h3>CS Windows Libraries</h3>
<p>Rather than having to install CS dependant components manually, Microsoft Visual C++, MinGW/MSYS and Cygwin
users can download a single package which contains all common headers, pre-built library files, and dynamic link
libraries in pre-compiled form from the Crystal Space website, http://www.crystalspace3d.org/.</p>
@@ -879,8 +900,14 @@
<a href="http://www.crystalspace3d.org/downloads/cs-win32libs/static/">http://www.crystalspace3d.org/downloads/cs-win32libs/static/</a><br/>
</div>
The currently used CS revision needs version <b>LIBS_VER</b>. Don't mix up with other versions!</p>
+ <div class="MSVC">
+ <p>Run the program and install the libraries. The Default name is fine. </p></div>
+<div class="MINGW">
+<p>Run the program and install the libraries in C:\CSLibs. <br>
+This helps to
+trim down the length of the CEL linker flag list.</div>
- <p>Run the program and install the libraries. The Default name is fine. When it asks you for the CS directory, enter
+<p>When it asks you for the CS directory, enter
<b>C:\development\CS</b>.<br>
When you have to select the components, you can select the options you prefer through the check boxes.<br>
@@ -906,12 +933,8 @@
Goto the start menu, go to Programs and then to CrystalSpace Win32 libraries.
Select "Copy DLLs to a CS directory". Set the directory to C:\development\CS when prompted.
<div class="MINGW">
- Next, copy CrystalSpaceLibs MinGW directory into a new generic directory like this:<br>
- (You may need to verify the mingw directory first.)<br><br>
- <i class="command">
- cp -rf /C/CrystalSpaceLibs/lib/mingw-gcc-3.4 /C/CrystalSpaceLibs/lib/mingw
- </i>
- </div>
+ Next, copy CrystalSpaceLibs MinGW directory into a new generic directory.
+ </div>
</p>
<h3>Crystal Entity Layer (CEL)</h3>
@@ -1045,13 +1068,14 @@
<div class="Windows">
- <p>Run MSYS from the start menu to open the shell.</p>
+ <p>Run MSYS from the start menu to open the shell. Be aware that if you have MSYS opened already, you need to restart the console, otherwise
+ many things won't be found during the build process. Make sure you run the export commands to set the environment variables again</p>
<h3>Crystal Space (CS)</h3>
<p>Switch to the Crystal Space source dir using 'cd /c/development/cs'.
Configure to debug mode and jam. (if you wish to build in optimized mode, just run
configure without any arguments) If you chose to build cal3d, rather than use
- it from the CS win libs, you can specify it's location with: --with-cal3d=/c/development/cal3d/
+ it from the CS win libs, you can specify its location with: --with-cal3d=/c/development/cal3d/
<p><div class="commandBox">
./configure --without-java --without-perl --without-python --without-lib3ds<br>
<div class="Normal">
@@ -1079,21 +1103,24 @@
You can test this build by running the demo application "celtst.exe" in /c/development/cel to check that everything is ok.
<h3>PlaneShift</h3>
- <p>Change your working directory to PS's,
+ <p>If you chose to build cal3d, rather than use
+ it from the CS win libs, you can specify its location after the configure command with: --with-cal3d=/c/development/cal3d/ <br>
+Change your working directory to PS's,
and do:</p>
<p><div class="commandBox">
./autogen.sh<br>
<div class="User">
- ./configure --with-libcal3d=/home/user/development/cal3d<br>
+ ./configure <br>
</div>
<div class="Developer">
- ./configure --enable-debug --with-libcal3d=/home/user/development/cal3d<br>
+ ./configure --enable-debug <br>
</div>
</div>
</p>
<p>
- Sometimes when compiling with GCC it says the list of linker flags for CEL is
-too long and that many of the flags are duplicates.<br>
+ Sometimes when compiling with GCC it says the list of linker flags
+for CEL is too long. Many of the flags are just duplicates and can be
+removed. The box below can be used to do it for you automatically.<br>
<script language="Javascript">
<!--
function fixflags()
@@ -1258,7 +1285,22 @@
<div class="Windows">
<p>Note: You might have to copy a few DLL files from other build directories to your
PlaneShift directory if you get problems. You usually need to move libz-cs.dll, libcurl.dll (or similar), and libmySQL.dll.</p>
+<div class="MINGW">
+<p>For Mingw you need to copy also these files to the
+Planeshift directory:<br>
+C:\msys\1.0\local\bin\libpng12-0.dll<br>
+C:\development\cs\cg.dll<br>
+C:\development\cs\cgGL.dll<br>
+C:\MinGW\bin\libjpeg-62.dll<br><br>
+or by command-line:<br>
+cp /c/msys/1.0/local/bin/libpng12-0.dll <br>
+cp /c/development/cs/cg.dll <br>
+cp /c/development/cs/cgGL.dll <br>
+cp /c/MinGW/bin/libjpeg-62.dll <br>
+</p>
</div>
+
+</div>
<div class="MSVC">
<h3>Setting Up For Debugging</h3>
<p>Now before you can debug the programs, you need to change some properties of the project.<br>
@@ -1273,7 +1315,21 @@
<h2><a name="update">Get PS Art</a></h2>
<p>
-The artwork for PlaneShift is not included in SVN. There are two ways to get it: you can either get the data
+You can choose to run your local client and server with the official artwork or with the SVN one.</p><p>
+The SVN artwork is rather incomplete and it doesn't contain any fancy piece of art. It is however necessary
+to have if you want to run your client. If you want to fetch this art, you need to collect it from SVN and put it in
+a <i>art</i> subdirectory in your Planeshift directory.
+
+<div class="Linux">
+<p><i class="command">/home/user/development$ svn co https://planeshift.svn.sourceforge.net/svnroot/planeshift/art planeshift</i></p>
+</div>
+
+<div class="Windows">
+<p><i class="command">https://planeshift.svn.sourceforge.net/svnroot/planeshift/art</i></p>
+</div>
+</p><p>
+The official released artwork for PlaneShift is not included in SVN.
+There are two ways to get it: you can either get the data
from a Planeshift release or use the Planeshift updater.<br>
It's suggested, if you have a release of
Planeshift installed, to get the data from it, saving download time and bandwidth.
@@ -1289,7 +1345,9 @@
<h3>Using the Planeshift Updater</h3>
<p>
-If you don't have a Planeshift installation you can use the updater you have built to get the required data.<br>
+If you don't have a Planeshift installation you can use the updater you have built to get the required data, if the updater is enabled
+this doesn't happen systematically after every release).<br>
+
It will connect to our update central site and download all the missing material. All you need is updated art
and data files. This is done by editing updaterconfig.xml and first setting the correct mirrors that are in use.
Our current mirror list is:
@@ -1445,6 +1503,7 @@
PS Server: loadmap npcroom1<br>
PS Server: loadmap npcroom2<br>
PS Server: loadmap npcroom_corr<br>
+ PS Server: loadmap podium<br>
PS Server: spawn<br>
PS Server: ready
</div></p>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|