Clockworks Gaming Archive 4.0.6_4.1.0_4.2.2_4.3.0_4.3.4_5.1.0
Welcome to my dev archive. I hope you find what your looking for. Kind regards _Ikester_
Search
 
 

Display results as :
 


Rechercher Advanced Search

Latest topics
» phoenix-w7r8
Wed Nov 05, 2014 12:05 am by _IKESTER_

» Please come visit my new site
Tue Jul 22, 2014 3:45 pm by _IKESTER_

» 5.1.0 Mop_Eve_online multi server.
Thu Jun 26, 2014 3:26 am by _IKESTER_

» Clockworks cata updated 2014
Sat Jan 11, 2014 3:23 pm by _IKESTER_

» {Release} Tree Trinity 3.3.5 Stable Playerbots v17
Mon Dec 09, 2013 5:23 pm by _IKESTER_

» 2500_PHP_SCRIPTS_MEGA_PACK
Thu Oct 31, 2013 11:27 am by _IKESTER_

» 5000 Web Templates Incl. Php,Flash,_Ikester_.rar
Thu Oct 31, 2013 11:25 am by _IKESTER_

» Top wow addons
Sun Oct 27, 2013 1:26 pm by _IKESTER_

» Large lua script bundle for arcemu.
Mon Oct 21, 2013 10:15 am by _IKESTER_

Navigation
 Portal
 Index
 Memberlist
 Profile
 FAQ
 Search
February 2017
MonTueWedThuFriSatSun
  12345
6789101112
13141516171819
20212223242526
2728     

Calendar Calendar

IKESTER

[HOWTO] Compile Trinity Core

View previous topic View next topic Go down

[HOWTO] Compile Trinity Core

Post by EVIL MONKEY on Tue Jan 18, 2011 5:40 pm

[HOWTO] Compile Trinity Core



Before you start this phase you need to have installed TortoiseHG and Visual Studio.

Step 1.
Create a directory in which Core files will be pulled (for example: C:\Trinity).
Right-click on the directory and click on 'TortoiseHG' -> 'Clone a Repository'.
Fill in the data as follows:

Quote:
Source Path: https://trinitycore.googlecode.com/hg/trinitycore
Destination Path: C:\Trinity
Click on 'clone'. Wait a few minutes (or less) and all the files will be pulled in the directory C:\Trinity.

Configuring and Generating Visual Studio solutions with CMake

Note:
- For OpenSSL, do NOT use the light version
- For MySQL, do NOT use the "essential"-version.As quoted on the MySQL page:
The Windows "msi-essential-*" installers do not include: Instance Manager tool, Documentation, Development headers



Open the CMake GUI. (window will look like the above screenshot)
The two top text areas are used to tell where CMake should look for the source tree, and also where to put the build files.
Now set the source to where you have checked out the Trinity sourcecode (in this case C:/Trinity), and then set the Build directory to where you have created your dedicated folder (in this case D:/Build) using the Browse buttons as in the below screenshots:

Step 2.





When you have set the source and build directories, you can click Configure.




After clicking Finish it will start chewing through the source code and analyze the CMakeLists.txt spread all over the source tree.



When done it will show you a list of options which it wants you to confirm (the red parts shown below).
Go through them and check/uncheck those you want enabled/disabled (you can hover the options to see what they are used for).
The default ones are shown below, and we do not advice you to turn off SERVERS as it selects the actual server-daemons

Now you've most probably have also seen some text in the large white textbox.
You will find notifications from CMake here, and also information about what it has found / not found of libraries/headers and the likes.
In our case, we have a fully installed system:
- it detects that we're on a 64-bit platform
- it detects that we have a proper version of MySQL with development-libraries and headers installed (for 64-bit systems)
- it detects that we have a properly installed OpenSSL libraries/headers -installation
In short, it's happy about our setup, but still wants us to verify the information.
In other words it wants us to click on Configure again to verify what it has detected.



When CMake has verified the information, and not found any more "errors" that it wants to complain about, it'll remove the red stuff, and wait for further input.
Click on Generate, and it will happily start chugging away and creating the solutionfiles/projectfiles/makefiles it requires to build for that specific compiler.



When done, it'll state "Generating done", and let you start compiling from the generated solution files.



So, open the build folder, and open the solution file, as shown underneath here. And proceed to the next step - Compiling the Source.



Compiling the Source
Go on the top menu 'Build' and click on Configuration Manager. Make sure you set the build to 'release Win32' or 'release x64' depending on the Operating System Trinity will be running on and what you have set during CMake configuration.
Warning: Visual C++ 2008 Express edition does not support the 64 bit platform. You will need to install the full Visual Studio, as well as additional components to enable 64 bit support. Refer to Microsoft's website and documentation for more details.
Now go back to the 'Build' menu and click on 'Clean Solution'. Unless you are just testing a compilation, it is always best to clean your build before compiling your new Trinity revision. Compilation length differs from machine to machine, you should expect it to take 15-30 minutes.
You will find the following message once the compilation has finished successfully:

Quote:
========== Build: 14 completed, 0 failed, 0 up-to-date, 1 skipped ==========
You will find your freshly compiled binaries in the D:\build\ folder as we have specified during the CMake configuration process.
Keep the following files:

Quote:
ACE.dll
libeay32.dll
libmySQL.dll
ssleay32.dll
README
worldserver.conf.dist
worldserver.exe
authserver.conf.dist
authserver.exe
Delete any other file which is not in the above list, you will not need them.

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 or by using the ToroiseHG View Changelog option.
Simply right-click on your C:\Trinity folder and click on 'TortoiseHG' -> 'Synchronize'. Click on the button 'pull' at top of the window and it will start pulling the new/updated files. Once it is finished click on 'Update to Branch Tip' at the bottom of the window and you are done! Now you can repeat the compiling procedure above.
It is always best to remove the binaries from the C:\Trinity\bin folder every time you compile a new revision (and remember to clean your build).

Credit to trinitycore's Wiki

EVIL MONKEY
GLOBAL MOD
GLOBAL MOD

Posts : 26
Points : 37049
Reputation : 7368
Join date : 2010-01-09

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum