mirror of
https://github.com/azerothcore/mod-ale
synced 2025-11-29 15:38:17 +08:00
Update INSTALL.md
This commit is contained in:
@@ -1,32 +1,27 @@
|
|||||||
#Installation
|
#Installation
|
||||||
Get the core:<br/>
|
1. Get the core:<br/>
|
||||||
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Wotlk) [Eluna TrinityCore WotLK](https://github.com/ElunaLuaEngine/Eluna-TC-Wotlk)<br />
|
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Wotlk) [Eluna TrinityCore WotLK](https://github.com/ElunaLuaEngine/Eluna-TC-Wotlk)<br />
|
||||||
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Cata) [Eluna TrinityCore Cataclysm](https://github.com/ElunaLuaEngine/Eluna-TC-Cata)
|
[](https://travis-ci.org/ElunaLuaEngine/Eluna-TC-Cata) [Eluna TrinityCore Cataclysm](https://github.com/ElunaLuaEngine/Eluna-TC-Cata)<br />
|
||||||
|
|
||||||
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreClassic) [Eluna cMaNGOS Classic](https://github.com/eluna-dev-mangos/ElunaCoreClassic)<br />
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreClassic) [Eluna cMaNGOS Classic](https://github.com/eluna-dev-mangos/ElunaCoreClassic)<br />
|
||||||
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreTbc) [Eluna cMaNGOS TBC](https://github.com/eluna-dev-mangos/ElunaCoreTbc)<br />
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreTbc) [Eluna cMaNGOS TBC](https://github.com/eluna-dev-mangos/ElunaCoreTbc)<br />
|
||||||
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreWotlk) [Eluna cMaNGOS WotLK](https://github.com/eluna-dev-mangos/ElunaCoreWotlk)
|
[](https://travis-ci.org/eluna-dev-mangos/ElunaCoreWotlk) [Eluna cMaNGOS WotLK](https://github.com/eluna-dev-mangos/ElunaCoreWotlk)
|
||||||
|
|
||||||
Open `git bash` and do
|
2. Open `git bash` and do
|
||||||
|
`git submodule init`
|
||||||
1. `git submodule init`
|
`git submodule update`
|
||||||
2. `git submodule update`
|
5. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
|
||||||
3. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
|
6. Compile the core normally (use cmake if needed)
|
||||||
|
|
||||||
Compile the core normally (use cmake if needed)
|
|
||||||
|
|
||||||
#Updating
|
#Updating
|
||||||
When updating you should take up the `commit hash` you are on, just in case.
|
1. 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.
|
You can get it from git with `git log` for example.
|
||||||
You should take note what are the newest SQL updates in `sql/updates/*` folders.
|
You should take note what are the newest SQL updates in `sql/updates/*` folders.
|
||||||
|
2. Use `git pull` to get the newest source changes.
|
||||||
1. Use `git pull` to get the newest source changes.
|
3. Then use `git submodule update` to update Eluna from github.
|
||||||
2. Then use `git submodule update` to update Eluna from github.
|
4. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
|
||||||
3. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master`
|
5. Try compiling and if you encounter errors, report to [support](https://github.com/ElunaLuaEngine/Eluna#links) or [issues](https://github.com/ElunaLuaEngine/Eluna/issues).
|
||||||
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` `git submodule update`, 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`.
|
||||||
|
6. If the compiling was successful, you should update your database if needed.
|
||||||
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/*`.
|
You can do this by running all **new** SQL files in `sql/updates/*`.
|
||||||
You need to see your notes from before pulling the updates or you can use the old commit hash to see on github what were the last files you ran.
|
You need to see your notes from before pulling the updates or you can use the old commit hash to see on github what were the last files you ran.
|
||||||
An easy way is to just look at the created/modified date on the files.
|
An easy way is to just look at the created/modified date on the files.
|
||||||
|
|||||||
Reference in New Issue
Block a user