Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Björn Stenberg" <bjst@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] ptest bugfix: Make all ptest files go into -ptest package
Date: Mon, 25 Mar 2013 16:18:04 +0000	[thread overview]
Message-ID: <1364228284.3097.58.camel@ted> (raw)
In-Reply-To: <1364222065-62444-1-git-send-email-bjst@enea.com>

On Mon, 2013-03-25 at 15:34 +0100, Björn Stenberg wrote:
> Move ${PN}-ptest to start of PACKAGES to ensure all ptest files are
> packaged in the -ptest package.
> 
> Add QA exclusions to insane.bbclass to ensure -ptest packages can contain
> any files they need.
> 
> Bugfix: Add subshells for 'type' command.
> 
> This patch fixes bug #4069.
> 
> Signed-off-by: Björn Stenberg <bjst@enea.com>
> ---
>  meta/classes/insane.bbclass |    6 +++---
>  meta/classes/ptest.bbclass  |   15 ++++-----------
>  2 files changed, 7 insertions(+), 14 deletions(-)
> 
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index 2f10688..5170580 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -216,7 +216,7 @@ def package_qa_check_dev(path, name, d, elf, messages):
>      Check for ".so" library symlinks in non-dev packages
>      """
>  
> -    if not name.endswith("-dev") and not name.endswith("-dbg") and not name.startswith("nativesdk-") and path.endswith(".so") and os.path.islink(path):
> +    if not name.endswith("-dev") and not name.endswith("-dbg") and not name.endswith("-ptest") and not name.startswith("nativesdk-") and path.endswith(".so") and os.path.islink(path):
>          messages.append("non -dev/-dbg/-nativesdk package contains symlink .so: %s path '%s'" % \
>                   (name, package_qa_clean_path(path,d)))
>  
> @@ -229,7 +229,7 @@ def package_qa_check_staticdev(path, name, d, elf, messages):
>      libgcc.a, libgcov.a will be skipped in their packages
>      """
>  
> -    if not name.endswith("-pic") and not name.endswith("-staticdev") and path.endswith(".a") and not path.endswith("_nonshared.a"):
> +    if not name.endswith("-pic") and not name.endswith("-staticdev") and not name.endswith("-ptest") 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)))
>  
> @@ -273,7 +273,7 @@ def package_qa_check_dbg(path, name, d, elf, messages):
>      Check for ".debug" files or directories outside of the dbg package
>      """
>  
> -    if not "-dbg" in name:
> +    if not "-dbg" in name and not "-ptest" in name:
>          if '.debug' in path.split(os.path.sep):
>              messages.append("non debug package contains .debug directory: %s path %s" % \
>                       (name, package_qa_clean_path(path,d)))
> diff --git a/meta/classes/ptest.bbclass b/meta/classes/ptest.bbclass
> index 6ab5ee4..c51c4e6 100644
> --- a/meta/classes/ptest.bbclass
> +++ b/meta/classes/ptest.bbclass
> @@ -14,18 +14,11 @@ PTEST_ENABLED = "${@base_contains("DISTRO_FEATURES", "ptest", "1", "0", d)}"
>  RDEPENDS_${PN}-ptest_virtclass-native = ""
>  RDEPENDS_${PN}-ptest_virtclass-nativesdk = ""
>  
> -PACKAGES += "${@base_contains('DISTRO_FEATURES', 'ptest', '${PN}-ptest', '', d)}"
> -
> -FILES_${PN}-dbg += "${PTEST_PATH}/.debug \
> -                    ${PTEST_PATH}/*/.debug \
> -                    ${PTEST_PATH}/*/*/.debug \
> -                    ${PTEST_PATH}/*/*/*/.debug \
> -                    ${PTEST_PATH}/*/*/*/*/.debug \
> -                   "

Why are we putting all the debug files into the -ptest package now? Does
that make sense?

Cheers,

Richard

> +PACKAGES =+ "${@base_contains('DISTRO_FEATURES', 'ptest', '${PN}-ptest', '', d)}"
>  
>  do_configure_ptest_base() {
>      if [ ${PTEST_ENABLED} = 1 ]; then
> -        if [ type -t do_configure_ptest = function ]; then
> +        if [ $(type -t do_configure_ptest) = function ]; then
>              do_configure_ptest
>          fi
>      fi
> @@ -33,7 +26,7 @@ do_configure_ptest_base() {
>  
>  do_compile_ptest_base() {
>      if [ ${PTEST_ENABLED} = 1 ]; then
> -        if [ type -t do_compile_ptest = function ]; then
> +        if [ $(type -t do_compile_ptest) = function ]; then
>              do_compile_ptest
>          fi
>      fi
> @@ -46,7 +39,7 @@ do_install_ptest_base() {
>              if grep -q install-ptest: Makefile; then
>                  oe_runmake DESTDIR=${D}${PTEST_PATH} install-ptest
>              fi
> -            if [ type -t do_install_ptest = function ]; then
> +            if [ $(type -t do_install_ptest) = function ]; then
>                  do_install_ptest
>              fi
>          fi





  reply	other threads:[~2013-03-25 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  8:30 Problems with ptest and package splitting Björn Stenberg
2013-03-21 15:23 ` [PATCH] ptest bugfix: Make all ptest files go into -ptest package Björn Stenberg
2013-03-22 14:12   ` Björn Stenberg
2013-03-25 14:34     ` [PATCH v2] " Björn Stenberg
2013-03-25 16:18       ` Richard Purdie [this message]
2013-04-08  8:41         ` Björn Stenberg
2013-04-04  6:40 ` [PATCH v3] ptest bug fixes Björn Stenberg
2013-04-10 13:34 ` [PATCH v4] " Björn Stenberg

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=1364228284.3097.58.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bjst@enea.com \
    --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