ET: Legacy Development

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).

• Fix "chmod: cannot access './legacy/omni-bot/': No such file or directory" error
• Fix wIn installaler Polish translation
• Fix WA default config + DB creation (done)

The WA achive shouldn’t be entirely extracted in the mod folder, but correctly installed. (done)

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.

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}