Where can I submit changes to the source. We really need svn and trac... This patch fixes bad resolution values in loch for computers with multiple displays. This patch shouldn't effect computers with single displays. http://ohc.tx2600.net/patch/multi-screen-support.patch patch -p0 loch/lxGUI.cxx < multi-screen-support.patch Steelwool
On 2006-10-10 17:21 -0400, Philip Schuchardt wrote:
Where can I submit changes to the source. We really need svn and trac...
I have put my (ther debian) version of therion in svn://wookware.org/therion This includes some fixes so that loch builds under g++ 4.1 without a load of warnings. However this is version has also had the makefiles hacked about with to get rid of a lot of the cross-platform stuff, and make it build in debian-world, and tom has been deleted, so it's not 'upstream source of therion'. I put it up so people could collaborate on packaging v0.4 I could check in plain upstream therion as well if people felt this was as sensible place to keep the definitive version, but that's really up to stacho (who may not want to use SVN at all) or may prefer to set it up on the therion server (it makes sense). The patch is at http://wookware.org/therion_0.4.0-1.diff.gz where you can fish out the loch/*.cxx patches and ignore the rest (I would like to discuss the makefile setup sometime. It is currently nice and simple to read but much of the make-work is actually done by perl-scripts and the cross-platform support is fairly primitive. I would like to bin the perl and make the makefiles use make constructs to decide what to do, and get smarter about library config (pckconfig, for example). This way lies autoconf, which I'm not sure is an improvement, but there is certainly room for improvement I think. If we could agree this that would be better than me making the debian version very different.) Is there any point keeping libtom in the source? Is it not entirely superceded by loch? Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://wookware.org/
I think CMake is a good option: http://www.cmake.org/HTML/Index.html Steelwool... On Tuesday 10 October 2006 10:04 pm, Wookey wrote:
On 2006-10-10 17:21 -0400, Philip Schuchardt wrote:
Where can I submit changes to the source. We really need svn and trac...
I have put my (ther debian) version of therion in svn://wookware.org/therion
This includes some fixes so that loch builds under g++ 4.1 without a load of warnings.
However this is version has also had the makefiles hacked about with to get rid of a lot of the cross-platform stuff, and make it build in debian-world, and tom has been deleted, so it's not 'upstream source of therion'.
I put it up so people could collaborate on packaging v0.4
I could check in plain upstream therion as well if people felt this was as sensible place to keep the definitive version, but that's really up to stacho (who may not want to use SVN at all) or may prefer to set it up on the therion server (it makes sense).
The patch is at http://wookware.org/therion_0.4.0-1.diff.gz where you can fish out the loch/*.cxx patches and ignore the rest
(I would like to discuss the makefile setup sometime. It is currently nice and simple to read but much of the make-work is actually done by perl-scripts and the cross-platform support is fairly primitive. I would like to bin the perl and make the makefiles use make constructs to decide what to do, and get smarter about library config (pckconfig, for example). This way lies autoconf, which I'm not sure is an improvement, but there is certainly room for improvement I think. If we could agree this that would be better than me making the debian version very different.)
Is there any point keeping libtom in the source? Is it not entirely superceded by loch?
Wookey
I think CMake is a good option: http://www.cmake.org/HTML/Index.html
If other people doing packaging agree, I have nothing against. S.
On 2006-10-11 10:20 +0200, Stacho Mudrak wrote:
I think CMake is a good option: http://www.cmake.org/HTML/Index.html
If other people doing packaging agree, I have nothing against.
I haven't used cmake myself yet, but I have only heard good things about it. It does not cover every bizarre ancient system like automake does, but then we don't care about them, and automake is incomprehensible to mere mortals. And it does cover the important systems that therion actually runs on, whilst also being reasonably comprehensible. If anyone (philip?) is enthused to convert the existing Makefiles to cmake then I think that would probably be a good thin all round. It probably does require moving to a version-control system though so we don't tread on each other's toes. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://wookware.org/
I'll work on trying to convert the make files to cmake today. Philip Schuchardt On Wednesday 11 October 2006 10:51 am, Wookey wrote:
On 2006-10-11 10:20 +0200, Stacho Mudrak wrote:
I think CMake is a good option: http://www.cmake.org/HTML/Index.html
If other people doing packaging agree, I have nothing against.
I haven't used cmake myself yet, but I have only heard good things about it. It does not cover every bizarre ancient system like automake does, but then we don't care about them, and automake is incomprehensible to mere mortals. And it does cover the important systems that therion actually runs on, whilst also being reasonably comprehensible.
If anyone (philip?) is enthused to convert the existing Makefiles to cmake then I think that would probably be a good thin all round.
It probably does require moving to a version-control system though so we don't tread on each other's toes.
Wookey
Wookey napsal(a):
On 2006-10-10 17:21 -0400, Philip Schuchardt wrote:
Where can I submit changes to the source. We really need svn and trac...
.....
(I would like to discuss the makefile setup sometime. It is currently nice and simple to read but much of the make-work is actually done by perl-scripts and the cross-platform support is fairly primitive. I would like to bin the perl and make the makefiles use make constructs to decide what to do, and get smarter about library config (pckconfig, for example). This way lies autoconf, which I'm not sure is an improvement, but there is certainly room for improvement I think. If we could agree this that would be better than me making the debian version very different.)
For easy packaging for different Linux distros make DEST parameter is really needed. Than I can create build scripts for Slackware and Arch.
Is there any point keeping libtom in the source? Is it not entirely superceded by loch?
I think it is little bit confusing to have two viewers. Is it posible that the Model viewer menu item in xtherion will be just launcher for loch? Or what is the idea of having two different viewers? As Stacho wrote default 3D model format is .lox now. Is buit-in viewer able to open this format? L.
Quoting Ladislav Blazek <lblazek@speleo.cz>:
I think it is little bit confusing to have two viewers. Is it posible that the Model viewer menu item in xtherion will be just launcher for loch? Or what is the idea of having two different viewers?
There is no idea. If nobody will protest, there is no problem to remove 3D viewer from xtherion in the next release. S.
Our firewall in the office allows us to access only HTTP services, therefore we would have no access to SVN and other tools :( And until now, there were not so many patches to therion.
Where can I submit changes to the source. We really need svn and trac...
Please, use following link to submit patches: https://savannah.nongnu.org/patch/?group=therion
I am sorry, but your page is not available to me, no idea why. Could you please sumbit this patch to savannah? Thanks, S.
On 2006-10-11 10:13 +0200, Stacho Mudrak wrote:
Our firewall in the office allows us to access only HTTP services, therefore we would have no access to SVN and other tools :( And until now, there were not so many patches to therion.
SVN can be used under webdav, I believe, which I think is http only. I haven't got that set up on my server though. Looks like we should use the savannah.org facilities anyway, assuming you can access them sensibly.
Where can I submit changes to the source. We really need svn and trac...
Please, use following link to submit patches:
OK. I should do that with debian ones too., henceforth, I assume. <creates savanaha account> Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://wookware.org/
Looks like we should use the savannah.org facilities anyway, assuming you can access them sensibly.
I think, this patch collection system is a reasonable first iteration to the full version control.
OK. I should do that with debian ones too., henceforth, I assume. <creates savanaha account>
No account is needed, anonymous patches are accepted. S.
I've always been interested in the google code hosting service at: http://code.google.com/hosting/ I don't know much about their stability and uptime though. Philip Stacho Mudrak wrote:
Looks like we should use the savannah.org facilities anyway, assuming you can access them sensibly.
I think, this patch collection system is a reasonable first iteration to the full version control.
OK. I should do that with debian ones too., henceforth, I assume. <creates savanaha account>
No account is needed, anonymous patches are accepted.
S.
_______________________________________________ Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
Hello, I've just downloaded the latest version of therion (0.4.1, dev. snapshot of 2006_10_12). When I compile these sources, everything goes OK till it starts to compile loch, the new 3D viewer... The problem mainly seems to be in some headers : it answer frequently that it doesn't find the vtk headers, such as vtkPointData.h, so that it generates a lot of consequent errors But in my case, I have an installation of vtk, coming with Paraview... This should be ok, no ? Otherwise, how can I show the path to these headers to the compiler ??? Apart from this point, it works well !! Thanks Thierry
On 2006-10-15 10:02 +0200, thierrygonon wrote:
Hello,
I've just downloaded the latest version of therion (0.4.1, dev. snapshot of 2006_10_12). When I compile these sources, everything goes OK till it starts to compile loch, the new 3D viewer... The problem mainly seems to be in some headers : it answer frequently that it doesn't find the vtk headers, such as vtkPointData.h, so that it generates a lot of consequent errors But in my case, I have an installation of vtk, coming with Paraview... This should be ok, no ? Otherwise, how can I show the path to these headers to the compiler ??? Apart from this point, it works well !!
Set the path in the loch Makefile. e.g. (on a debian system) VTKPATH = /usr/include/vtk-5.0 it will no doubt be different on your setup. I had to change the libs list as well. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://wookware.org/
I need to finish converting the makefiles to the cmake... Cmake should automatically find all the include directories and libraries. Steelwool On Monday 16 October 2006 10:11 pm, Wookey wrote:
On 2006-10-15 10:02 +0200, thierrygonon wrote:
Hello,
I've just downloaded the latest version of therion (0.4.1, dev. snapshot of 2006_10_12). When I compile these sources, everything goes OK till it starts to compile loch, the new 3D viewer... The problem mainly seems to be in some headers : it answer frequently that it doesn't find the vtk headers, such as vtkPointData.h, so that it generates a lot of consequent errors But in my case, I have an installation of vtk, coming with Paraview... This should be ok, no ? Otherwise, how can I show the path to these headers to the compiler ??? Apart from this point, it works well !!
Set the path in the loch Makefile. e.g. (on a debian system) VTKPATH = /usr/include/vtk-5.0
it will no doubt be different on your setup.
I had to change the libs list as well.
Wookey
There still might be a problem with offscreen rendering. It is completely platform dependent and I have no idea how to do it on Cocoa. S. Quoting Philip Schuchardt <ohc@vt.edu>:
I need to finish converting the makefiles to the cmake... Cmake should automatically find all the include directories and libraries.
Steelwool
On Monday 16 October 2006 10:11 pm, Wookey wrote:
On 2006-10-15 10:02 +0200, thierrygonon wrote:
Hello,
I've just downloaded the latest version of therion (0.4.1, dev. snapshot of 2006_10_12). When I compile these sources, everything goes OK till it starts to compile loch, the new 3D viewer... The problem mainly seems to be in some headers : it answer frequently that it doesn't find the vtk headers, such as vtkPointData.h, so that it generates a lot of consequent errors But in my case, I have an installation of vtk, coming with Paraview... This should be ok, no ? Otherwise, how can I show the path to these headers to the compiler ??? Apart from this point, it works well !!
Set the path in the loch Makefile. e.g. (on a debian system) VTKPATH = /usr/include/vtk-5.0
it will no doubt be different on your setup.
I had to change the libs list as well.
Wookey
Therion mailing list Therion@speleo.cz http://www.speleo.cz/mailman/listinfo/therion
participants (6)
-
Ladislav Blazek -
Philip Balister -
Philip Schuchardt -
Stacho Mudrak -
thierrygonon -
Wookey