Messages

1

Released Mods / Re: [UFO MAPS] Luke's Extra UFOs (52 working maps!)

« on: April 14, 2014, 09:31:54 pm »

DarkDefender: I was aware of some of the case discrepancies in the ruleset, but unaware of their impact. Is lower case file names preferable on Mac and Linux, or are they just very case sensitive?

Lower case file names are preferable on Mac and Linux. You can still keep the files with mixed case if you want to. But then you will have to be very careful so that you don't have typos in the ruleset. If all files were in lower case it would be easy to spot case typos and no silliness like UfOIl.PcK can occur.

2

Released Mods / Re: [UFO MAPS] Luke's Extra UFOs (52 working maps!)

« on: April 14, 2014, 07:34:06 pm »

I would just like to point out that 3 files in this mod pack doesn't match up with what is written in the ruleset.
This currently breaks loading of the data files on linux and mac (probably everything else than windows).

The files in question are: ox_ufo2c.rmp ufol83.pck ufol83.tab
In the ruleset they are defined as: ox_ufo2c.RMP UFOL83.PCK UFOL83.TAB

I see there is a lot of mixed case going on in the file names. I would suggest to have all the files in lowercase instead to avoid file loading problems in the future.

3

Programming / Re: 0.9 Build fixes for OSX

« on: May 16, 2013, 01:50:40 pm »

I think I solved the problem. I replaced every new pair declaration in the push back function with make_pair because the pair type is already defined in the vector and voila, it now compiles for me with clang!
Can you try it out and see if it solves it for you also?

Not only does this cut down on some unnecessary code it also solves the compilation problem. However I don't know exactly why clang had a problem with the old code. I will rule it out as a bug in clang for the time being. Or perhaps this is deliberate to force the code to be cleaner I guess? However the error message suggest otherwise...  

4

Programming / Re: 0.9 Build fixes for OSX

« on: May 16, 2013, 10:43:09 am »

It might be that VS and gcc is more loose in their c++ standard implementation. But the problem we have is the following:
1. The code compiled fine with clang before the commit
2. There are other variables that are defined just like O_WESTWALL & co is. However those doesn't break clang it seems
3. If we just accept a quick fix for this without knowing why and what went wrong then there will probably be breakage further down the line.

I installed clang 3.2 my self to see if I could compile it. It doesn't work here either. But I get a better error message:

Code: [Select]

openxcom-TileEngine.o: In function `pair':
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.2/include/g++-v4/bits/stl_pair.h:105: undefined reference to `OpenXcom::MapData::O_WESTWALL'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.2/include/g++-v4/bits/stl_pair.h:105: undefined reference to `OpenXcom::MapData::O_NORTHWALL'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
If we take a look at what changed in that commit https://github.com/SupSuper/OpenXcom/commit/6024bedf3cca3855a5b00b315b5a24d8530964e9 we can see that it is now using "std::pair" to store the O_* stuff. And it wasn't using a pair datatype before. So that is probably what broke it and not the definition of the O_* ints.
So now the question is why clang doesn't like pairs in this situation

5

Programming / Re: 0.9 Build fixes for OSX

« on: May 15, 2013, 12:32:42 am »

Are you sure this is not a bug with clang/llvm? It complies fine with gcc and MSVS.

6

Builds & Ports / Re: Gentoo openxcom git ebuild

« on: May 13, 2013, 12:02:08 am »

Ah, ok. Supsuper, just write that the openxcom ebuild is in the gamerlay overlay on the downloads page.

7

Builds & Ports / Gentoo openxcom git ebuild

« on: May 12, 2013, 11:06:52 pm »

Here is an ebuild for openxcom.

Code: [Select]

# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
EAPI=3

inherit git autotools


DESCRIPTION="OpenXcom is an open-source clone of the popular
UFO: Enemy Unknown (X-Com: UFO Defense in USA)"
HOMEPAGE="https://openxcom.org/"
EGIT_REPO_URI="https://github.com/SupSuper/OpenXcom.git"

LICENSE="GPL"
SLOT="0"
KEYWORDS="x86 amd64"
IUSE=""

DEPEND="media-libs/libsdl
media-libs/sdl-mixer
media-sound/timidity++
media-libs/sdl-gfx
media-libs/sdl-image
dev-cpp/yaml-cpp"
RDEPEND="${DEPEND}"

src_prepare() {
eautoreconf
}
src_compile() {
emake || die "emake failed"
}

src_install() {
emake DESTDIR="${D}" install || die "emake install failed"
}

pkg_postinst() {
    einfo "You will need to install the Xcom data files in:"
    einfo "\$XDG_DATA_HOME/openxcomi/data or \$XDG_CONFIG_HOME/openxcom/data"
einfo "see https://www.ufopaedia.org/index.php?title=Installing_(OpenXcom)"
einfo "for more info."
}

Save it as openxcom-9999.ebuild and put it in a local overlay https://wiki.gentoo.org/wiki/Overlay
For example "/usr/local/portage/games-strategy/openxcom" and run "ebuild openxcom-9999.ebuild digest" then you can just emerge it like usual.