Although I deliver a core trinity already compiled you may want or need to compile it yourself, to make your own mod / debug or because you are under another system. Here are the dependencies and utilities needed to compile the 6.2.4 core. This can be done in visual studio 2013 as in visual studio 2015 or 2017.
Before starting it is important not to mix the x86 (32bit) and x64 (64bits) versions when the choice is possible. This is not the case for example for Cmake which is only in x86. Below the examples are given for windows x64.
The link for a compilation on a 64 bit system:
https://sourceforge.net/projects/boost/f...es/1.63.0/
Choose boost_1_63_0-msvc-12.0-64.exe for a compilation under visual studio 2013 and a 64 bit system
At a minimum you will need version 1.59, trinity recommends 1.60 which resolves a problem with ASIO. Personally I use 1.63
Beware of the name ... many have problems because they chose the wrong version. Example: boost_1_63_0-msvc-12.0-64.exe, 12 indicates visual studio version 12 (2013) and 64 indicates a 64x system
The link for a compilation on a 64 bit system: MySQL :: Download MySQL Community Server
Use a 5.6x version, especially not the problematic version 5.7
The link for a compilation on a 64 bit system: Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions
Always take a version in V1.0.x, never a light version or V1.1.x. Win64 OpenSSL v1.0.2j example
At installation choose the / bin folder rather than the windows system folder
Visual Studio 2015
Visual Studio 2015 update 3 Click HERE
In order to prepare the sources for visual sudio (because these can be used on several x86, x64, Linux, Mac, ... systems) you will need version 3.3.2 of Cmake, avoid another even higher version which can be a problem.
Link to Cmake: choose cmake-3.3.2-win32-x86.zip or cmake-3.3.2-win32-x86.exe, whether you are x86 or x64
In this one once all the dependencies installed and just before compilation you will need:
First click on "Configure" and choose your Visual studio: version + x86 or x64, it may be that an error occurs this is normal, it occurs because all dependencies are not specified.
Check the boxes SCRIPT, SERVERS, TOOLS (to compile the map extraction tools, etc.),
In SCRIPT pass all the options on static otherwise some script will not be automatically included in the core
Click on Generate to generate the solution for your visual studio, if an error occurs this product check the dependency paths. Pay close attention to the slach "/" and anti shash "\". If an error occurs again check that you are using the correct version and x64 or x86 format of your dependencies.
For informations :
The environment variables must be created during the installation of the dependencies but this is not necessarily the case, to check therefore if you encounter problems.
Installing / uninstalling multiple versions can also create problems at this level.
These environmental variables are taken into account after restarting your PC
Below my environment variables, it's up to you to adapt your paths:
Credit to : Stitch from Aquayoup
Before starting it is important not to mix the x86 (32bit) and x64 (64bits) versions when the choice is possible. This is not the case for example for Cmake which is only in x86. Below the examples are given for windows x64.
The outbuildings
BOOST
BOOST
The link for a compilation on a 64 bit system:
https://sourceforge.net/projects/boost/f...es/1.63.0/
Choose boost_1_63_0-msvc-12.0-64.exe for a compilation under visual studio 2013 and a 64 bit system
At a minimum you will need version 1.59, trinity recommends 1.60 which resolves a problem with ASIO. Personally I use 1.63
Beware of the name ... many have problems because they chose the wrong version. Example: boost_1_63_0-msvc-12.0-64.exe, 12 indicates visual studio version 12 (2013) and 64 indicates a 64x system
Citation :
Environment variables :
BOOST_ROOT : C:\Core-trinity\boost_1_63_0
BOOST_INCLUDE_DIR : C:\Core-trinity\boost_1_63_0
BOOST_LIBRARYDIR : C:\Core-trinity\boost_1_63_0\lib64-msvc-14.0\libboost_filesystem-vc120-mt-1_63.lib
Boost_DIR : C:\Core-trinity\boost_1_63_0
CMAKE :
Boost_Dir C:/Core-trinity/boost_1_63_0
Boost_filesystem_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_filesystem-vc120-mt-gd-1_63.lib
Boost_filesystem_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_filesystem-vc120-mt-1_63.lib
Boost_include_dir C:/Core-trinity/boost_1_63_0
Boost_iostreams_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_iostreams-vc120-mt-gd-1_63.lib
Boost_iostreams_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_iostreams-vc120-mt-1_63.lib
Boost_Library_Dir C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0
Boost_program_option_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_program_options-vc120-mt-gd-1_63.lib
Boost_program_option_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_program_options-vc120-mt-1_63.lib
Boost_regex_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_regex-vc120-mt-gd-1_63.lib
Boost_regex_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_regex-vc120-mt-1_63.lib
Boost_system_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_system-vc120-mt-gd-1_63.lib
Boost_system_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_system-vc120-mt-1_63.lib
Boost_thread_library_debug C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_thread-vc120-mt-gd-1_63.lib
Boost_thread_library_release C:/Core-trinity/boost_1_63_0/lib64-msvc-12.0/libboost_thread-vc120-mt-1_63.lib
Mysql
The link for a compilation on a 64 bit system: MySQL :: Download MySQL Community Server
Use a 5.6x version, especially not the problematic version 5.7
Citation :
Environment variables:
MYSQL_DIR : C:\Core-trinity\mysql-5.6.38-winx64
MYSQL_INCLUDE_DIR : C:\Core-trinity\mysql-5.6.38-winx64\include
MYSQL_LIBRARY : C:\Core-trinity\mysql-5.6.38-winx64\lib\libmysql.lib
CMAKE :
MYSQL_EXECUTABLE : C:/Core-trinity/mysql-5.6.38-winx64/bin/mysql.exe
MYSQL_INCLUDE_DIR : C:/Core-trinity/mysql-5.6.38-winx64/include
MYSQL_LIBRARY : C:/Core-trinity/mysql-5.6.38-winx64/lib/libmysql.lib
OPENSSL
The link for a compilation on a 64 bit system: Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions
Always take a version in V1.0.x, never a light version or V1.1.x. Win64 OpenSSL v1.0.2j example
At installation choose the / bin folder rather than the windows system folder
Citation :
Environment variables :
OPENSSL_CONF : C:\Core-trinity\OpenSSL-Win64\bin\openssl.cfg
Cmake :
OPENSSL_ROOT_DIR : C:/Core-trinity/OpenSSL-Win64
OPENSSL_INCLUDE_DIR : C:/Core-trinity/OpenSSL-Win64/include
Tools for compiling
Visual Studio 2015
Visual Studio 2015 update 3 Click HERE
Citation:
Environment variables / Cmake:
VS120COMNTOOLS: C: \ Program Files (x86) \ Microsoft Visual Studio 12.0 \ Common7 \ Tools \
Cmake
In order to prepare the sources for visual sudio (because these can be used on several x86, x64, Linux, Mac, ... systems) you will need version 3.3.2 of Cmake, avoid another even higher version which can be a problem.
Link to Cmake: choose cmake-3.3.2-win32-x86.zip or cmake-3.3.2-win32-x86.exe, whether you are x86 or x64
In this one once all the dependencies installed and just before compilation you will need:
First click on "Configure" and choose your Visual studio: version + x86 or x64, it may be that an error occurs this is normal, it occurs because all dependencies are not specified.
Check the boxes SCRIPT, SERVERS, TOOLS (to compile the map extraction tools, etc.),
WITHOUT_GIT
(since we don't use git but local sources).In SCRIPT pass all the options on static otherwise some script will not be automatically included in the core
Click on Generate to generate the solution for your visual studio, if an error occurs this product check the dependency paths. Pay close attention to the slach "/" and anti shash "\". If an error occurs again check that you are using the correct version and x64 or x86 format of your dependencies.
For informations :
The environment variables must be created during the installation of the dependencies but this is not necessarily the case, to check therefore if you encounter problems.
Installing / uninstalling multiple versions can also create problems at this level.
These environmental variables are taken into account after restarting your PC
Below my environment variables, it's up to you to adapt your paths:
Credit to : Stitch from Aquayoup
Last edited by a moderator: