From c38e275ab7123d30075993d50d8a08c447486997 Mon Sep 17 00:00:00 2001
From: Uleat The current c/c++ support standard of the EQEmulator server code base mandates the use of Visual Studio 2013 or later compilers. Visual Studio 2017 is the current standard for binary compilation. Please ensure that your system meets the Visual Studio 2017 Minimum System Requirements. Visual Studio 2017 is the current EQEmulator standard for binary compilation. Please ensure that your system meets the Visual Studio 2017 Minimum System Requirements. If your system does not meet the above requirements, or you are/would like to use an older version of Visual Studio, check the minimum system requires for the version you plan to use. (It must still meet the Visual Studio 2013 or later requirement of the code base.) If your system does not meet the above requirements, or you are/would like to use an older version of Visual Studio, check the minimum system requirements for the version you plan to use. (It must still meet the Visual Studio 2013 or later requirement of the code base.) This setup assumes an install on a 64-bit Windows operating system with 32-bit target binaries. Sometimes an automated server installation will fail due to the %Path% variable being full. This can happen with a manual installation as well. Since this guide installs more programs than are required to just operate a server, verifying the length of %Path% is critical before we start. Since this guide installs more programs than are required for server operation, verifying the length of %Path% is critical before we start. Visual Studio 2017 Community Edition (see note under install) [select Visual Studio 2017 Community Edition] Visual Studio 2017 Community Edition [select Visual Studio 2017 Community Edition] MariaDB (64-bit) [download] Some programs may be able to use newer versions, or even the lastest releases, without issue. But, this is not the case with Perl and (later) dependencies. Note: Microsoft now requires a user account to download Visual Studio. Clicking the Visual Studio link above will take you to the 'older versions' page. Clicking the download button on this page will prompt you to log in or create an account. [back] The above list of programs is known to work for compiling working server binaries. Note: TortoiseGit is a menu-driven, add-on gui interface for Git. Though optional, this instructional provides for its use. Note: TortoiseGit is a menu-driven, add-on gui interface for Git. Though optional, this instructional provides for its use. Some programs may be able to use newer versions, or even the lastest releases, without issue. But, this is not the case with Perl and (later) dependencies. The above list of programs is known to work for compiling working server binaries. Note: Microsoft now requires a user account to download Visual Studio. Clicking the Visual Studio link above will take you to the 'older versions' page. Clicking the download button on this page will prompt you to log in or create an account. [back] For other options, go to the EQEmulator server code repository web page at https://github.com/EQEmu/Server For options 2 & 3, go to the EQEmulator server code repository web page at https://github.com/EQEmu/Server
@@ -74,9 +74,7 @@
-
-
-
-
-
@@ -116,10 +116,6 @@
-
-
-
Install MariaDB
-
@@ -264,7 +260,89 @@
Running CMake
[walk-through]
+CMake's default options are adequate to configure and generate the files needed for Visual Studio.
+ +There are two directory locations that you will need to provide:
+ +Where is the source code:
Where to build the binaries:
For the source code, type-in or navigate to your 'c:/<account>/Server' directory.
+ +The easiest way to define the build directory is to copy the source and paste it in. Then, add '/build' to the end of the path so that you have 'c:/<account>/Server/build'.
+ +Once CMake knows where to look, click the 'Configure' button. You will get a pop-up window stating that the 'build' directory does not exist. Click 'OK' to create it.
+ +The next window will be for the compiler selection. Ensure that 'Visual Studio 15 2017' is selected.
+ +
+
+You should now have a list of unconfigured options (in red) showing in the main window of CMake:
+ +
+
+The follow list contains pertinent options that most users will want to change:
+ +Once you have set the options that you would like for your server, click 'Configure' again.
+ +Since we set an option (login server) that requires additional settings, more unconfigured options have appeared. In this case, the open ssl library:
+ +
+
+Since these new options are only file path declarations, no changes need to be made. Click 'Configure' one last time.
+ +
+
+Note: Regardless of option settings, anytime that you have red (unconfigured) entries in your options list, you will need to click 'Configure' to ensure that the settings are applied to the current CMake file generation template.
+ +You can now click the 'Generate' button.
+ +If file generation was successful, you should see 'Generating done' at the bottom of the CMake window.
+ +You are now ready to open Visual Studio and compile your code!