OpenMW does not run out of the box with saucy

[psi29a]

I have a newly installed Saucy (13.10) Ubuntu system and tried installing OpenMW from our repo. The launcher does it dance, imports ini and then fails to load because it complains it can't find plugin.cfg.

On system two (also newly installed) with Debian, the whole process works without a problem. No plugin.cfg to be found.

I copy my config files over from Debian or Ubuntu, and OpenMW still complains with the same error.

bbrick@Redqueen:~/.config/openmw$ openmw
Loading config file: /home/bbrick/.config/openmw/openmw.cfg... done.
Loading config file: ./openmw.cfg... done.
Loading config file: /etc/openmw/openmw.cfg... done.
Using default (English) font encoding.

ERROR: RenderSystem with name OpenGL Rendering Subsystem not found, make sure the plugins are loaded

strace gives this:

write(5, "10:46:31: *-*-* Version 1.8.1 (B"..., 39) = 39
getcwd("/home/bbrick/.config/openmw", 128) = 29
stat("/home/bbrick/.config/openmw/NOTFOUND/RenderSystem_GL.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/home/bbrick/.config/openmw/NOTFOUND/RenderSystem_GLES2.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/home/bbrick/.config/openmw/NOTFOUND/RenderSystem_GL3Plus.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/home/bbrick/.config/openmw/NOTFOUND/RenderSystem_Direct3D9.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/home/bbrick/.config/openmw/NOTFOUND/Plugin_CgProgramManager.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/home/bbrick/.config/openmw/NOTFOUND/Plugin_ParticleFX.so", 0x7fffd4e98ae0) = -1 ENOENT (No such file or directory)
stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2944, ...}) = 0
write(5, "10:46:31: Particle Emitter Type "..., 49) = 49

It looks like, at least on Saucy, isn't building properly...

On Saucy, the libs sit here:

/usr/lib/libMyGUI.OgrePlatform.so
/usr/lib/libMyGUI.OgrePlatform.so.0debian0
/usr/lib/libMyGUI.OgrePlatform.so.0debian0.0.0
/usr/lib/x86_64-linux-gnu/libOgreProperty.so
/usr/lib/x86_64-linux-gnu/libOgrePaging.so.1.8.1
/usr/lib/x86_64-linux-gnu/libOgreTerrain.so
/usr/lib/x86_64-linux-gnu/libOgreTerrain.so.1.8.1
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE-Paging.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE-Terrain.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE-RTShaderSystem.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE-PCZ.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/OGRE-Property.pc
/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so
/usr/lib/x86_64-linux-gnu/libOgreRTShaderSystem.so.1.8.1
/usr/lib/x86_64-linux-gnu/libOgreMain.so
/usr/lib/x86_64-linux-gnu/libOgrePaging.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_BSPSceneManager.so.1.8.1
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_ParticleFX.so.1.8.1
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/RenderSystem_GL.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_PCZSceneManager.so.1.8.1
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_ParticleFX.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_OctreeZone.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_PCZSceneManager.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_BSPSceneManager.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_OctreeSceneManager.so
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_OctreeSceneManager.so.1.8.1
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/RenderSystem_GL.so.1.8.1
/usr/lib/x86_64-linux-gnu/OGRE-1.8.0/Plugin_OctreeZone.so.1.8.1
/usr/lib/x86_64-linux-gnu/libOgreMain.so.1.8.1
/usr/lib/x86_64-linux-gnu/libOgreProperty.so.1.8.1

Notice that the libs are installed in OGRE-1.8.0 while the version is 1.8.1... maybe that is the problem?

This ogre is the default ogre used by Ubuntu, not our own.

[psi29a]

Found this in build folder:

Code: Select all

CMakeCache.txt:OGRE_PKGC_LIBDIR:INTERNAL=/usr/lib/x86_64-linux-gnu
CMakeCache.txt:OGRE_PREFIX_WATCH_INT_CHECK:INTERNAL=/opt/ogre;/opt/OGRE;/usr/lib/ogre;/usr/lib/OGRE;/usr/local/lib/ogre;/usr/local/lib/OGRE;/home/bcurtis/ogre;/home/bcurtis/OGRE;NOTFOUND;NOTFOUND

Specifically the "NOTFOUND" bits are important.

Could be a bug in cmake, in it trying to find ogre plugins?

[psi29a]

a "sudo ln -sf OGRE-1.8.0 OGRE-1.8.1" and a rebuild later... it works.

This means:
1) Our saucy builds are broken
2) Ubuntu's Ogre (1.8.1) saucy build is broken (should be 1.8.1 not 1.8.0 dir)
3) Our cmake isn't failing if it can't find a renderer

[Zini]

Irritating. What is the plan here? Fix 1 and 3 on our side and complain to the Ubuntu guys about 2?

[psi29a]

I made a bug here:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1244592

if more people can login here and complain, that would be great to help raise the 'heat' level of the bug. So (2) is done for now.

For (3), I will have a go at making cmake reliably fail when our required plugins aren't found. I'll also look into a work around, if 1.8.1 isn't found, then try 1.8.* until we find something matching 1.8.1 in the filename. I'm not sure if cmake is that expressive.

If either 2 or 3 are fixed, then we can work on 1.

[maqifrnswa]

I made a bug here:
https://bugs.launchpad.net/ubuntu/+sour ... ug/1244592

if more people can login here and complain, that would be great to help raise the 'heat' level of the bug. So (2) is done for now.

If only there was someone with magic ubuntu dust that can escillate things...

This may be serious enough for an SRU (stable release update)

saucy testing build going on here:
https://launchpad.net/~showard314/+arch ... ld/5162870
https://launchpad.net/~showard314/+arch ... ld/5162869

once you confirm it works, I'll make it happen

[psi29a]

Awesome sauce Scott!

How do I get those wondrous powers?

Update: Your fix doesn't solve the problem, the directory is still /usr/lib/xxx/OGRE-1.8.0

[maqifrnswa]

Awesome sauce Scott!

How do I get those wondrous powers?

Update: Your fix doesn't solve the problem, the directory is still /usr/lib/xxx/OGRE-1.8.0

looked into it more: ubuntu kind of half-assed it... the kept the package names and directories the same, but added a new version. pkgconfig knows where to find things, but since cmake uses it's own modules for finding libraries, it's expecting to find it in OGRE-1.8.1. I'm building again with a simple symlink like you did, try it again when it's done building please. That will be a bandaid.

BTW, ogre-1.9 is in the archives for debian and ubuntu.

[psi29a]

I see in your saucy and trusty builds in debian/rules:

Code: Select all

# Use this variable to define the particular version of OGRE that we're building
OGRE_VERSION=1.8.0

Am I mistaken or should this be 1.8.1 and would that solve the issue?

I'll be able to test more tomorrow. Thanks for looking into this.

[maqifrnswa]

I see in your saucy and trusty builds in debian/rules:

Code: Select all

# Use this variable to define the particular version of OGRE that we're building
OGRE_VERSION=1.8.0

Am I mistaken or should this be 1.8.1 and would that solve the issue?

I'll be able to test more tomorrow. Thanks for looking into this.

that's what i tried the first time, but didn't work for you.
it also renames the packages, causing us to need to rebuild every depending package in ubuntu. It's cleaner and safer to keep it as it is released and just add a symlink.