linux/poky.git/meta/classes/sstate.bbclass, branch 1.4_M3.rc1

sstate: Do not add the --no-run-if-empty arguement to xargs when on Darwin, as it is not supported.

2013-01-15T08:10:14+00:00

(From OE-Core rev: 73b34d43633717b99e4f2f669939939cfa59eecb) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sstate.bbclass:specify function dirs to avoid race

2013-01-09T15:05:26+00:00

Specify dirs in which the shell function "sstate_create_package" and "sstate_unpack_package" are executed and don't use ${B} as default dirs to avoid possible race with task do_rootfs at deb image creation time. [YOCTO #3674] (From OE-Core rev: ccef1cf783669a4683eda9d4b44dbe6bcf426259) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

sstate.bbclass: Improve stamp-extra-info task handling to avoid warnings

2012-12-17T17:24:58+00:00

If you change a machine to a different package architecture, you will see sstate errors about overwriting files as the code stands today. Instead it should clean out the files safely and correctly. This patch changes the naming of stamp-extra-info manifest files to avoid this problem. It will potentially trigger warnings during builds in existing TMPDIRs until the system adjusts to the new naming, these are harmless. [YOCTO #3521] (From OE-Core rev: 2cc8ee57f8148844bb7bcd4aaf34f6891cf3d410) Signed-off-by: Richard Purdie

sstate.bbclass: Remove unused/uneeded variable

2012-12-17T17:24:58+00:00

(From OE-Core rev: 33ddf788c04044c8fe7ffbadab8787a5b6603186) Signed-off-by: Richard Purdie

sstate.bbclass: Simplify overcomplicated cleanall function

2012-12-17T17:24:57+00:00

The code was written before SSTATETASKNAMES existed. Since it does exist, lets simply the code. (From OE-Core rev: 9817e2efdb94395655d711f5eadedcd249c8cffe) Signed-off-by: Richard Purdie

sstate: fix typo

2012-12-06T22:59:10+00:00

(From OE-Core rev: 17d27fd6e2750e6455f656159da56c3350c4b3cd) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sstate: fix typo

2012-12-06T16:36:08+00:00

(From OE-Core rev: 10cceb3854acd5c619d81011bac02da11ed580d2) Signed-off-by: Richard Purdie

sstate: fetch .siginfo files from SSTATE_MIRROR

2012-12-06T12:31:19+00:00

This would be useful for doing siginfo compares to understand why a build is not reusing something when using SSTATE_MIRROR. No error will be reported if it fails to find the .siginfo file [YOCTO #2898] [RP: Small tweaks] (From OE-Core rev: 6d86690330f0d43839b904fced4b4b02cb27b8c6) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

sstate.bbclass: fix detection of owners matching sstate files

2012-12-05T15:34:07+00:00

* without this patch: Python 2.7.3 >>> sstate_search_cmd = "grep -rl /OE/jansa-test/shr-core/tmp-eglibc/pkgdata/armv7a-vfp-neon-oe-linux-gnueabi/runtime-reverse/vim-common /OE/jansa-test/shr-core/tmp-eglibc/sstate-control --exclude=master.list | sed -e 's:^.*/::' -e 's:\.populate-sysroot::'" >>> cmd_array = sstate_search_cmd.split(' ') >>> search_output = subprocess.Popen(cmd_array, stdout=subprocess.PIPE).communicate()[0] grep: |: No such file or directory grep: sed: No such file or directory * Adding shell=True and using cmd string instead of array makes it work: >>> search_output = subprocess.Popen(sstate_search_cmd, shell=True, stdout=subprocess.PIPE).communicate()[0] >>> print search_output manifest-armv7a-vfp-neon-gvim.package manifest-armv7a-vfp-neon-vim-tiny.package manifest-armv7a-vfp-neon-vim.package But still isn't 100% reliable, I guess it's caused by some other package being removed from sstate while grep is already running. So sometimes grep can show error on STDERR >>> search_output = subprocess.Popen(sstate_search_cmd, shell=True, stdout=subprocess.PIPE).communicate()[0] grep: /OE/jansa-test/shr-core/tmp-eglibc/sstate-control/manifest-armv7a-vfp-neon-systemtap.package: No such file or directory (From OE-Core rev: d84f7d7a12b4271f7b2bfde9fb356d750abff15d) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

sstate.bbclass: fixed file-conflict check

2012-12-05T15:34:06+00:00

The value of subprocess.Popen().communicate()[0] is a string. Checking for '!= None' will always match causing bogus warnings regarding already staged files. (From OE-Core rev: acdd76482efc3caf80e9e0b7359be7ca724ae09a) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie