Archlinux system how to install the game

[behind1231]

Studied two days if the game under the archlinux system installation, the results are not ~! , please show ~ I love this game, hope to be able to play on

[mic-e]

I'm developing on Arch Linux; it shouldn't be a problem... you just need to install all the required dependencies. Once you succeed, please report the list of all packages you installed so it can be added to the building.md file.

[franciscod]

also developing on arch, what problems did you have? On 1 Nov 2014 15:12, "behind1231" notifications@github.com wrote:

Studied two days if the game under the archlinux system installation, the results are not ~! , please show ~ I love this game, hope to be able to play on

— Reply to this email directly or view it on GitHub https://github.com/SFTtech/openage/issues/77.

[janisozaur]

I haven't noticed any. If I recall correctly, all the required libs are in main archives, no need to use AUR.

[behind1231]

Archlinux system how to install the game??????????

[TheJJ]

In case you haven't noticed, the game is far from finished right now. Volunteers are having fun creating the engine right now, there are no prebuilt packages available, and even if there were, the end-user functionality is pretty low right now.

You can follow the steps in building.md. If you encounter problems, you have to be more specific what exactly went wrong, otherwise it's really hard to guess and try to look into your head.

[behind1231]

Could NOT find SDL2 (missing: SDL2IMAGE_LIBRARIES)

[behind1231]

FATAL Exception: file nonexistant: .//converted/termcolors.docx

[mic-e]

Could you please post a list of all packages you did install?

[franciscod]

Install sdl2 and sdl2 image: pacman -Ss sdl image

[qlonik]

Hello. I tried to build openage on archlinux and it works great. I just needed to do minor tweaks regarding build, but that was about it.

Regarding packages: I had some of them already installed as dependecies for some other stuff, and i had to install the rest myself. This should be enough to get packages for arch:

pacman -S --needed gcc python python-pillow python-numpy glew ftgl ttf-dejavu freetype2 fontconfig cmake sdl2 sdl2_image opusfile opus-tools

or

pacman -S --needed clang python python-pillow python-numpy glew ftgl ttf-dejavu freetype2 fontconfig cmake sdl2 sdl2_image opusfile opus-tools

This will get all the dependecies from dependency list.

Regarding build itself: When configuring, I specified compiler clang++ or g++ and it didn't work for me. It was producing this error: for clang++

configure: error: unknown compiler suite: clang++. manually specify --c-compiler and --cpp-compiler, or use one of [llvm, gnu]

and for g++

configure: error: unknown compiler suite: g++. manually specify --c-compiler and --cpp-compiler, or use one of [gnu, llvm]

So instead I specified gnu which worked. I assume that if clang is installed, then there should be llvm.

And then when I converted media files, if I had path starting with ~, I was getting this error:

you need to specify AGE2DIR (e.g. /home/user/.wine/drive_c/age).
Makefile:37: recipe for target 'media' failed
make: *** [media] Error 1

So instead, I specified the absolute path to AOE2 folder.

Other than that, it works great! Thank you for this project!

[franciscod]

Cool!

Some of that is distro-independent (like the ~ on the media convert path)

Could you add the arch-specific steps to building.md and make a pull request? :) It will be very useful to whoever makes the initial PKGBUILD for openage :)

[qlonik]

Sure :)

[mic-e]

The "~ gives you an error" issue is because the shell won't expand ~ if it's in the middle of an argument... you can also use $HOME.

Back when I wrote/refactored ./configure I decided against allowing the gcc/g++ aliases for -c, to keep the script as clean and simple as possible... I think that was a bad idea.

[TheJJ]

This should be fixed by #115.

[dudelson]

Also runnning arch, I got the same "FATAL Exception: file nonexistant: .//converted/termcolors.docx" when trying to run the game with ./openage, but doing make run instead fixed the problem. I have no idea why this happens but hopefully the work-around helps.

[qlonik]

Someone had the same problem here #83
Basically using make run they provide argument --data=assets and when using ./openage it sets that parameter to be ./, so openage cannot find assets

[mic-e]

@thejj: yup. closing @dudelson: you need to build the assets, and run as ./openage --data=assets. the most recent version of openage doesn't that require anymore (fixed by #110)