openmw.org

psi29a wrote: @kill: the generic/static builds use osg-3.4 proper or scrawl's fork?

The generic builds use normal osg-3.4 compiled on debian wheezy.

Hi Rippl I've been cross-compiling openmw from linux to windows for a few years now. With a recent mingw-w64 toolchain and pre-packaged dependencies it's no trouble at all. On debian it could be quite a hassle though since AFAIK there are only a few mingw-w64 packages so you would have to manually c...

OpenMW 0.41.0 Linux targz package release builds:

32 Bit
64 Bit

RC4 Linux targz packages:

32 Bit
64 Bit

RC3 Linux targz packages (skipped RC2):

32 Bit
64 Bit

Linux targz packages:
RC1 32 Bit
RC1 64 Bit

I have working flatpack packages for openmw and openmw-cs and am currently working on making snap packages too. Would it be possible to distribute an appimage for OpenMW at some point? I've used the one for Krita for a while now, and it's been very convenient to be able to just download and run the ...

Sure, we'll do a google hangout g/talk thing sometime. You know, in case I and/or k1ll get hit by a bus. Speaking of which, how k1ll makes his releases is also black-magic. From what I gather, he creates static builds of all libraries that he can so that it is generic enough. It also has to be buil...

Second: Also OSG does print errors to the console when it can't load a module because of a missing dependency so there is an indication that something went wrong and how to fix it. Anyway maybe we should add to the release notes that Qt4 and libpng12 are required to use the targz package binaries. ...

IIRC I'm intentionally leaving out libpng because there was a problem with the system Qt4 picking up the bundled libpng library even though it depends on the systems libpng version. Means neither the launcher nor openmw-cs were able to run even though Qt4 was available. Most distros (including Fedo...