Task #975
Add WolfAdmin to installers
| Status: | Feedback | % Done: | 80% | ||
|---|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | ||
| Assignee: | - | ||||
| Category: | General | ||||
| Target version: | 2.78 | ||||
| OS: | Arch: |
Description
Let’s add our prefered game manager to the installs.
Related issues
Associated revisions
cmake: add WolfAdmin to installers, refs #975
misc: fix cmake scripts for geoip, ob & wa
misc: fixed WolfAdmin install path, refs #975
misc: updated WolfAdmin md5sum, refs #975
History
#1
Updated by IR4T4 almost 3 years ago
- Related to Feature #932: Tighter interface with Lua admin suite added
#2
Updated by Timothy almost 3 years ago
- Subject changed from Add WoldAdmin to installers to Add WolfAdmin to installers
#3
Updated by Spyhawk almost 3 years ago
From #217:
IR4T4 wrote:
We should ask the OB team to change their code and read the OB config file from fs_homepath first. If there is no file in fs_homepath the fs_basepath file is failback case.
There is a similar issue with WolfAdmin. We should ensure it takes fs_basepath as fallback (for config files, maybe database too).
#4
Updated by Spyhawk almost 3 years ago
- Related to Task #974: Release 2.76 "The enemy is weakened!" added
#5
Updated by Spyhawk almost 3 years ago
- Related to Feature #183: New referee menu for Omni-bot control added
#6
Updated by Spyhawk over 2 years ago
- Fix "chmod: cannot access './legacy/omni-bot/': No such file or directory" error
Fix wIn installaler Polish translationFix WA default config + DB creation(done)
#7
Updated by IR4T4 over 2 years ago
- Related to Bug #1010: Engine db_mode 1 isn't accessible from mod and LuaSQL added
#8
Updated by IR4T4 over 2 years ago
- % Done changed from 0 to 80
#9
Updated by Spyhawk over 2 years ago
The WA achive shouldn’t be entirely extracted in the mod folder, but correctly installed. (done)
#10
Updated by illwieckz about 1 year ago
I tried to compile ET: Legacy using easybuild.sh but it fails on WolfAdmin extraction step:
-- Installing WolfAdmin
-- Downloading WolfAdmin archive to /home/illwieckz/dev/etlegacy/build/legacy/wolfadmin.tar.gz
-- [download 1% complete]…
-- [download 100% complete]
-- Extracting WolfAdmin archive to /home/illwieckz/dev/etlegacy/build/legacy/wolfadmin
CMake Error at cmake/ETLInstallWolfAdmin.cmake:19 (file):
file COPY cannot find
"/home/illwieckz/dev/etlegacy/build/legacy/wolfadmin/luamods".
Call Stack (most recent call first):
CMakeLists.txt:168 (include)
CMake Error at cmake/ETLInstallWolfAdmin.cmake:22 (file):
file COPY cannot find
"/home/illwieckz/dev/etlegacy/build/legacy/wolfadmin/lualibs".
Call Stack (most recent call first):
CMakeLists.txt:168 (include)
-- Adding WolfAdmin to installer scripts
-- ***********************************************************
-- Genuine ET files are not copied - ET: Legacy won't start !!!
-- In order to start the game copy
-- pak0.pk3, pak1.pk3 and pak2.pk3
-- to ./etmain
-- ***********************************************************
-- Configuring incomplete, errors occurred!
See also "/home/illwieckz/dev/etlegacy/build/CMakeFiles/CMakeOutput.log".
Exiting!The CMakeOutput.log seems to have nothing related to WolfAdmin:
$ grep -ir wolfadmin /home/illwieckz/dev/etlegacy/build/CMakeFiles/CMakeOutput.log
ØThe wolfadmin.tar.gz file is correctly downloaded, stored with the right name and expected path, and listable.
#11
Updated by illwieckz about 1 year ago
Wait, I just did that in cmake/ETLFunctions.cmake and it now works, that makes no sense:
- COMMAND ${CMAKE_COMMAND} -E tar -xzf ${_PATH}
+ COMMAND ${CMAKE_COMMAND} -E tar -xvzf ${_PATH}#14
Updated by IR4T4 11 months ago
- Related to deleted (Feature #183: New referee menu for Omni-bot control)