Hi Wookey - It is kind of a strange situation for me. I earn a good living as a software packager for Windows applications. I can turn MSI files inside-out. But RPMs?? I have no clue where to even start!
Of course, if I were to take on RPM packaging, I still have to get Therion to compile. Fedora 17 is over a year old. They are up to 19, and I expect to see 20 before the end of the year. Still, it's not THAT old. On that subject - Fedora package names are quite different from Debian. I ran some queries on my system to see what is installed. Here is what it shows. I think this covers everything you mentioned. ================ [bgee at main2 ~]$ rpm -qa | grep -i wx wxGTK-devel-2.8.12-4.fc17.x86_64 wxPython-2.8.12.0-2.fc17.x86_64 wxBase-2.8.12-4.fc17.x86_64 wxGTK-2.8.12-4.fc17.x86_64 wxGTK-media-2.8.12-4.fc17.x86_64 wxGTK-gl-2.8.12-4.fc17.x86_64 [bgee at main2 ~]$ rpm -qa | grep -i mesa mesa-libGL-devel-8.0.4-1.fc17.x86_64 mesa-libOSMesa-devel-8.0.4-1.fc17.x86_64 mesa-libglapi-8.0.4-1.fc17.x86_64 mesa-libxatracker-8.0.4-1.fc17.x86_64 mesa-libOSMesa-8.0.4-1.fc17.x86_64 mesa-dri-filesystem-8.0.4-1.fc17.x86_64 mesa-libGLU-8.0.4-1.fc17.x86_64 mesa-dri-drivers-8.0.4-1.fc17.x86_64 mesa-libgbm-8.0.4-1.fc17.x86_64 mesa-libEGL-8.0.4-1.fc17.x86_64 mesa-libGLU-devel-8.0.4-1.fc17.x86_64 mesa-libGLES-8.0.4-1.fc17.x86_64 mesa-libGL-8.0.4-1.fc17.x86_64 [bgee at main2 ~]$ rpm -qa | grep -i freetype freetype-2.4.8-4.fc17.x86_64 freetype-2.4.8-4.fc17.i686 freetype-devel-2.4.8-4.fc17.x86_64 [bgee at main2 ~]$ rpm -qa | grep -i vtk vtk-tcl-5.8.0-6.fc17.x86_64 vtk-5.8.0-6.fc17.x86_64 vtk-python-5.8.0-6.fc17.x86_64 vtk-devel-5.8.0-6.fc17.x86_64 vtk-qt-5.8.0-6.fc17.x86_64 vtk-java-5.8.0-6.fc17.x86_64 [bgee at main2 ~]$ ===================== I assume xTherion needs vtk .... If vtk were the problem, then I would expect the Therion compiles to fail too. It runs through xTherion without error. It only fails when it gets to Loch. Regards - Bill Gee On Tuesday, October 08, 2013 10:16:34 Wookey wrote: > +++ cawa sorix [2013-10-08 08:17 +0200]: > > Hi, > > > > To build therion on debian, I install first packages below: > > wx2.8-headers > > libwxgtk2.8-dev > > wx-common > > mesa-common-dev > > libglu1-mesa-dev > > libfreetype6-dev > > libvtk5-dev > > And the packaging adds $(VTKLIBS) to PLIBS in the makefile: > > --- therion-5.3.11.orig/loch/Makefile 2013-09-03 03:59:17.912863415 > +0100 > +++ therion-5.3.11/loch/Makefile 2013-09-06 03:07:56.662776189 > +0100 > @@ -33,10 +33,10 @@ > CC = gcc > POBJECTS = lxR2P.o > VTKLIBS = -lvtkHybrid -lvtkImaging -lvtkIO -lvtkGraphics > -lvtkFiltering -lvtkCommon -lfreetype > -CXXPFLAGS = -DLXLINUX $(shell wx-config --cxxflags) -Wno-deprecated $(shell > freetype-config --cflags) -I$(VTKPATH) +CXXPFLAGS = -DLXLINUX $(shell > wx-config --cxxflags) $(shell freetype-config --cflags) -I$(VTKPATH) > CCPFLAGS = -DLXLINUX $(shell wx-config --cflags) LXLIBDIR = linux -PLIBS > = $(shell wx-config --libs --gl-libs) -L$(VTKLIBPATH) $(VTKLIBS) -lGLU > -lpthread -lz +PLIBS = $(shell wx-config --libs --gl-libs) $(VTKLIBS) > -lpthread -lz $(shell pkg-config --libs libpng glu) -ljpeg -lX11 LXPLATFORM > = LINUX > > # PLATFORM WIN32 > > > I suspect the problem is in the command line option > > "-L/usr/lib/vtk-5.4". �The > > system by default does not have this directory. �I added a symbolic > > link > > to > > the location of vtk (/usr/include/vtk-5.4) but it made no difference. > > Debian is up to vtk-5.8. I'd expect Fedora to have a newer version by > now too? But the makefile in 5.3.11 doesn't actually specify an > explicit version any more. It uses: > VTKVERSION = $(shell tclsh ./getvtkver.tcl version) > > I guess RPMworld needs a caving packager :-) > > Wookey
