Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] insane.bbclass: Add test for static .a libraries in non-staticdev packages
Date: Wed, 25 Jan 2012 15:44:40 +0000	[thread overview]
Message-ID: <1327506280.19643.255.camel@ted> (raw)
In-Reply-To: <1327456194-9871-1-git-send-email-sgw@linux.intel.com>

On Tue, 2012-01-24 at 17:49 -0800, Saul Wold wrote:
> This check verifies that non staticdev and non pic packages do not
> have static libraries in them. There are a few exceptions for the
> libgcc-dev and libgcov-dev packages which are whitelisted, also the
> *_nonshared.a need to be part of their respective -dev packages.
> 
> This is currently a warning to work out any other issues in the upper
> layers but will be moved to ERROR at somepoint in the future.
> 
> [YOCTO #663]
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/classes/insane.bbclass |   20 +++++++++++++++++++-
>  1 files changed, 19 insertions(+), 1 deletions(-)
> 
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index ce21496..7aea73b 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -109,7 +109,7 @@ def package_qa_get_machine_dict():
>  
> 
>  # Currently not being used by default "desktop"
> -WARN_QA ?= "ldflags useless-rpaths rpaths unsafe-references-in-binaries unsafe-references-in-scripts"
> +WARN_QA ?= "ldflags useless-rpaths rpaths unsafe-references-in-binaries unsafe-references-in-scripts staticdev"
>  ERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch la2 pkgconfig la perms"
>  
>  def package_qa_clean_path(path,d):
> @@ -192,6 +192,24 @@ def package_qa_check_dev(path, name, d, elf, messages):
>          messages.append("non -dev/-dbg/-nativesdk package contains symlink .so: %s path '%s'" % \
>                   (name, package_qa_clean_path(path,d)))
>  
> +QAPATHTEST[staticdev] = "package_qa_check_staticdev"
> +
> +# These 2 packages contain archive libraries that need to be in -dev
> +STATICDEV_WHITELIST = "libgcc-dev libgcov-dev"
> +def package_qa_check_staticdev(path, name, d, elf, messages):
> +    """
> +    Check for ".a" library in non-staticdev packages, use a STATICDEV_WHITELIST
> +    for exceptions
> +    """
> +
> +    import re
> +    staticdev_whitelist = d.getVar('STATICDEV_WHITELIST', True)
> +    if (staticdev_whitelist.find(name) != -1):
> +        return
> +    if not name.endswith("-pic") and not name.endswith("-staticdev") and path.endswith(".a") and not path.endswith("_nonshared.a"):
> +        messages.append("non -staticdev package contains static .a library: %s path '%s'" % \
> +                 (name, package_qa_clean_path(path,d)))
> +
>  QAPATHTEST[debug-files] = "package_qa_check_dbg"
>  def package_qa_check_dbg(path, name, d, elf, messages):
>      """

Looks good but instead of adding STATICDEV_WHITELIST, could we set:

INSANE_SKIP_libgcc-dev = "staticdev"
INSANE_SKIP_libgcov-dev = "staticdev"

in the gcc recipe and use the existing code to handle that?

Cheers,

Richard




      reply	other threads:[~2012-01-25 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25  1:49 [PATCH 1/2] insane.bbclass: Add test for static .a libraries in non-staticdev packages Saul Wold
2012-01-25 15:44 ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1327506280.19643.255.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox