yolinlin/mod-ale
1
0
Fork 0
mirror of https://github.com/azerothcore/mod-ale synced 2025-11-29 15:38:17 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update INSTALL.md

Browse Source
This commit is contained in:
Rochet2
2014-03-23 23:05:42 +02:00
committed by Foereaper
parent f07521a1aa
commit d4d3aa8a84
1 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/INSTALL.md
View File

@@ -7,25 +7,24 @@ Get the core:<br/>
[![Build Status](https://travis-ci.org/eluna-dev-mangos/ElunaCoreTbc.png?branch=master)](https://travis-ci.org/eluna-dev-mangos/ElunaCoreTbc) [Eluna cMaNGOS TBC](https://github.com/eluna-dev-mangos/ElunaCoreTbc)<br />
[![Build Status](https://travis-ci.org/eluna-dev-mangos/ElunaCoreWotlk.png?branch=master)](https://travis-ci.org/eluna-dev-mangos/ElunaCoreWotlk) [Eluna cMaNGOS WotLK](https://github.com/eluna-dev-mangos/ElunaCoreWotlk)
On **TrinityCore** navigate to `\src\`<br />
On **MaNGOS** navigate to `\src\game\`<br />
Open `git bash` and do
Open `git bash` in `LuaEngine` folder and do
1. `git init`
2. `git remote add origin https://github.com/ElunaLuaEngine/Eluna`
3. `git pull origin master`
1. `git submodule init`
2. `git submodule update`
3. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
Compile the core normally (use cmake on TC)
Compile the core normally (use cmake if needed)
#Updating
When updating you should take up the `commit hashes` you are on, just in case.
When updating you should take up the `commit hash` you are on, just in case.
You can get it from git with `git log` for example.
Use this when git is open in the source folder as well as in LuaEngine folder.
You should take note what are the newest SQL updates in `sql/updates/*` folders.
Use `git pull` in core source and in LuaEngine folder to get the newest source changes and Eluna from github.
1. Use `git pull` to get the newest source changes.
2. Then use `git submodule update` to update Eluna from github.
3. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
Try compiling and if you encounter errors, report to [support](https://github.com/ElunaLuaEngine/Eluna#links) or [issues](https://github.com/ElunaLuaEngine/Eluna/issues).
You can revert back to the old sources by using `git reset --hard 000000`, where 000000 is the `commit hash`.
You can revert back to the old sources by using `git reset --hard 000000` `git submodule update`, where 000000 is the `commit hash`.
If the compiling was successful, you should update your database if needed.
You can do this by running all **new** SQL files in `sql/updates/*`.