openembedded-core.git/meta/classes/allarch.bbclass, branch fido

allarch: Force TARGET_*FLAGS variable values

2015-12-08T22:14:48+00:00

TARGET_CPPFLAGS, TARGET_CFLAGS, TARGET_CPPFLAGS and TARGET_LDFLAGS may
differ between MACHINEs. Since they are exported they affect task hashes
even if unused which leads to multiple variants of allarch packages
existing in sstate and bouncing in the sysroot when switching between
MACHINEs.

allarch packages shouldn't be using these variables anyway, so let's
ensure they have a fixed value in order to avoid this problem.

(Compare with 05a70ac30b37cab0952f1b9df501993a9dec70da and
14f4d016fef9d660da1e7e91aec4a0e807de59ab.)

(From OE-Core master rev: d08fda21bfb7d264c238af0232a22cdd751f5150)

Signed-off-by: Mike Crowe 
Signed-off-by: Ross Burton 
Signed-off-by: Joshua Lock

allarch: Add warning about packagegroup

2014-08-23T22:01:51+00:00

Since we want to start including this class conditionally, detect cases
where packagegroup files use the old ordering and inform the user they
need to update this.

Signed-off-by: Richard Purdie

allarch: Generate same package for MIPS and non-MIPS targets

2014-07-25T14:33:31+00:00

LINKER_HASH_STYLE differs between MIPS and non-MIPS targets. This means
that LDFLAGS differs too. LDFLAGS is exported so it influences all task
hashes. Unfortunately this means that packages with architecture "all"
differ depending on whether they are built for a MIPS or non-MIPS target.
This causes a lot of unnecessary churn in the ipk/all directory when
switching build targets.

The simplest way to fix this is to ensure that LDFLAGS stays the same for
architecture "all" packages by clearing it. It shouldn't being used by such
packages anyway.

Signed-off-by: Mike Crowe 
Signed-off-by: Richard Purdie

allarch: Set empty TARGET_PREFIX and TARGET_FPU

2014-01-19T17:10:45+00:00

* set empty TARGET_PREFIX
  This has a bit weird reason caused by unsupported setup where
  external-toolchain is used in some DISTRO only for some MACHINEs
  and internal is used for other MACHINEs.
  Because external-toolchain usually comes with different TARGET_PREFIX
  it was causing allarch recipes to have different signatures even
  when they don't use toolchain at all.
  Empty TARGET_PREFIX also helps to find allarch recipes which still
  have default dependency on e.g. virtual/${TARGET_PREFIX}gcc.
* add TARGET_FPU just for completeness (it was used in icecc.bbclass
  but now it's vardepexcluded there as well)

Signed-off-by: Martin Jansa 
Signed-off-by: Richard Purdie

allarch.bbclass: set SDK_ARCH and SDK_CC_ARCH to "none"

2014-01-16T11:56:40+00:00

allarch packages shouldn't use these variables.

[YOCTO #5396]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific directory

2013-09-13T16:41:10+00:00

Currently we have a hierarchy of pkgdata directories and the code has to put together
a search path and look through each in turn until it finds the data it needs.

This has lead to a number of hardcoded paths and file globing which
is unpredictable and undesirable. Worse, certain tricks that should be
easy like a GL specific package architecture become problematic with the
curretn search paths.

With the modern sstate code, we can do better and construct a single pkgdata
directory for each machine in just the same way as we do for the sysroot. This
is already tried and well tested. With such a single directory, all the code that
iterated through multiple pkgdata directories and simply be removed and give
a significant simplification of the code. Even existing build directories adapt
to the change well since the package contents doesn't change, just the location
they're installed to and the stamp for them.

The only complication is the we need a different shlibs directory for each
multilib. These are only used by package.bbclass and the simple fix is to
add MLPREFIX to the shlib directory name. This means the multilib packages will
repackage and the sstate checksum will change but an existing build directory
will adapt to the changes safely.

It is close to release however I believe the benefits this patch give us
are worth consideration for inclusion and give us more options for dealing
with problems like the GL one. It also sets the ground work well for
shlibs improvements in 1.6.

Signed-off-by: Richard Purdie

allarch: Allow class to be included but overridden

2012-11-26T10:00:27+00:00

We have cases where we'd like to inherit this class by default but allow
special cases to override it. This change makes the code of the class
conditional on PACKAGE_ARCH remaining set to "all", allowing it to be
overridden. packagegroup usage is one case this is desirable.

Signed-off-by: Richard Purdie

classes: Drop do_package stamp-extra-info

2012-11-21T16:53:56+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.

Signed-off-by: Richard Purdie

allarch: No need to make packaging machine specific

2012-07-22T10:40:09+00:00

Normally do_package is machine specific but this makes little sense for allarch
recipes. This patch unsets the appropriate variable.

Signed-off-by: Richard Purdie

allarch.bbclass: disable shlib and debug symbol processing

2011-11-07T14:03:38+00:00

all-arch packages should not contain any binaries that need processing,
so disable the shared library dependency processing and debug symbol
splitting/stripping to save some time during packaging.

Signed-off-by: Paul Eggleton