| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
This article is part of the Installation Guide. You can read it alone or click on the previous link to easily move between the steps.
|
Linux
...
| Columna | ||||||
|---|---|---|---|---|---|---|
Getting startedThis how-to will attempt to help with TrinityCore, and also show how this can be done in a way that also shows you the basics of how linux compilations works.
Advices:
Your server may be abruptly killed by an angry administrator or system staff for overuse of system resources. Creating a user to work withStart with logging in to your Linux-machine and create an account for the server itself - on most recent distributions this can easily be done with the following command :
Note : Change <username> into the preferred username of your server-account - we will as far as possible avoid using specific usernames in this how-to. Sample usernames found in various parts of this guide: wow , trinity ( - select a logical name that makes sense to you when creating the user - ). Required softwareSee Requirements Optional softwareThese tools are only needed or useful if you are connecting from a Windows host to your Linux machine Graphical database-viewing/editingPlease note that the software called Navicat is NOT supported due to issues with how it handles SQL-files with "/* */"-style comments. We advise all users to stay well clear of this program unless they really are looking for issues. Remote console connects to the serverFile transfer through SFTP or FTP |
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Content
|
Building the server itself
Getting the source code
3.3.5
| Bloque de código |
|---|
cd ~/
git clone -b 3.3.5 git://github.com/TrinityCore/TrinityCore.git |
This will clone 3.3.5a branch, this is the RECOMMENDED branch for starters.
6.x
| Bloque de código |
|---|
cd ~/
git clone -b 6.x git://github.com/TrinityCore/TrinityCore.git |
This will clone 6.x branch, note that this is NOT the recommended branch for starters.
The directory TrinityCore will be created automatically and all the source files will be stored in there.
| Nota |
|---|
FreeBSD users will need to apply the patch located here for g3d to compile properly, before doing anything else. |
Compiling the source code
Creating the build-directory
To avoid issues with updates and colliding source builds, we create a specific build-directory, so we avoid any possible issues due to that (if any might occur)
| Bloque de código |
|---|
cd TrinityCore
mkdir build
cd build |
Configuring for compiling
To configure the core, we use space-separated parameters attached to the configuration-tool (cmake) - do read the entire section before even starting on the configuration-part.
This is for your own good, and you HAVE been warned. A full example will also be shown underneath the explanations.
| Bloque de código |
|---|
cmake ../ [additional parameters] |
Parameter explanations
path to your OpenSSL library - do not use if you have OpenSSL installed system wide:
| Panel |
|---|
-DOPENSSL_LIBRARIES=<path to OpenSSL library> |
path to your OpenSSL includes directory - do not use if you have OpenSSL installed system wide:
| Panel |
|---|
-DOPENSSL_INCLUDE_DIR=<path to OpenSSL includes> |
...
Note : * means "used by default", and does not need to be set.
The above parameters when combined into a full example :
| Bloque de código |
|---|
cmake ../ -DCMAKE_INSTALL_PREFIX=/home/<username>/server -DWITH_WARNINGS=1
Another Example Below:
cmake ../ -DCMAKE_INSTALL_PREFIX=/home/wow/server -DCONF_DIR=/home/wow/server/etc -DTOOLS=1 -DWITH_WARNINGS=1 |
The above build the tools, set installation base directory to /home/<username>/server and show all warnings during compile.
Note that you WILL have to configure the server well if you ever want to use the RA-access functionality.
Building the core
After configuring and checking that everything is in order (read cmakes output), you can build Trinity (this will take some time unless you are on a rather fast machine)
| Bloque de código |
|---|
make
make install |
If you have multiple CPU cores, you can enable the use of those during compile :
| Bloque de código |
|---|
make -j <number of cores>
make install |
Alternatively:
| Bloque de código |
|---|
make -j$(nproc) install |
After compiling and installing, you will find your core binaries in /home/<username>/server/bin, and the standard configuration files in the /home/<username>/server/etc folder.
(As usual, replace <username> with the username you created earlier). Now you can continue reading on and learn how how to update the source tree.
Keeping the code up to date
TrinityCore developers are always at work fixing and adding new features to the core. You can always check them here. To update the core files, do the following :
| Bloque de código |
|---|
cd ~/TrinityCore/
# For 3.3.5 Branch
git pull origin 3.3.5
# For 6.x Branch
git pull origin 6.x |
Now return to the compilation-section again, and repeat the instructions there.
Installing MySQL Server
When configuring MySQL make sure you remember the password you set for the default root account and that you enabled both MyISAM and InnoDB engines.
You can leave all the other settings as default. You might want to enable remote access to your MySQL server if your are also testing a website for your Trinity server or if you have friends testing with you which need access from remote. Remember that this will decrease the security level of your MySQL server!
SPECIAL NOTES!
Things to notice :
| Panel |
|---|
-DSSLLIB=<path> has been deprecated and is not used at all (remove this if ever used before) |
The new method for custom SSL-libraries are:
| Panel |
|---|
-DOPENSSL_LIBRARIES=<path to OpenSSL libraries directory> |
The paths for installation can be done without any other parameters but this :
| Panel |
|---|
-DCMAKE_INSTALL_PREFIX=/path/to/where/you/want/core/to/be/installed |
It will create the following structure:
| Panel |
|---|
<path>/bin/ - binaries will be placed here |
Also, compile has been tested on Debian 8 x32/x64, Ubuntu 15.04 x64 - all without problems IF YOU DO NOT MESS AROUND ON YOUR OWN!
| Nota |
|---|
Please remember to rename the worldserver.conf.dist and authserver.conf.dist files in worldserver.conf and authserver.conf respectively, unless you want to keep the configuration files of a previously compiled version of the core. |
OS X
Getting started
This guide describes how to get TrinityCore running on OS X. OS X ships with several libraries including OpenSSL and a special version of Readline - both required by TrinityCore. But: They are useless. OpenSSL is too old and Readline is... well... special. So we have to build the right ones. This is fairly easy and by doing this on your own (using programs like MacPorts or Homebrew is the alternative) you may learn more about libraries, your Mac and its handling on a non-graphic way. But no matter what you're doing in this guide there is one rule you should remind and never ever break:
...
Open the generated "TrinityCore.xcodeproj" and select "Product" -> "Build" for a Debug build or "Product" ->"Archive" for a Release build. Do not forget to select "install" as compilation target.
Keeping the code up to date
| Bloque de código |
|---|
cd $TRINITY/repo git reset --hard HEAD git pull |
...
Windows
| Sección | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
...