Hi Hubert, On Tue, Oct 23, 2018 at 11:02:13PM -0400, Hubert Chathi wrote: > Thanks for filing this issue. Olm 3 was released today, which has new > Python bindings, and which will make python-olm arch-dependent. I'll > take a look at this issue when I create a new package, but having just > skimmed this briefly, suggestion are welcome on how having python-olm > being arch-dependent will affect this issue.
That'll render my patch essentially useless. I suggest that you leave this bug open as long as python-olm is arch-independent. Once it becomes arch-dependent, you close it with tags + wontfix. The closure will prompt me to look into it again. Python extensions can still be cross built. The dh-python dependency is fine. python-all-dev is the problematic once. For enabling cross compilation you typically use "libpython-all-dev, python-all-dev:native" instead. Given that ":native" is irrelevant for native builds and that python-all-dev depends on libpython-all-dev that works for native builds as well. Then it depends on how the extension is built. The most common ways include some form of setup.py and autotools. I'd expect autotools to just work. For setup.py, you need to pass the cross toolchain along. I think dh-python does that for Python 3.x already. In general, going with the helpers tends to work best (e.g. use "dh_auto_configure -- --with-foo" instead of "./configure --with-foo"). Helmut
