[SOLVED] Using openxcom windows nightlies in linux with wine

[niculinux]

Very lastly (I promise!!) Game works also if the folder is put outside the wine prefix, eg /home/openxcom or even /desktop/opnexcom; moreover mods will work if the related folder is put in a subfolder /user of the game installation directory, that is to say:

Code: [Select]

/home/openxcom/user/mods/

[7Saturn]

That's a strange place to save files. Are you sure about that? Or did you just add a user »openxcom« to your system? Otherwise I doubt, that one has writing permissions there...

[winterheart]

Just don't use wine for openxcom. Compile own version from git, there no problem to do it.

[niculinux]

That's a strange place to save files. Are you sure about that? Or did you just add a user »openxcom« to your system? Otherwise I doubt, that one has writing permissions there...

No just used "raw" paths, and only for mods. Over and out!

[7Saturn]

Just don't use wine for openxcom. Compile own version from git, there no problem to do it.

I have to agree on that. With a little scripting, one can even get automatisation to that extend, that downloading latest nightly, patching files, copying translations and installing will take no more than 5 minutes, including archiving the compiled version with date.

[Leprechaun]

Why use WINE over GIT? Well, I have an answer, although it won't matter to many here ...

Last night was my first time to try GIT, and I still don't think I actually used it. I entered https://github.com/ ... whatever and found a ZIP link that I used to download the source code. Then I used cmake and ccmake several times, trying to work out what the hints on configuration settings meant. When I finally tried to run it, I got the same error niculinux got above.

Working from the instructions at https://www.ufopaedia.org/index.php?title=Compiling_with_CMake_%28OpenXcom%29
I did get it to work, after I fixed it ... I converted the bourne shell script to bash, added a PATH variable, deleted the double quote marks around the executable and data paths, and corrected the final directory from "data" to "UFO". Then it ran.

And here's why I am entering this reply. There are just too many threads for a newbie to figure out just how to make things work. For example, looking at threads on how to install nightlies, I find three paths given:

https://github.com/SupSuper/OpenXcom/commits/master     <AND>
https:https://openxcom.org/git-builds    <AND>
https://github.com/SupSuper/OpenXcom.git

OK, perhaps they are all correct. Or not. But how is a newbie supposed to know? Once you know how things work, getting hints is probably fine. But I don't know that I got the right nightly to run FMP, which is where I want to go. Have I wandered into a dead end and will have to back out to get what I want? And since I don't understand what GIT is used for, nor am I sure that I even used it, I don't know how to delete the old stuff when I am sure I have the location of the new stuff. Same problem with cmake and ccmake - never used them before last night. When I make a change, what will I have to do with them to make it work?

I'm committing myself to writing a single, comprehensive instruction set to go from nothing to Xcom with the FMP pack running on most any version of Linux. But I need some help from more knowledgeable people helping me determine which threads are going in the right direction, and which are dead ends or false leads.