Developer Workflow Improvements

From Yocto Project
Revision as of 12:22, 20 March 2015 by PaulEggleton (talk | contribs) (Drop completed tasks)
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

SDK

  • 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?
  • Fix runqemu(and possibly other tools?) since we no longer have the nativesdk sysroot (Add them to buildtools-lite?)
  • 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.
  • Installing the sdk to /opt requires root perms, but if you run the installer under sudo/as root then the inner execution of bitbake to prepare the SDK fails at sanity check
  • uninative-tarball errors when restoring from sstate (should it even try?)
  • uninative-tarball reports "WARNING: Function doesn't exist" during build
  • When publishing the SDK(tool not available yet), warn the user if there are items added to the image/distro via local.conf and suggest moving the items the distro or image config.
  • Add a message to the start of the environment script with pointers to the things you can do with it
  • Add a note to the generated local.conf/bblayers.conf mentioning that it's auto-generated and warning against editing

devtool

  • Add support for plugins in multiple layers
  • Support 'devtool modify linux-yocto' -- Extract/build working, but modify is missing config creation - Paul
  • Use git to track changes made by extra task functions?
  • extract: Try to get author/date info about patches from metadata git history if not able to find it any other way?
  • update-recipe: warning when running on mdadm: WARNING: Variable key FILES_${PN} ( ${base_libdir}/udev/rules.d/*.rules) replaces original key FILES_mdadm

recipetool

  • Rudimentary spec file conversion?
  • Ability to do interactive adds via a UI
  • Add comments in on do_configure(_append), do_install_(append) etc.
  • Handle USE_* options in Makefiles?
  • Extract dependencies from cmake