openmw.org

K1ll wrote:I've also made both a libogre-static and an openmw source package. They are nearly done but i need a short description (max 60 characters) and a long description for these binary packages which are build by the openmw source package:

openmw (contains the openmw binary)
openmw-data (contains the desktop file and the resources)
openmw-launcher (contains the launcher binary)
esmtool (contains the esmtool binary)

The libogre package, does that include the Plugin_CgProgramManager? We need this for all future versions of OpenMW. That means we need the nvidia package first, if I'm not mistaken. See here:
https://launchpad.net/~ogre-team/+archi ... /+packages

We can use their debian source packages as a base or just copy their ppa and modify them to be static builds in the source.

BrotherBrick wrote:

K1ll wrote:I've also made both a libogre-static and an openmw source package. They are nearly done but i need a short description (max 60 characters) and a long description for these binary packages which are build by the openmw source package:

openmw (contains the openmw binary)
openmw-data (contains the desktop file and the resources)
openmw-launcher (contains the launcher binary)
esmtool (contains the esmtool binary)

The libogre package, does that include the Plugin_CgProgramManager? We need this for all future versions of OpenMW. That means we need the nvidia package first, if I'm not mistaken. See here:
https://launchpad.net/~ogre-team/+archi ... /+packages

We can use their debian source packages as a base or just copy their ppa and modify them to be static builds in the source.

We can just include their ppa to buid the static ogre package.

There is an option to add ppas on launchpad:
https://help.launchpad.net/Packaging/PP ... other_PPAs

I thought about doing the same with the libbullet and static ogre ppa(s) for a seperate openmw ppa so none gets the idea to download those packages.

Yeah, I've been reading up about that last week.

For libbullet (our own modified version that fixes a few bugs) we have 3 series: lucid, oneiric and precise. They should be building as I type this now.
https://launchpad.net/~openmw/+archive/ ... /+packages

Should things work out, I'll try my hand at ogre. I will base them off the Ogre Team's packages using their nvidia and freeimage packages to create a static package for us to use.

For those reading this: these packages are for static libraries and not for the *.so (shared objects) files, so they will not be usable as such. We still recommend using debget and ogre team's ppa for libbullet and ogre.

I've updated the latest bullet using the 'proper' way to handle our bin/dev files.

What is the next step? I know you have libogre working, do we still need the nvidia package? Is there anything else?

With the help of K1ll we now have a few PPAs that people can use.

I'm proud to say that our 'official' Ubuntu packages can be found here:
https://launchpad.net/~openmw/+archive/openmw
^-- includes 32 and 64bit packages from Lucid to Precise that is statically compiled and does not need users to worry about libbullet nor libogre.

For those wishing to use static (*.a) libraries:
https://launchpad.net/~openmw/+archive/deps

For those wishing to use dynamic (*.so) libraries instead:
https://launchpad.net/~openmw/+archive/build

It'd be nice if someone who understands the packaging situation updated these pages to reflect that we have our own PPAs now.

Mind if I update it with Fedora instructions?

artorius wrote:Mind if I update it with Fedora instructions?

Why would anyone mind?
Also, if this is your first time using the wiki don't forget to add yourself to the wiki usergroup

Fedora build instructions now up.

werdanith wrote: Why would anyone mind?

I didn't know if I would step on anyone's toes. Figured I would ask just in case.

Should we have a separate packaging page on the wiki? To show SPEC files for .rpm packages and the script files necessary to buld the .deb packages?

For those wishing to use the PPA with *.so files, there is an issue with OGRE in that it wants to store its files in /usr/lib/(x86_64|i386)-linux-gnu/OGRE-1.7.4 instead of /usr/lib/OGRE .

I'll need to investigate it further and either provide a symlink for it or OpenMW needs to update itself for multilib/arch support. Not sure what is best at the moment. This is something new as of 1.7.4 in Ubuntu (their own build specifications).