Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cpan-base: Add more debug paths to FILES
Date: Tue, 23 Oct 2012 12:02:19 -0700	[thread overview]
Message-ID: <5086E9BB.5080005@linux.intel.com> (raw)
In-Reply-To: <1350598767.4470.179.camel@x121e.pbcl.net>

On 10/18/2012 03:19 PM, Phil Blundell wrote:
> We seem to be mostly installing modules into vendor_perl nowadays.
> Make sure that the .debug data from there is captured appropriately.
>
> Also, expand ${PERLLIBDIRS} at the point of assignment so we don't
> call the python again and again.
>
> Signed-off-by: Phil Blundell <pb@pbcl.net>
> ---
>   meta/classes/cpan-base.bbclass |    9 +++++++--
>   1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/cpan-base.bbclass b/meta/classes/cpan-base.bbclass
> index 660c15f..cf697f1 100644
> --- a/meta/classes/cpan-base.bbclass
> +++ b/meta/classes/cpan-base.bbclass
> @@ -39,8 +39,13 @@ def is_target(d):
>           return "yes"
>       return "no"
>
> -PERLLIBDIRS = "${@perl_get_libdirs(d)}"
> +PERLLIBDIRS := "${@perl_get_libdirs(d)}"
> +PERLVERSION := "${@get_perl_version(d)}"
>
>   FILES_${PN}-dbg += "${PERLLIBDIRS}/auto/*/.debug \
>                       ${PERLLIBDIRS}/auto/*/*/.debug \
> -                    ${PERLLIBDIRS}/auto/*/*/*/.debug"
> +                    ${PERLLIBDIRS}/auto/*/*/*/.debug \
> +		    ${PERLLIBDIRS}/vendor_perl/${PERLVERSION}/auto/*/.debug \
> +		    ${PERLLIBDIRS}/vendor_perl/${PERLVERSION}/auto/*/*/.debug \
> +		    ${PERLLIBDIRS}/vendor_perl/${PERLVERSION}/auto/*/*/*/.debug \
> +		    "
>
Merged into OE-Core (with whitespaces fixed)

Thanks
	Sau!




      parent reply	other threads:[~2012-10-23 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 22:19 [PATCH] cpan-base: Add more debug paths to FILES Phil Blundell
2012-10-18 22:28 ` Martin Jansa
2012-10-23 19:02 ` Saul Wold [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=5086E9BB.5080005@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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