linux/poky.git/meta/classes/native.bbclass, branch 1.4_M1

classes: Drop do_package stamp-extra-info

2012-11-21T16:56:03+00:00

This was needed when do_package for target recipes was target specific however since it now isn't we can remove these stale references. (From OE-Core rev: 1c54d8c3639659bc8cf8fa2786a1aa9ed785b723) Signed-off-by: Richard Purdie

classes: Be consistent about sstate-inputdirs/outputdirs ending with '/'

2012-11-14T14:38:28+00:00

If sstate-inputdirs and sstate-outputdirs don't match with ending '/' characters, the manifest file can end up corrupted. This change ensures the metadata is consistent in ending do_populate_root tasks with this character to avoid manifest file corruption. (From OE-Core rev: 3910eaf88d14904eef85b9e391387547df7fc54e) Signed-off-by: Richard Purdie

classes: replace virtclass-native(sdk) with class-native(sdk)

2012-11-02T16:18:27+00:00

The overrides virtclass-native and virtclass-nativesdk are deprecated, which should be replaced by class-native and class-nativesdk. [YOCTO #3297] (From OE-Core rev: 9fbeab63315fef0dbcc91c5e7051665764758a6e) Signed-off-by: Robert Yang Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

package.bbclass: Switch shlibs to pkgdata directory and make package non-machine specific

2012-10-22T08:47:47+00:00

Currently, do_package is machine specific since the shlibs data is installed into each machine specific sysroot. This change moves the shlibs data to the pkgdata structure, at the expense of having to iterate over a set of shlibs directories instead of a single one. It turns out this isn't any particular hardship for the code and as a result, do_package stops being machine specific leading to optimisations for builds that use a common PACKAGE_ARCH. (From OE-Core rev: cc088489d70fb27d460c3dbe35d6ea382123c134) Signed-off-by: Richard Purdie

native.bbclass: correct PATH to have native-intercept be prepended

2012-06-28T15:26:44+00:00

This was needed since it was after the sysroots and thus in some cases the native sysroot chown was being found and used instead of the script provided by native-intercept/chown. This was noticed by the non-gplv3 build since it's coreutils depends on coreutils-native. (From OE-Core rev: bb5095d3f73a00222f50f9dd2cf8dc27cc72b4a2) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

classes: Add recipe class to overrides

2012-04-30T10:37:22+00:00

We have currently no override to detect a recipe being build cross, crosssdk or for target at times we can use virtclass-native and virtclass-nativesdk to override stuff in recipes but we dont have way to modify a variables based on recipe type always. This patch adds in such an override and in particular makes a target override class available. With this change now we can say: EXTRA_OECONF_class-target = "...." EXTRA_OECONF_class-native = "..." EXTRA_OECONF_class-nativesdk = "..." EXTRA_OECONF_class-crosssdk= "..." Based of an original patch by Khem Raj (From OE-Core rev: cf332fd9bf685f6d42b11c1f0c37b934c7f5bcbe) Signed-off-by: Richard Purdie

gzip/pigz-native: Install into a prefix to avoid clashing with system binaries

2012-03-21T15:33:07+00:00

Due to the system providing a copy of gzip, we face some issues when we 'shadow' that copy with our own leading to a varient of race type bugs, and issues for example if a dependency such as libz is missing but the binary is still present. We usually rely on our dependency logic to protect us from this but for gzip, we don't have this protection since its not listed by all its users (and doing so would be impractical). This patch installed pigz and gzip into their own directory which we only add to PATH when we explictly want these binaries in much the same way we do with perl-native. This means dependency logic is correct when we use the binary and everything should work well. The patch adds an explict dependency into image.bbclass since the accelerated speed of compression is most appreciated at rootfs time. (From OE-Core rev: 7a98c0ef28822ae1fcee45b14db3edcfd4c7ad8f) Signed-off-by: Richard Purdie

native.bbclass: make TOOLCHAIN_OPTIONS empty

2012-03-19T20:28:46+00:00

The native pkg doesn't need the TOOLCHAIN_OPTIONS, but it maybe used by native pkgs, for example, the cmake.bbclass uses TOOLCHAIN_OPTIONS: OECMAKE_C_FLAGS ?= "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} ${CPPFLAGS}" and TOOLCHAIN_OPTIONS is: TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}" If a native pkg inherits cmake.bbclass, then: TOOLCHAIN_OPTIONS = " --sysroot=" and OECMAKE_C_FLAGS would be: ${HOST_CC_ARCH} --sysroot= ${CPPFLAGS} This would cause unexpected errors, I think that we can make TOOLCHAIN_OPTIONS empty in native.bbclass since native pkg doesn't need it. [YOCTO #2124] (From OE-Core rev: e5555c743a9637f86a0a2c4c45a63a80838e81ae) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

native.bbclass: Fix variable remapping coverage

2012-01-05T12:36:28+00:00

When looking for RDEPENDS to process, bitbake iterates through PACKAGES *and* PN. Since native.bbclass sets PACKAGES to be empty, its pointless remapping the list of PACKAGES since this does nothing. There is a problem since *_${PN} are used by bitbake but not remapped by the native.bbclass class extension code. This changes the code to remap _${PN} in both expanded and unexpanded forms. As a result of this, various surprising dependencies are uncovered and the patch rectifies those. These are real bugs since they're injecting unneeded (unremapped) dependencies into the dependency chain. (From OE-Core rev: 0f485bfd6fc82a109b9da629e464fca1e90faec3) Signed-off-by: Richard Purdie

classes, conf: Exclude native and nativesdk recipes from libc specific override

2011-12-01T16:54:07+00:00

Based on suggestions from RP libc-uclibc and libc-glibc overrides are for denoting system C library in use on the target and not for the host therefore we make sure that the override only takes effect for target recipes only. (From OE-Core rev: 6e2b53f47da0e97271fb51b281d24da1e1d549cc) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie