Hello Andre, On Thu, 2010-02-11 at 17:32 +0100, Andre Espaze wrote: > Hi Adam, > > I am André Espaze, the Logilab's employee supposed to help you in the > Salomé packaging for Debian. First I wanted to thank you for the great > work that you did on the current package. Then I would like to let you > know my progress on the testing part. Great, thanks for following up on this. > I have succeeded to build most of the Salomé modules with the > version 5.1.3-3 that you uploaded at http://lyre.mit.edu/~powell/salome/ > however I wanted to discuss the following problems: > > - the configure step in 'debian/rules' needs to add VTKSUFFIX="-5.4" > else vtk is not found and many components do not build. Indeed, I built -3 before VTK 5.4 was in unstable. I am using --with-vtk-version=5.4 which seems to do the same thing. > - it lacks the omniorb4-nameserver package in the dependency list > else the KERNEL component does not find the omniNames command. Okay, the salome binary package needs to depend on this, right? I don't think it needs to be in Build-Depends. > - as you said, the med 2.3.5 library needs to be built manually > with hdf5-1.8.4 but the main problem is that tests do not pass > in that case. There are patches to hdf5 (bug 510057) and med (bug 566828, fix is in the git repository) to build these two using the default MPI implementation, e.g. OpenMPI on most arches, LAM on others (soon MPICH2, which will require further changes to the current HDF5 package...). The HDF5 team is a bit slow to adopt patches, but hopefully plans for a March freeze will get this done, so MED-MPI and Salomé can get in. > - it seems to lack the 'config.h' file in the libopencascade-* > packages. Else do you know where that file could be? I fear that > some components (like GEOM) really need it. Denis replied to this. I didn't notice any problems building GEOM, are there run-time issues which could result from missing this file? > - the GEOM module crashes when trying to add a geometrical object I see. Could this be related to the OCC config.h issue? I don't see how... I'm impressed that it actually runs -- hadn't tried to run it yet! > You can find all the steps that I did, more details and also more problems > at: http://www.python-science.org/ticket/1383 Thanks, I'll look over this. > How to you plan to collaborate on the package building? I would suggest > to use the project http://www.python-science.org/project/salome-packaging > because I can be efficiently organized on such a platform. Would you > like to add a git or mercurial repository on which we will share the > package source code? It is already on the Debian Science git repository at http://git.debian.org/git/debian-science/packages/salome.git/ . I'm trying to get it to work with git/quilt, as right now a couple of the "clean" targets are a bit too aggressive -- they remove a lot that shouldn't be removed. > I am looking forward to work with you, I am as well! Thanks for the post. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
Attachment:
signature.asc
Description: This is a digitally signed message part