Package Details: warzone2100-git r15440.ca2727322-1

Git Clone URL: (read-only, click to copy)
Package Base: warzone2100-git
Description: 3D realtime strategy game on a future Earth (Git version)
Upstream URL:
Keywords: game
Licenses: GPL
Conflicts: warzone2100
Provides: warzone, warzone-svn, warzone2100, warzone2100-beta
Submitter: disastro
Maintainer: disastro
Last Packager: disastro
Votes: 9
Popularity: 0.59
First Submitted: 2010-11-28 08:49
Last Updated: 2020-07-07 13:00

Latest Comments

1 2 3 4 5 Next › Last »

gameslayer commented on 2021-03-02 23:53

Can you add aarch64 to the pkgbuild build file please

arch=('i686' 'x86_64' 'armv7h' 'aarch64')

disastro commented on 2020-07-07 13:02

CMake and Ninja now used for building as per upstream, please report any issues

Anonymous comment on 2020-03-11 05:14

configure: error: *** This build toolchain is deprecated (and will be removed) - please use the CMake build toolchain. (If you really want to ignore this for now, specify: --enable-promise-to-use-cmake) ***

It seems warzone2100 isn't going to use autotools anymore, and has switched to CMake. The package should be updated for that.

Forgon commented on 2018-03-21 11:36

After fetching the source code repository, it is necessary to execute git submodule update --init --recursive within it.

The PhysFS patches are out-of-date and should be removed. Also, support for the Qt backend has been deprecated in favor of SDL.

disastro commented on 2018-01-10 10:59

@Forgon Thank you for the suggestions. Not using https for git is a remnant from the past, I'll change that.

As for the debugging, I've thought about this long and hard already and also discussed this in IRC and this is the way I am happy with for now. makepkg will strip debug symbols by default, and the package, even if -git, isn't meant to be a debug package. Anyone can remove --disable-debug themselves and add the necessary makepkg options when they need debugging.

Forgon commented on 2018-01-10 08:32

Thank you for your improvements, disastro.

I further suggest:

  • replace 'git' with 'git+https' for the source

  • remove the '--disable-debug' option for the configure script (this package is for testing, no one plays the latest builds online)

disastro commented on 2018-01-09 13:57

I've replaced my horrible physfs patch with the patchset at

Config directory moves because of that again from ~/.local/share/.warzone2100-master to ~/.warzone2100-master

Sorry for the inconvenience. I've also updated the dependencies

EndlessEden commented on 2017-11-06 08:50

Disabled Debug works...
but there is a "Relaxed" option. that still builds with debug options, but ignores warnings.

Please consider this, and i use the debug ingame menu, for testing maps and changes, im pushing upstream.


Also, i was using native. I specified "Piledriver" in my comment instead of "bdver2", by mistake. i havent used the platform specific flag, in a long time. so i had forgotten.

I avoid Generic because i see a measurable 31% decrease in performance. As well as a 11% decrease from -O2, vs -03 or -fast. - Which may seem fine to you, but im working on a mod and every little bit helps...

disastro commented on 2017-11-05 07:40

Hello EndlessEden,
Me and a couple of people ran multiple builds of the package and couldn't replicate your build failure unfortunately.

The only time we could break the build on a different error was by using clang instead of clang++, so make sure your CXX is set to clang++. clang++ (03) worked with both debugging enabled or disabled while g++ still fails on that unitialized error if using O3 with debugging.

EDIT2: Actually seems it's just gcc that can't use piledriver because such mtune setting doesn't seem to exist? clang just ignores it?
(I could only test march=native or mtune=generic and couldn't test piledriver personally but the people on IRC did and it built fine for them even on clang++, with only -fno-plt as an extra CFLAG to yours.)

What I suggest based on the build error and our testbuilds is try with either g++ or mtune=generic although it's hard to say if that will fix anything since I am not sure of the other changes to your system. I want to remind you that Arch uses g++ and O2 by default so it's all extra if a package builds with special flags. That being said I am unsure why the CFLAGS, while unsupported, work on the system or two tried on IRC and not on yours.

EDIT: PS. Based on some of the discussions on IRC I've decided to --disable-debug for everyone and trust that the makepkg debugging build works if one enables it.

phillid commented on 2017-11-05 07:26

@EndlessEden, works for me with the same CFLAGS and CXXFLAGS, except I have -fno-plt hanging on the end of both. Just to cover my bases; you are running up-to-date Arch, right?