Developer Workflow Improvements: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(Add more tasks)
(Update status)
Line 21: Line 21:


=== devtool ===
=== devtool ===
* Add support for plugins in multiple layers
* <strike>The following recipes can't currently be extracted: linux-yocto*, *gcc*, perf</strike>
* <strike>The following recipes can't currently be extracted: linux-yocto*, *gcc*, perf</strike>
* <strike>Ensure messages are friendly</strike> (for now)
* <strike>Ensure messages are friendly</strike> (for now)
* <strike>Use proper logging for output</strike>
* <strike>Use proper logging for output</strike>
* Support 'devtool modify linux-yocto' - externalsrc doesn't seem to work here at the moment
* Add support for plugins in multiple layers
* Support 'devtool modify linux-yocto' - externalsrc doesn't seem to work here at the moment -- ''Started, paused until Bruce's patchset is ready - Paul''
* Avoid bitbake warning when workspace layer is empty
* Avoid bitbake warning when workspace layer is empty
* Add an option for modify / add to use the same directory for source and build where that's required
* Add an option for modify / add to use the same directory for source and build where that's required
* Basic support for updating patches from source tree git repository
* Basic support for updating patches from source tree git repository -- ''Started - Paul''
* Write tests for use next to the build system
* Write tests for use next to the build system


=== recipetool ===
=== recipetool ===
* Rudimentary spec file conversion?
* <strike>More comprehensive license auto-detection</strike>
* <strike>More comprehensive license auto-detection</strike>
* <strike>Use proper logging for output</strike>
* <strike>Use proper logging for output</strike>
* <strike>Ensure messages are friendly</strike> (for now)
* <strike>Ensure messages are friendly</strike> (for now)
* Rudimentary spec file conversion?
* Write tests for use next to the build system
* Write tests for use next to the build system

Revision as of 22:13, 11 December 2014

Developer workflow improvements as documented in the following bugzilla entry:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6662

Todo list

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 - Randy
  • Use uninative in new-sdk during setscene -- Done - Randy
  • devtool 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

  • The following recipes can't currently be extracted: linux-yocto*, *gcc*, perf
  • Ensure messages are friendly (for now)
  • Use proper logging for output
  • Add support for plugins in multiple layers
  • Support 'devtool modify linux-yocto' - externalsrc doesn't seem to work here at the moment -- Started, paused until Bruce's patchset is ready - Paul
  • Avoid bitbake warning when workspace layer is empty
  • Add an option for modify / add to use the same directory for source and build where that's required
  • Basic support for updating patches from source tree git repository -- Started - Paul
  • Write tests for use next to the build system

recipetool

  • More comprehensive license auto-detection
  • Use proper logging for output
  • Ensure messages are friendly (for now)
  • Rudimentary spec file conversion?
  • Write tests for use next to the build system