On Mon, 09. Jul 22:33, Baptiste Carvello wrote: > Hi Radi, hi Frédéric, Hi > > I'm still around, but I've been fighting with the tools (cowbuilder > mostly, it now works, and I get the same build error as Frédéric). Did you checkout my latest commits. I fixed the build errors. > > Regarding the python packages, I don't think we can rely much on the > upstream build system, as they just set PYTHONPATH and use the modules > in-place in the source tree. So we'll have to copy the .py files, and > maybe a few data files too (not sure, I found some, but they seem to > only be used in tests). > > As far as the setup.py is concerned, my proposition would be to write a > fake 'build' stage that executes after the upstream build system and > only copies the files to the appropriate places, so that the distutils > 'install' stage can find them. I thought so too. My intension with this setup.py file was only to get a clean installation of the modules. If just cp the *ext.so from ./lib to cctbx_sources and call: python setup.py install --root=/whatever/path we already get a clean install. As for now all Shlibs will go into ./lib/usr/lib. So they can be copied then too. I guess the best would be to specify a prefix during the build. But I'm not entirely sure yet. The problem is there are so much shlibs build. A few of them should go into seperate binary packages (libcctbx0, libsctbx0...) I can easily do this with regex but I'd like a more elegant method.
regards Radi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
