Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - knapsu

Pages: [1] 2
Hi. The PPA repository openxcom-beta is discontinued. Please use universal AppImage packages instead. These packages can be downloaded from OpenXcom website.

@hairybert DEB packages for Ubuntu Bionic created.

Hey @hairybert. I'll update the PPA on weekend. Take care.

If you need more info about AppImage package please read this post,5432.0.html

@Stoddard, the Debian package specification files are in OpenXcom repository. Take a look here

Honestly with AppImage that just works everywhere I don't see too much need for nightly DEB and RPM packages anymore.

@niculinux, if you need AppImage packages for OpenXcom Extended than I suggest you clone the repository. This repo is fully automated to make daily OpenXcom builds for 32-bit and 64-bit Linux using Travis CI and upload them to website. After you clone it modify line 49 for 'scripts/' to point to OpenXcom Extended repository and enable Travis for your cloned repo. Also replace '--scp' with '--transfer' on line 24 in '.travis.yml' file so that final AppImage packages will be uploaded and shared to as you won't be able to upload them to OpenXcom website.

Builds & Ports / Re: AppImage - Universal package for Linux
« on: May 15, 2017, 04:51:30 pm »
@Hythlodaeus, to use mods you just extract them to data directory. List of valid paths can be found here

Personally I put mods inside my user home directory $HOME/.local/share/openxcom/mods. I find it easier to use (copy/delete mods) than switching to root account and copying extracted files to system directory /usr/share/openxcom/* (location may be different depending on distribution packaging).

The rest is just enabling them in Options > Mods when running OpenXcom.

Builds & Ports / Re: AppImage - Universal package for Linux
« on: May 14, 2017, 02:38:42 pm »
I've updated topic description with links to development/nightly AppImage packages. You can play TFTD with those builds.

Builds & Ports / Re: AppImage - Universal package for Linux
« on: May 14, 2017, 01:44:35 pm »
Hey @blesst, I tested it on openSuSE Leap 42.2 64-bit already. Rechecked it and it works for me.
I guess the issue might be happening if you have locally installed openxcom package, as when running the AppImage the local paths/files takes priority before paths/files embedded in appimage file. when OpenXcom app searches for data directory and it finds a path in local filesystem it tries to use it.

Can you uninstall openxcom pacakge using yast/zypper and rerun the AppImage?

Builds & Ports / Re: AppImage - Universal package for Linux
« on: May 13, 2017, 11:16:17 am »
Tahnks @blesst for info. Which version of openSUSE are you using?

Builds & Ports / AppImage - Universal package for Linux
« on: April 21, 2017, 04:12:39 pm »
Hi everyone. Because I got tired of all those issues when it comes to build and distribute packages for different Linux distributions, incompatibilities and quirks even between releases for one single distribution, issues with missing or buggy yaml-cpp package, I've decided to give AppImage a try.
To explain it in few words, we create an application package that can be downloaded from a web page (like for Windows and macOS) and just run by executing this file. Very straightforward, nothing downloaded in the background, nicely integrates with our desktop, and integrates nicely with our desktop. The fun fact is... it actually works!

You can read more about AppImage format here

I've created test packages for 64-bit and 32-bit platforms based on DEB packages (it was easier for me). When I find time I will check integrating AppImage directly with CMake as a build step (this would make Linux nightlies awesomely easy to test).

I wish to check if it works on as many Linux distributions as possible before proposing this to SupSuper and Warboy.
I've already check it using VirtualBox on the following distributions:
- Ubuntu Xenial (64-bit)
- Ubuntu Yakkety (64-bit)
- Ubuntu Trusty (64-bit and 32-bit)
- Fedora 25 (64-bit)
- openSUSE Leap 42.2 (64-bit)

Because I have limited resources I would appreciate if anyone could test it on Arch Linux, CentOS, Debian, and previous Fedora or openSUSE.
Generally all modern distributions that have glibc 2.14 (released after 2012) should work.

Links to OpenXcom 1.0 packages:
[links removed as they are no longer valid]

Links to OpenXcom Nightly packages:
[links removed as they are no longer valid]

Troubleshooting / Re: 1.0.518a651-dirty
« on: February 27, 2017, 11:40:42 am »
Hey! Sorry for digging up such an old thread... The problem with version number is now fixed. I had a typo in my automated build scripts which resulted in OPENXCOM_VERSION_STRING always sticking with commit hash 518a651 despite sources being in more recent version. I've checked the latest builds and it is good now.

A small reminder...

Nightly builds are done every weekend for Ubuntu 14.04 LTS (Trusty Tahr) and Ubuntu 16.04 LTS (Xenial Xerus).

These packages works with all other Linux distributions that are based on Ubuntu LTS (Linux Mint, Neon, etc).
Packages for Xenial also works with Debian Unstable (at least the last time I've checked).

The Ubuntu Nightly Builds PPA is here:

Hey. I've added OpenXcom 1.0 packages for Ubuntu 16.10 (Yakkety Yak) for anyone who does not want to use the latest bleeding edge version.
As usual libyaml package makes the most trouble when creating good DEB packages. I needed to patch it to work with GCC 6.

The Ubuntu PPA is here:

@SupSuper, sure. Adding hash is a good idea.

The commit hash will be taken directly from git repo and added to version string.


Hey. I've received a request to create OpenXcom packages for Debian Testing (Stretch). It's done.

To download them just go to the page

Pages: [1] 2