I compile it (and tweak some of the code) for my personal use. I think if you are a Linux user, you should just DIY, since that's sort of the point of Linux too
Step 1: Make sure you have
the dependenciesIt's super easy to "
sudo apt-get Package name", as they are listed between parenthesis on the webpage. Get them all, obviously. You can also use
the command here, presumably.
Step 2: Get the code
Either download it from the github webpage or git clone it. There are link in the first post of Meridian's exe to the github page.
Step 3: Compile
As listed in the page linked above, there are a few options. I have had success with
CMake option, although the webpage is now a bit confusing with information overload. So here's my checklist:
0. make installation directory (called "srcdir" in these notes)
1.
git clone git@github.com:MeridianOXC/OpenXcom.git srcdir (or just move the files you downloaded from github into your srcdir)
2. {copy
patched XCOM assets into
srcdir/bin/data}
3.
mkdir srcdir/build 4.
cd srcdir/build 5.
cmake .. 6.
ccmake .. (this opens a little "gui-lite" in the terminal. Things to do in the gui are in {}
7. {set CMAKE_BUILD_TYPE to
Release (or Debug if you want useful stack traces, but that slows the game a lot)}
8. {set CMAKE_INSTALL_PREFIX to
/path/to/where/you/want/the/game/to/be/ 9. {set DATADIR to define folder in which OpenXCom will look for the data subfolder (ex.: you can do
/path/to/where/you/want/the/game/to/be/data/}
10. {configure, then generate and exit}
11. make -j3
12. make install
This will give you a "openxcom" executable in
/path/to/where/you/want/the/game/to/be/bin/.
Next to the
bin folder you'll also get a user folder, in which to put the Piratez files from the user directory that is in the archive that Dioxine distributes (it annoys me that you have to download the whole thing with a Windows executable and dig out the mod, but Dioxine is convinced Windows users are clueless about how to set things up and need everything pre-set.. so Linux users have to do the extra work).
I actually do things slightly differently, where I have separate user and data directories, so I run OpenXCom with a little script:
#!/bin/bash
usrPath='/path/to/where/you/want/the/user/folder/to/be/user'
cfgPath='/path/to/where/you/want/the/config/to/be/config'
dataPath='/path/to/where/you/want/the/data/to/be/data'
/path/to/where/you/want/the/game/to/be/bin/openxcom -user $usrPath -cfg $cfgPath -data $dataPath 1>/path/to/where/you/want/the/Log/to/be/XPiratezLog.txt 2>&1This allows me to define a specific user directory, config directory and data directory, and to get a log of the executable in case it crashes so I can maybe have a bit of info on what went wrong. The user and data directories are especially useful as you can make 1000% sure that the game is looking where you want it to instead of wherever it might think the things are.
