Yocto prebuilt SDK integration

From SecretLab

Jump to: navigation, search

Prebuilt SDK integration

Goal

Speedup target image generation by reusing prebuilt tools from SDK native and target binaries

1. Generate prebuilt tarball with installable packages collection for native and target. Alternative set a package repository?

2. Populate sysrootfs from prebuilt native and target installable packages, similar to ADT sysroot population

  • Avoid package installation to use sudo by using pseudo? need to package pseudo to main Linux distributions?
  • Also in scripts/bitbake detect if host has pseudo installed and avoid to build it and save ~80 native recipes dependencies to provide pseudo.
  • Ship opkg-cl into main Linux distributions avoid build it to install ipk packages.

3. Build sstate-cache information or reuse the sstate-cache information generated in prebuilt sdk similar as SSTATE_MIRRORS

  • sstate-control? Generate package data entries from instalable package data information.

4. Work directory, fetch and patch tasks only run if recipes are explicit called, need an state to reflect this in sstate? Package installed but not local built.


Partial progress in the firts 2 task see [1]

  • package_sdk.bbclass cointains the generate_sdk_pkgs function which was part of task-poky-sdk.bb add a conditional variable to enable sdk packages generation.
  • In task-poky-sdk.bb PACKAGEFUNCS append generate_sdk_pkgs function if is enabled via user local variable PACKAGES_SDK_GEN
  • sdk-packager_0.1.bb recipe creates a tarball with all the sdk packages (only native packages at the moment).

Need further discussion, some similarities whit ADT.

[1] http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=aalonso/prebuilt-sdk

Retrieved from "http://wiki.secretlab.ca/Yocto_prebuilt_SDK_integration"
Personal tools