Developer Workflow Improvements: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(Drop completed tasks)
Line 10: Line 10:
* Write test script for SDK
* Write test script for SDK
* Randy: getting errors from bitbake about changed signatures - behaviour change after Hongxu's patch?
* Randy: getting errors from bitbake about changed signatures - behaviour change after Hongxu's patch?
* <strike>Update environment setup script to use buildsystem toolchain -- ''Done but needs testing and function dependent on uninative - Randy''</strike>
* Fix runqemu''(and possibly other tools?)'' since we no longer have the nativesdk sysroot ''(Add them to buildtools-lite?)''
* Fix runqemu''(and possibly other tools?)'' since we no longer have the nativesdk sysroot ''(Add them to buildtools-lite?)''
* <strike>Refactor to move functionality to SDK classes rather than meta-newsdk recipe</strike>
* 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.
* 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
* 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 errors when restoring from sstate (should it even try?)
* uninative-tarball reports "WARNING: Function  doesn't exist" during build
* uninative-tarball reports "WARNING: Function  doesn't exist" during build
* <strike>Error when running recipetool from devtool "Error: The OE SDK/ADT was detected as already being present in this shell environment. Please use a clean shell when sourcing this environment script." - probably need to bypass this check via an extra environment variable</strike>
* 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.
* 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 message to the start of the environment script with pointers to the things you can do with it
Line 23: Line 20:


=== devtool ===
=== devtool ===
* <strike>Need to run do_populate_sysroot when you run "devtool build" (so that libraries can be added)</strike>
* <strike>Add an option for modify / add to use the same directory for source and build where that's required</strike>
* Add support for plugins in multiple layers
* Add support for plugins in multiple layers
* Support 'devtool modify linux-yocto' -- ''Extract/build working, but modify is missing config creation - Paul''
* Support 'devtool modify linux-yocto' -- ''Extract/build working, but modify is missing config creation - Paul''
Line 30: Line 25:
* extract: Try to get author/date info about patches from metadata git history if not able to find it any other way?
* 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
* update-recipe: warning when running on mdadm: WARNING: Variable key FILES_${PN} ( ${base_libdir}/udev/rules.d/*.rules) replaces original key FILES_mdadm
* 'devtool modify' needs to at least try to get initial revision when -x is not specified - ''In progress - Paul''
* 'devtool deploy-target' needs to be more verbose about ssh failures (just get "lost connection" on e.g. known host key mismatch) - ''In progress - Paul''
* Add option to 'devtool deploy-target' to add "-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no" to ssh/scp command - ''In progress - Paul''


=== recipetool ===
=== recipetool ===
Line 40: Line 32:
* Handle USE_* options in Makefiles?
* Handle USE_* options in Makefiles?
* Extract dependencies from cmake
* Extract dependencies from cmake
* LICENSE files can be picked up twice if they match more than one expression in our list e.g. COPYING.GPL - ''In progress - Paul''

Revision as of 12:22, 20 March 2015

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
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Developer_Workflow_Improvements&oldid=14336"