[OE-core] [PATCH 1/1] archiver.bbclass: Just archive gcc-source for all gcc recipes

Christopher Larson clarson at kergoth.com
Thu Mar 24 18:04:20 UTC 2016


On Thu, Mar 24, 2016 at 8:26 AM <mariano.lopez at linux.intel.com> wrote:

> From: Mariano Lopez <mariano.lopez at linux.intel.com>
>
> It is pointless to archive several times the gcc source.
> This change will archive gcc source once, for the gcc-source-{PV}
> recipe.
>
> [YOCTO #9327]
>
> Signed-off-by: Mariano Lopez <mariano.lopez at linux.intel.com>
> ---
>  meta/classes/archiver.bbclass | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/meta/classes/archiver.bbclass b/meta/classes/archiver.bbclass
> index b95176b..1546bd0 100644
> --- a/meta/classes/archiver.bbclass
> +++ b/meta/classes/archiver.bbclass
> @@ -61,6 +61,12 @@ python () {
>      else:
>          bb.debug(1, 'archiver: %s is included: %s' % (pn, reason))
>
> +    # We just archive gcc-source for all the gcc related recipes
> +    if d.getVar('BPN', True) in ['gcc', 'libgcc'] \
> +            and not pn.startswith('gcc-source'):
> +        bb.debug(1, 'archiver: %s is excluded, covered by gcc-source' %
> pn)
> +        return
>

Hmm, I wonder if it'd be possible to make this more generic, check for
work-shared or something.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160324/00b2ba92/attachment-0002.html>


More information about the Openembedded-core mailing list