From: Joao C. <jc...@fe...> - 2003-02-28 01:00:48
|
On Thursday 27 February 2003 20:49, Rafael Laboissiere wrote: > * Jo=E3o Cardoso <jc...@fe...> [2003-02-27 19:07]: > > But now I'm starting to think that a newer release will only happen i= n > > within a year, as we usually only release once a year, given our > > limited human resources. > > I thus think that's a pity that my improvements will only reach users= in > > 2004. Also, the "bug fix" turned out to be a major configuration > > redesign. > > > > My question is if we should not abandon the bug fix release, and take > > the April opportunity to make a new real release instead. > > I think that Alan will agree with me on this: what determines the relea= se > number is the improvement in CVS, not the reverse. So, if your changes= are > integrated and if they build and work correctly until April, I do not s= ee > any problem in committing it. We should just be careful to not put HEA= D in > a severe bad state. Well, they were working after 5.2.0 but before your configuration changes= =2E As=20 a matter of fact I'm expecting your help with the configuration issue. > > plgriddata() takes non-uniformly sampled data and will resample it us= ing > > several techniques, returning gridded data ready for use with our 3D > > data APIs. > > > > The new function requires access to an well know external library, Qh= ull > > (that Rafael knows well), http://www.thesa.com/software/qhull/, > > and to other simple libraries, libnn and libcsa, > > http://www.marine.csiro.au/~sakov/ > > Sounds great. > > > libnn and libcsa are small libraries not widely know and its > > configuration does not supports shared libraries. libnn also needs a > > patch to work with Qhull, because by default it works with "triangle"= , > > http://www-2.cs.cmu.edu/~quake/triangle.html, which is a non-free > > program. > > > > I think that the most effective way of using libnn and libcsa is to > > incorporate them into our source tree. I have already asked to libcsa= and > > libnn author's permission, and he agreed. > > I would avoid this if possible. Me too, but we would have to distribute nn and csa ourself, which would p= ut an=20 extra configuration/maintenance burden on ourself. Also, libnn needs a patch, and it is not reasonable in the auto-everythin= g=20 world to ask users to do it for us ;-) > I took a look at libnn. It compiles fine, > but generates only a static lib. I agree with you that integrating it = in > our source tree is probably the best thing to do. The way how I setup them in my sources was to create two subdirectories i= n=20 src, one to hold a striped version of nn and another subdir to hold a str= iped=20 csa. csa can always be built, as it depends on nothing, while nn should o= nly=20 be built if Qhull is available. In the src directory there is a new file,= =20 plgriddata.c, which is always built. As I said in another mail, I don't have much time now, but I can try to u= se=20 the Carnival holiday to update my setup to your configuration changes (th= at=20 you will latter hopefully fix :) and commit them. I will commit my other changes latter. Joao |