Ember media installation

I’ve just committed some updates to Ember which should help developers with getting the correct media. These consists of a new rsync service installed at amber as well as some new make targets for easy media installation.

After compiling and installing Ember developers need to also install the needed media. This has been done by downloading a tarball from the net (hosted by sourceforge currently) and unpacking it to the correct location. For stable releases it’s pretty straight forward, although it’s easy to unpack it to the incorrect location. But for the development version it’s not that simple. The problem is that the media is constantly changing, and mainly at my box, so I need a better way to push it out to other developers. One solution is to mandate that all developers also keep a copy of the media svn repository checked out, but there are a couple of problems there that needs to be solved first, chief amongst them Ogre’s inability to correctly handle duplicate resources (to be fixed in version 1.6)

I have therefore set up a rsync server at amber.worldforge.org::media-dev which can be used for keeping the media up to date. I’ve coupled this with some bash-scripts on my end which will automate the process of updating the media. To make it even easier for developers I’ve also added some two new make targets which will take care of the whole ordeal (basically run rsync with the correct commands). Depending on whether it’s a stable release or a development version that’s being used there are two new make targets:
make devmedia
and
make releasemediarsync
The former will use the development media while the latter will use the stable media for the current release. I also fiddled with a third make target which would automatically download the stable media from sourceforge, unpack it and copy it to the correct location, but my Makefile-fu isn’t strong enough. If anyone wants to take a stab at it they are more than welcome. The file in question is forge/clients/ember/Makefile.am.

Leave a Reply

You must be logged in to post a comment.


UA-925252-3