I am trying to write a Yocto/BitBake recipe which wraps WALinuxAgent. Therefore, I need to ensure that the build honours all paths and distro features of a cross-build, instead of querying native Python paths.
At the moment, I am using the --lnx-distro, --lnx-distro-version and --lnx-distro-name user flags, as well as maintaining a fork which identifies my particular Yocto-based Linux distro.
The setup.py script appears to still use the "legacy" install method instead of Python wheels. This means that the setuptools3.bbclass BitBake bbclass, which uses bdist_wheel distribution strategy doesn't work brilliantly well. In particular, it seems I can no longer specify the --lnx- flags to enable the cross-build.
Could you provide any advice? Is there any intention of upgrading to Python3 wheels?
@benmordaunt Sorry, at this point we don't have any plans to upgrade to Python3 weeks. I'll leave this issue open so that we can get to it at a later date.
Hi,
I am trying to write a Yocto/BitBake recipe which wraps WALinuxAgent. Therefore, I need to ensure that the build honours all paths and distro features of a cross-build, instead of querying native Python paths.
At the moment, I am using the
--lnx-distro
,--lnx-distro-version
and--lnx-distro-name
user flags, as well as maintaining a fork which identifies my particular Yocto-based Linux distro.The
setup.py
script appears to still use the "legacy" install method instead of Python wheels. This means that thesetuptools3.bbclass
BitBake bbclass, which uses bdist_wheel distribution strategy doesn't work brilliantly well. In particular, it seems I can no longer specify the--lnx-
flags to enable the cross-build.Could you provide any advice? Is there any intention of upgrading to Python3 wheels?
Thanks