Developer Workflow Improvements: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Randy Witt (talk | contribs) |
PaulEggleton (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
* <strike>Make relocation in toolchain-shar-template.sh optional</strike> -- ''Done - Randy'' | * <strike>Make relocation in toolchain-shar-template.sh optional</strike> -- ''Done - Randy'' | ||
* Use uninative in new-sdk during setscene | * Use uninative in new-sdk during setscene | ||
* devtool in SDK needs fixing after toolchain changes | |||
* Refactor to move functionality to SDK classes rather than meta-newsdk recipe | |||
* Ensure we have bugzilla entries for additional major functionality | |||
Revision as of 17:53, 30 October 2014
Developer workflow improvements as documented in the following bugzilla entry:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6662
Todo list
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
- Modularise devtool -- In progress - Paul
- 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 - Randy- Use uninative in new-sdk during setscene
- devtool in SDK needs fixing after toolchain changes
- Refactor to move functionality to SDK classes rather than meta-newsdk recipe
- Ensure we have bugzilla entries for additional major functionality
