[Q] Yocto Integration
- Dominant language
- Python
- Stars
- 581
- Forks
- 397
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 9
Description
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 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?
Thanks
Contributor guide
Research direction
Start by reviewing setup.py and the setuptools3.bbclass workflow described in the issue, then trace how the --lnx-distro, --lnx-distro-version, and --lnx-distro-name flags are handled during a wheel build. Done would require a maintainer-approved approach for Yocto cross-build paths and distro features, plus a clear decision about Python 3 wheel support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100