Mika Boström kirjoitti: > In order to ease testing and distribution in future, we needed to > create debian packages for the viewer. >
Thanks! (again, we've talked on irc too) > funky problems later on, of which the python module should be the most > obvious one. I'd like to use the system python where available instead > of an embedded interpreter but maybe that's just me... > What do you mean exactly? At least when I built the py module on ubuntu, it built fine against the system python. But in the running application it has to run embedded inside the viewer process, otherwise it cannot access the memory nor call functions within the viewer that are the API for Python written plugins. It's still the same Python interpreter code though that your system has, just instanciated within Naali. It should be able to use any python modules that your system has etc. Naali is not (currently) a set of Python libraries, which you could use from a non-embedded interpreter. But that question is AFAIK not related to building or packaging, but to how the app itself is architected. > Running the viewer on hardware with Intel video seems to fail. In a > virtual machine, binary segfaults immediately after initialising GLX. On > my x86-64 host the error occurs later, when a shader program fails. Most > likely a hardware and/or driver issue. > On win32 it runs on Intel cards, so perhaps a driver thing? Running on weaker gfx cards could be supported better by having some way of configuring which shaders are run. > The simplest way to provide these packages should be a debian > repository, with the missing packages and (daily?) snapshot builds. > That would be great indeed. ~Toni > [begin packaging instructions] > > ********************************************* > *** RealXtend packaging for Ubuntu Karmic *** > ********************************************* > > Acquiring the required build-dependencies: > > - Poco 1.3.5: (not yet available in debian or ubuntu) > - install these packages: > dpatch > unixodbc-dev > libmysqlclient-dev > - go to http://mentors.debian.net/debian/pool/main/p/poco > - get these two files: > poco_1.3.5.orig.tar.gz > poco_1.3.5-1.diff.gz > - build the sources: > % gunzip poco_1.3.5-1.diff.gz > % tar zxf poco_1.3.5.orig.tar.gz > % cd poco-1.3.5-all && patch -p1 < ../poco_1.3.5-1.diff > % dpkg-buildpackage -rfakeroot -us -uc > - install the non-debug packages: > % cd .. > % ls libpoco*.deb | grep -v dbg_ | sudo xargs dpkg -i > - DO NOT DELETE PACKAGE FILES > > > - Caelum 0.5.0: (not packaged for debian at all) > - install these packages > scons > libogre-dev > - go to http://sourceforge.net/projects/caelum/files/ > - get the Caelum-0.5.0.zip source package > - unpack caelum sources: > % unzip Caelum-0.5.0.zip > - apply debianisation patch: > % cd Caelum-0.5.0 && patch -p1 < ../caelum-debianisation.diff > - build the sources: > % dpkg-buildpackage -rfakeroot -us -uc > - install the packages: > % cd .. > % sudo dpkg -i libogre-caelum*.deb > - DO NOT DELETE PACKAGE FILES > > > RealXtend viewer: > - make a fresh export (only if plan is to upload packages+sources) > - apply debianisation patch > - build: > % dpkg-buildpackage -rfakeroot -us -uc -tc > - install the resulting packages > > [end] > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/realxtend http://www.realxtend.org -~----------~----~----~----~------~----~------~--~---
