Jump to content

Question

This guide is for Release 21 (0.21.0) version of Mangos.

This guide explains how to get the source code from our git repositories and compile and run with a default config.

This guide assumes you have set-up a database and user accounts for it.

Before running the server, you need to run the extractor and put dbc, vmaps, maps and if you have them, mmaps in the folder with the server files.

Required Files

  • Git for windows - Git - Downloads
    Install making sure the following options are selected Windows explorer intergration - Simple context menu (Git bash, Git GUI)
  • Microsoft Visual Studio Community 2015 - Free Dev Tools - Visual Studio Community 2015
    • Install with default options selecting C++ when it asks you what programming language you are using

    [*]Notepad++ - http://notepad-plus-plus.org

    Useful for editing .conf files and any other editable files.

    [*]Additional required files are downloaded while cloning the repo

Getting the source code

Mangos Zero will be used for this guide.

  • Browse to where you would like to clone the files
  • Right click inside a blank area in the folder and select "Git Bash Here"
  • In the black command box type
    [b]git clone --recursive https://github.com/mangoszero/server -b develop21[/b]


    This will clone the latest Sever source into a folder called server - Including the --recursive is very important!
    git-clone.jpg

Installing the additional requirements

  • Go into the new Server / win folder
    It should have these files listed
    Server-winfolder.jpg
  • Install: Cmake, mysql and openSSL (which version depends on if you are running x32 or x64 [x32 being more stable]).
    • Default options are fine in most cases.

MaNGOS EasyBuild

  • Run MaNGOS_EasyBuild.exe located in server/win
  • Easy Build main screen
    Mangos_easybuild.jpg
  • Click the "check now" button
    EasyBuild_checked.jpg
    You should see green ticks and if you have everything done correctly you should be able to go to the build options page.
  • Once on the build options page tick the "Include PlayerBot AI", if you are certain you are not going to use this feature then leave unticked.
    EasyBuild_ProjectOptions.jpg
  • Clicking generate project will run cmake but inside of the EasyBuild application, you will see the output.
  • Visual studio should be started when it is finished generating.

Output showing EasyBuild with the option to automatically open visual studio unticked

EasyBuild_output.jpg

If you wish to compile at a later time the built files will be under /server_build/ you just need to double click on MaNGOS.sln

Compiling the source code

  • Visual studio
    Visual_stuio.jpg
  • Once the project has loaded go to the drop down just below the team menu and select Release and Win32
    Build_option.jpg
  • Press F7 or go to the Build menu and select Build Solution

The Mangos server is now compiling and time to go get a coffee, this process should take around 5-30 minutes depending on your system. Older single core systems will take longer.

[ATTACH=CONFIG]86[/ATTACH]

That's it! now head into the /server_build/bin / Win32_Release folder and your server files will be there.

git-clone.jpg.5ec9f177b524568e4508b8db89

Server-winfolder.jpg.614058a25472d24a516

Mangos_easybuild.jpg.40f611ba22a5914b949

EasyBuild_checked.jpg.ae11c92b560d050d71

EasyBuild_ProjectOptions.jpg.bc5d2742aed

EasyBuild_output.jpg.f4e41cd7213891623a3

Visual_stuio.jpg.7dad9570c53d19ccf0c2806

Build_option.jpg.f8efbe9ea8e30be912ce04c

Link to comment
Share on other sites

7 answers to this question

Recommended Posts

Thx for the source code. Damn how many people work on this project? Are you from Vatican? I mean the whole structure of the source code is different from the source code of Release 20. Yeah - so it is impossible actually to work further on Release 20 because the whole structure changed that significant that all the mistakes I corrected in Release 20 can not be integrated easily in Release 21 or it is impossible to integrate the changes of Release 21 into Release 20. That makes sense. But only if you work for the Vatican.

Link to comment
Share on other sites

Thx for the source code. Damn how many people work on this project? Are you from Vatican? I mean the whole structure of the source code is different from the source code of Release 20. Yeah - so it is impossible actually to work further on Release 20 because the whole structure changed that significant that all the mistakes I corrected in Release 20 can not be integrated easily in Release 21 or it is impossible to integrate the changes of Release 21 into Release 20. That makes sense. But only if you work for the Vatican.

Rel20 is considered dead to us. It is to be dropped or moved into a archive later this month. The R21 will become Master.

Link to comment
Share on other sites

Yeah - so it is impossible actually to work further on Release 20 because the whole structure changed that significant that all the mistakes I corrected in Release 20 can not be integrated easily in Release 21 or it is impossible to integrate the changes of Release 21 into Release 20.

The solution is so simple that the problem was never considered as one by the staff. PR your fixes to the Zero repo after a brief local testing period of few days, and keep your sources up to date with the current Develop branch.

Link to comment
Share on other sites

so it is impossible actually to work further on Release 20 because the whole structure changed that significant that all the mistakes I corrected in Release 20 can not be integrated easily in Release 21 or it is impossible to integrate the changes of Release 21 into Release 20.

It should be possible to merge all the develop21 changes into release20 - at that point, your code will be up to date with the latest mangos.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use