On Tue, 10. Jul 15:02, Baptiste Carvello wrote: > 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) Install target is not ready to use. We need to figure out how the package structure will look like first > 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. This is already done by the build target. It uses pyversions to determine for how many python versions a release has. > > 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. Looks good. I was thinking again about dependencies on small python packages. Maybe it's really best to do just one python package "python-cctbx" with all modules and all extensions? Else I don't have any clue how to build multiple packages with one setup.py. Do you? > > 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 :-) Interesting! I'll search the web for some info.
regards Radi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
