Developer Workflow Improvements
From Yocto Project
Jump to navigationJump to search
Developer workflow improvements as documented in the following bugzilla entry:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6662
Todo list
- Ensure we have bugzilla entries for additional major functionality
SDK
Running recipetool from devtool within the SDK seems to be broken-- Fixed, was related to custom environment setup script not being used (as well as poor error reporting) - Paul- Properly report failures in bitbake execution during install (output is currently discarded)
- Prevent do_rootfs itself from executing on install - we only need the tasks that it depends upon
- Write test script for SDK
- Randy: getting errors from bitbake about changed signatures - behaviour change after Hongxu's patch?
- Update environment setup script to use buildsystem toolchain -- Done but needs testing and function dependent on uninative - Randy
Make relocation in toolchain-shar-template.sh optional-- Done - RandyUse uninative in new-sdk during setscene-- Done - Randydevtool in SDK needs fixing after toolchain changes (Make a native recipe?)-- Done - Randy- Fix runqemu(and possibly other tools?) since we no longer have the nativesdk sysroot (Add them to buildtools-lite?)
- Refactor to move functionality to SDK classes rather than meta-newsdk recipe
Extraction of SDK doesn't work in ubuntu container due to /bin/sh -> dash-- Done - Randy- nativesdk-qemu-helper_1.0.bb and qemu-helper_1.0.bb don't publish the same set of files. Investigate, since runqemu(and possibly other things) may need to come from the buildsystem's native sysroot.
devtool
- Add support for plugins in multiple layers
- The following recipes can't currently be extracted: linux-yocto*, *gcc*, perf
- Write tests for use next to the build system
recipetool
- Rudimentary spec file conversion?
- More comprehensive license auto-detection
- Write tests for use next to the build system