Package Details: openxcom 1.0-8

Git Clone URL: (read-only, click to copy)
Package Base: openxcom
Description: An open-source reimplementation of the famous X-COM game
Upstream URL:
Licenses: GPL3
Submitter: None
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 45
Popularity: 0.000277
First Submitted: 2012-01-30 07:27
Last Updated: 2019-12-21 00:07

Latest Comments

1 2 3 4 Next › Last »

gonciarz commented on 2019-08-11 22:10

@WorMzy: I created a patch few weeks ago that unify paths for openxcom and openxcom-git.

I copy-paste my comment from openxcom-extended package: gonciarz commented on 2019-07-16 20:49 Hi WorMzy, I understand that the OpenXcom is dead now because guys do not release on github. But on the other hand I don't like disorder and manual steps. I just want to have all packages (openxcom/git, openxcom-extended/git) Still from my point of view the cleanest solution would be to apply a patch to openxcom that would change the 'data' path to 'UFO'. Actually I dig a bit and prepared one. Please accept it.

I'm not familiar how collaboration looks like on AUR git, but I usually create a pull request. I've tested the game and it loads properly. Please take a look here:

I believe that after merging that change to aur repo, we may change path in openxcom-data-steam. What do you think?


WorMzy commented on 2019-01-27 15:55

Sorry Ultima_12, I completely missed your message. FWIW, I can't reproduce the error you were getting, so hopefully it was just a transient issue with your build environment. EDIT: actually, checking the git update history, I updated the patchset after your message, but must've forgotten to post a message about the change. My bad.

@jenz: There seems to have been a change in the way that GL_GLEXT_VERSION is defined, and this trips over builds using -Werror (which is the default. I'm not sure how to fix this properly, and upstream has long since abandoned the v1.0 release (they recommend using nightly builds, which you can use openxcom-git to reproduce) so I doubt a patch will be made to fix this. Instead, I have disabled -Werror in the build, and checked that the built package still runs. Please give it a go and see if it resolves your issue.

Anonymous comment on 2019-01-27 11:39

Pinging. This package still fails

Ultima_12 commented on 2018-03-07 20:19

The package fails to build due to an issue with the source, specific output of:

src/Basescape/BaseInfoState.cpp: In member function ‘virtual void OpenXcom::BaseInfoState::init()’: src/Basescape/BaseInfoState.cpp:358:14: error: ‘floor’ was not declared in this scope ss5 << (int)floor(_base->getUsedStores() + 0.05) << ":" << _base->getAvailableStores(); ^~~~~ src/Basescape/BaseInfoState.cpp:358:14: note: suggested alternative: ‘float’ ss5 << (int)floor(_base->getUsedStores() + 0.05) << ":" << _base->getAvailableStores(); ^~~~~ float

WorMzy commented on 2016-05-09 13:54

I've pushed an update that fixes the errors, but I can't guarantee that my fixes won't cause problems in-game. If you could give it a go and let me know if you run into crashes or anything strange, that'd be great.

hollunder commented on 2016-05-09 12:22

Fails to build with this error:

src/Geoscape/Globe.cpp:1398:29: error: call of overloaded ‘abs(double)’ is ambiguous
seg = abs( sx/(2*M_PI)*96 );

WorMzy commented on 2014-09-05 21:18

You should already have that installed, as it's a member of base-devel:

slick commented on 2014-09-05 21:16


Today I tried to build the package and got the following error:
./configure: line 4319: syntax error near unexpected token `0.24'
./configure: line 4319: `PKG_PROG_PKG_CONFIG(0.24)'

I googled it [1], and it seems that `pkg-config' package is required for the build. So, you should probably add it to makedepends.


Boskote commented on 2014-06-21 00:52

For those who are unable to upgrade openxcom because of the error "yaml-cpp and yaml-cpp0.3 are in conflict" you can uninstall yaml-cpp0.3 using:
pacman -Rdd yaml-cpp0.3
And then the upgrade should run without a problem. The -Rdd allows for removing a package even though it is a dependency of another package (which is this case is the old version of openxcom).

As Dalrik stated below, it is also possible to manually uninstall and then reinstall openxcom. I didn't want to do this because I made a bunch of changes to the openxcom files that I didn't want risk messing up. So I found the -Rdd way, and thought I would share because it seems like a cleaner solution.

WorMzy commented on 2014-06-14 18:06

That was a superfast update! :D

A couple of points:

* You can drop the timidity++ dependency as it's no longer needed by default. (though I believe people can still use it if they want to)

* The manpage generation is a lot better nowadays too, so you may want to consider re-enabling it (just remove the --without-man and add xmlto, docbook-xml, and docbook-xsl to the makedepends).

Good luck with your alien hunting!