linux/poky.git/meta/classes/populate_sdk_rpm.bbclass, branch mickledore-next

classes: Combine rootfs_ and populate_sdk_

2014-08-15T17:21:46+00:00

There is no real reason to have these separate files any longer. It does mean in meta-toolchain type recipes some extra variables are defined but it also means the common code can be grouped and maintained together which I believe is more beneficial. We therefore merge the classes. (From OE-Core rev: 2cf42b49003494e1b10775523c9a2547eaf16ea4) Signed-off-by: Richard Purdie

populate_sdk_*: Drop now unneeded recrdeptask flags

2014-03-30T09:10:33+00:00

Now populate_sdk_base has the appropriate flags, we can drop these from the individual classes. (From OE-Core rev: 388bfe2dc168d31ba3c5c85684f3c96d2ae13800) Signed-off-by: Richard Purdie

populate_sdk_*.bbclass: remove old rootfs_list_installed_depends()

2014-03-12T03:28:56+00:00

We're using the python routines now. (From OE-Core rev: 04fa624394a6400803425fd61a79ce9552a79f99) Signed-off-by: Laurentiu Palcu Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

populate_sdk_rpm.bbclass: remove old shell code

2014-02-11T11:53:42+00:00

The old code no more needed since the job is done in python now. (From OE-Core rev: 96bf2a93bb75fea23732014106039e14d72cd1c7) Signed-off-by: Hongxu Jia Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

classes/image: write image manifest

2013-11-26T23:01:32+00:00

Write a list of installed packages to a .manifest file next to the image, so we can find out what went into the image after it has been constructed without necessarily having to have buildhistory enabled (although that will provide more detail.) We can make use of this for example in the testimage class associated code that checks for installed packages for determining whether or not to run specific tests. Note: this replaces the previous ipk-specific manifest code with something that works for ipk, rpm and deb, and instead of a pruned status file, packages are listed one per line, in the following format: Tests for all three backends have shown that the performance impact of this change is negligible (about 1.5s max). Implements [YOCTO #5410] (From OE-Core rev: 2978d1f2617a33e2e3a77e249d73e998d79b4ec9) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

populate_sdk_rpm: Only remove trailing whitespace, not all whitespace

2013-09-12T07:23:41+00:00

(From OE-Core rev: 06cb4deba6e4df4ffe3015602d5997b26d28778b) Signed-off-by: Richard Purdie

populate_sdk_rpm: Ensure empty strings aren't passed to attemponly rpm code

2013-09-11T22:31:01+00:00

If empty strings are passed to the rpm attemptonly code, it breaks. This ensures we don't do that. (From OE-Core rev: 6a0d5a3158608364f6baa11fe9ab7fa1f8e251ab) Signed-off-by: Richard Purdie

classes/buildhistory: record size of installed package not compressed archive

2013-08-16T10:44:16+00:00

* usually it's more important to know how much space will each package take on target device then size of compressed package * example for libewebkit0 with 4 different architectures, interesting that om_gta02 .ipk is bigger but it's smaller when installed before: MACHINE DEFAULTTUNE SIZE (.ipk file) om_gta04 cortexa8t-neon 15996 KiB libewebkit0 qemux86_64 x86-64 16992 KiB libewebkit0 spitz xscale 16148 KiB libewebkit0 om_gta02 arm920t 16260 KiB libewebkit0 after: MACHINE DEFAULTTUNE SIZE (installed) om_gta04 cortexa8t-neon 60544 KiB libewebkit0 qemux86_64 x86-64 63720 KiB libewebkit0 spitz xscale 60588 KiB libewebkit0 om_gta02 arm920t 56268 KiB libewebkit0 (From OE-Core rev: 85e4a77138381a6086d5ebd3a28cb5a94bc26a19) Signed-off-by: Martin Jansa Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

package/populate_sdk: Move functions from package_* to populate_sdk_*

2013-03-23T17:40:27+00:00

This fixes build failures introduced with "classes/buildhistory: implement history collection for SDK" by moving the functions to files where only the specific image type which is enabled is inherited. The failures occured when multiple PACKAGE_CLASSES were enabled. (From OE-Core rev: 9a414a57ad69a426a8d8a2970c42ca7427240615) Signed-off-by: Richard Purdie

classes/buildhistory: implement history collection for SDKs

2013-03-23T11:41:13+00:00

SDKs are constructed in a similar manner to images, and the contents can be influenced by a number of different factors, thus tracking the contents of produced SDKs when buildhistory is enabled can help detect the same kinds of issues as with images. This required adding POPULATE_SDK_POST_HOST_COMMAND and SDK_POSTPROCESS_COMMAND variables so that data collection functions can be injected at the appropriate points in the SDK construction process, as well as moving the list_installed_packages and rootfs_list_installed_depends functions from the rootfs_{rpm,ipk,deb} to the package_{rpm,ipk,deb} classes so they can also be called during do_populate_sdk as well as do_rootfs. Implements [YOCTO #3964]. (From OE-Core rev: c3736064483d4840e38cb1b8c13d2dd3a26b36aa) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie