Re: RE : RE : RE : cctbx debian package
Hi,
Le 09/07/2012 23:04, Radostan Riedel a écrit :
> Did you checkout my latest commits. I fixed the build errors.
Indeed, it now builds, but the install step fails with:
dh_install --fail-missing --package=cctbx-bundle build2.7-omp/bin/* \
usr/bin
dh_install: cctbx-bundle missing files (build2.7-omp/bin/*), aborting
make: *** [install.cctbx-bundle] Error 2
(tested with 0a5fb8d)
> 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.
One small difficulty though: the extensions need to be built for all the
supported python versions. So we'll need to call the build system
several times. And to install each version of the extension at the right
place.
By the way, I had a look at the import wrapper they use for loading
extensions (boost.python.import_ext) and wrote a few lines about it in
the wiki.
> 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.
There is a dh_install helper, which can be used to split files into
separate packages. I'm not sure if it does what you want. It also uses
lists and regexes :-)
Cheers,
Baptiste
Reply to: