From e9a05e2e4be9561c76d098f07a3698227b0f5fbe Mon Sep 17 00:00:00 2001
From: Uleat This guide provides instructions for compiling 32-bit Windows server binaries and setting up a local development server.Compiler Setup
[need to develop criteria]
+ +Some of the pre-requisits for compiling binaries are the same as running a server.
+ +If you have already installed any of the following, the download and installation requirement should be omitted.
+ +Visual Studio 2017 Community Edition (see notes under install) [select Visual Studio 2017 Community Edition]
MariaDB [download]
Perl [download]
CMake [download]
Git (see notes under install) [download]
TortoiseGit (optional - see notes under install) [download]
During the install process, double-check the option for c++ command-line compiler. This is required by CMake to determine available compiler options. CMake file generation will fail if this option is not enabled.
+ +[screenshot of option]
+ +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.
+ +[need specifics on what settings to use]
+ +At the end of the installation process, you will be prompted to install HeidiSQL. It is HIGHLY recommended that you install this program.
+ +This installation is self-explanatory. It is recommended that you install in the root directory ("c:\") to avoid possible issues.
+ +This installation is self-explanatory.
+ +This installation is self-explanatory.
+ +Note: Should you wish to download the repository code with no further chance of updating or restoration, this requirement may be omitted.
+ +This installation is self-explanatory.
+ +Note: If Git is not installed, this installation should be omitted.
+ +You will need to restart your computer to ensure that all of the %PATH% additions are loaded into memory.
+ +At this point, you will need to make a decision on how you want to manage your code.
+ +There are three options:
+ +Option 1, Retrieve the code as a one-time download (not recommended)
Option 2, Create a local repository from the parent EQEmulator project that can be updated, managed and maintained (recommended)
Option 3, Create a local repository from a fork of the EQEmulator project that you manage (recommended only if you want to contribute back to the parent project)
Note: If you choose to create a fork of the EQEmulator repository, you will need to create a [github.com] account.
+ +[walk-through for option 2]
+ +Library dependencies can be downloaded directly from [here].
+ +Inside of your local code directory, you will need to create a sub-directory called 'dependencies` and unzip the download's contents into it.
+ +[walk-through]
+ +[walk-through]
+ +