compile_instructions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
compile_instructions [2014/07/22 06:04] – thooge | compile_instructions [2016/12/25 15:03] (current) – [Distribution Specific Notes] thooge | ||
---|---|---|---|
Line 6: | Line 6: | ||
Please read all of your platform' | Please read all of your platform' | ||
+ | |||
+ | Compile with: | ||
+ | [[compile_bsd|BSD]] -- | ||
+ | [[compile_linux|Linux]] -- | ||
+ | [[compile_macos|MacOS]] -- | ||
+ | [[compile_windows|Windows]] | ||
===== Windows ===== | ===== Windows ===== | ||
- | ==== Requirements ==== | + | Wolfpack requires Python and the Qt library. |
- | Wolfpack requires Python | + | If you wish to use MySQL, you will also need to download MySQL. |
- | + | For detailled | |
- | If you wish to use MySQL, you will also need to download MySQL itself before compiling, since it comes with header files and libraries required to activate MySQL support on Wolfpack. | + | |
- | + | ||
- | Make sure that the QTDIR enviroment variables is properly set. | + | |
- | QTDIR should point to your qt folder, that is, where $QTDIR/ | + | |
- | + | ||
- | The examples shown here will also assume that $QTDIR/bin is in your $PATH. | + | |
- | + | ||
- | === Installing Qt === | + | |
- | + | ||
- | For compiling Qt yourself please follow up the specific | + | |
- | + | ||
- | ==== Generating Makefiles ==== | + | |
- | Go to the folder containing wolfpack folders. Inside the build folder you should find the configure script (configure2.py) The configure script will try to locate the headers and libraries required in your system and pass them to qmake to generate a makefile. Some options can be enabled/ | + | |
- | C: | + | |
- | Now change to the path ../boost and do mingw32-make. After compiling change back to ../build and compile Wolfpack server by typing mingw32-make. That's it. | + | |
- | + | ||
- | PS: You can also run make, nmake or mingw-make depending on your compiler. We recommend mingw32-make as it comes with Qt. | + | |
- | + | ||
- | ==== Compiler Specific Notes ==== | + | |
- | + | ||
- | Unfortunally, | + | |
- | + | ||
- | === MinGW === | + | |
- | Python doesn' | + | |
- | + | ||
- | To do so, you will need to download pexports.exe ( pexports 0.42h ). Extract it somewhere in your PATH, as a suggestion, use MingW' | + | |
- | cd \Python24\libs | + | |
- | pexports c: | + | |
- | dlltool --dllname python24.dll --def python24.def --output-lib libpython24.a | + | |
- | If you want to enable MySQL support, you will have to take similar steps to build an import library to mysql. | + | |
===== Linux ===== | ===== Linux ===== | ||
==== Requirements ==== | ==== Requirements ==== | ||
- | Wolfpack requires Python 2.3.x and Trolltech' | + | Wolfpack requires Python 2.x and Trolltech' |
Wolfpack will also require MySQL libraries and headers (aka development package) if you want to use MySQL, otherwise, it will default to the SQLite shiped along with Wolfpack. | Wolfpack will also require MySQL libraries and headers (aka development package) if you want to use MySQL, otherwise, it will default to the SQLite shiped along with Wolfpack. | ||
Line 56: | Line 32: | ||
==== Generating Makefiles ==== | ==== Generating Makefiles ==== | ||
- | Go to the folder containing wolfpack folders then do a chmod +x configure to fix the script permission. The configure script will try to locate the headers and libraries required in your system and pass them to qmake to generate a makefile. Some options can be enabled/ | + | Go to the folder containing wolfpack folders then do a chmod +x configure to fix the script permission. The configure script will try to locate the headers and libraries required in your system and pass them to qmake to generate a makefile. Some options can be enabled/ |
- | | + | ./configure2.py |
- | | + | |
If you don't have installed the Boost-packages or want them to link statically, you have to build the special boost-library: | If you don't have installed the Boost-packages or want them to link statically, you have to build the special boost-library: | ||
Line 67: | Line 42: | ||
make | make | ||
- | Debian GNU/Linux [[Client]]: (In the moment you have to add a path to your Python include files e.g. / | + | Debian GNU/Linux [[Client]]: (In the moment you have to add a path to your Python include files e.g. / |
+ | |||
+ | Finally | ||
+ | make | ||
+ | make install | ||
==== Distribution Specific Notes ==== | ==== Distribution Specific Notes ==== | ||
Line 73: | Line 52: | ||
=== Debian === | === Debian === | ||
- | * Recommended that you use at least Debian | + | * Recommended that you use at least Debian |
- | * In Debian Sarge the supplied QT Version is only 3.3.4 | + | |
- | * for more information see: http:// | + | |
* QT4 Packages: '' | * QT4 Packages: '' | ||
- | * Python Packages: '' | + | * Python Packages: '' |
- | * Python 2.4 to 2.7 ist also acceptable | + | * Boost: '' |
- | * Boost: '' | + | * OpenAL Packages: '' |
- | * OpenAL Packages: '' | + | * Recommended Packages: '' |
- | * Recommended Packages: '' | + | * MySQL Packages: '' |
- | * MySQL Packages: '' | + | |
The '' | The '' | ||
Line 97: | Line 73: | ||
===== MacOS X ===== | ===== MacOS X ===== | ||
- | This is actually in testing | + | see [[compile_macos]] |
- | * Install Python 2.7.6 | + | |
- | * Install QT 5.2.1 | + | |
- | * Install Command line tools for Xcode | + | |
- | * Download at https:// | + | |
- | * Open Terminal, shange to directory of your choice e.g. your home directory ''/ | + | |
- | * Set QTDIR environment variable \\ < | + | |
- | export QTDIR=/ | + | |
- | source ~/ | + | |
- | </ | + | |
- | * Set Xcode path: '' | + | |
- | * Make working directory \\ < | + | |
- | cd wpdev | + | |
- | </ | + | |
- | * Get current Sourcecode: < | + | |
- | * Configure \\ < | + | |
- | ./ | + | |
- | </ | + | |
- | + | ||
- | First Blocker: '' | + | |
- | * / | + | |
- | * First Test for Resolution: Install complete Xcode 5.1 | + | |
- | + | ||
- | Second BLocker: | + | |
- | * Linking error: '' | + | |
- | * Perhaps this is a conflict between different Python versions? | + | |
- | + | ||
- | + | ||
- | + | ||
- | To be continued... | + | |
compile_instructions.1406009068.txt.gz · Last modified: 2014/07/22 06:04 by thooge