Hi John,

The best possibility I can come up with is dh-virtualenv
http://dh-virtualenv.readthedocs.io/en/1.0/usage.html

I am far from a python guru and it looks fiendishly complicated, but appears to allow a virtual python environment during a package build.

Not sure however whether it requires python3.x or if it can be used for the exact purpose you require.

regards


On 04/10/17 19:26, John Morris wrote:
It occurs to me there's another possibility for cross-building Multi-Arch packages that might be somewhat simpler than the `gcc --sysroot` system I've been working on with Mick, but maybe a python guru would know better about the feasibility.

Under normal Multi-Arch cross-building circumstances, we would use e.g. `mk-build-deps --host-arch armhf -i`, and all armhf-arch dependency packages would be installed alongside the amd64 versions. Then we'd build the package as usual, while specifying the host arch, e.g. `dpkg-buildpackage -a armhf`.

However, because MK uses many python dependencies, and building Multi-Arch python packages is non-trivial [1], the `mk-build-deps` command uninstalls the amd64 build-arch `python2.7` and other packages in order to install the armhf host-arch deps (python-simplejson, libboost-python-dev, cython, python-tk, python-protobuf). Of course this would break the build, since the amd64 build-arch python would be missing.

I wonder if a build-arch python could somehow be installed outside the packaging system, for example in /usr/local, and just for the package build, we point to that python. Then the packaging system could be fooled into cross-building armhf packages, and the only antics we'd have to perform would be installing the alternative python version.

Does anyone think they know how to do that, install python outside of the packaging system? Maybe that means build from source, or maybe it means install the amd64-arch package first and move it out of the way, or maybe use some other creative means. This would be a really valuable thing to have going forward, since it would clear the path for cross-building packages for many Debian releases to come without the difficult antics of the currently proposed system.

[1]: https://wiki.debian.org/Python/MultiArch

    John


--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to