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_build: Unify directory layout for native and target builds
Date: Thu, 18 Oct 2012 12:51:43 -0700	[thread overview]
Message-ID: <50805DCF.3060104@linux.intel.com> (raw)
In-Reply-To: <1348608781.1335.9.camel@x121e.pbcl.net>

On 09/25/2012 02:33 PM, Phil Blundell wrote:
> There seems to be no benefit in having them be different and this
> appears to cause a certain amount of confusion about paths for
> the native modules.
>
> Signed-off-by: Phil Blundell <pb@pbcl.net>
> ---
> previously posted as RFC, no comments so reposting as an actual patch
>
>   meta/classes/cpan_build.bbclass |    7 ++-----
>   1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/meta/classes/cpan_build.bbclass
> b/meta/classes/cpan_build.bbclass
> index 36ffc56..0809602 100644
> --- a/meta/classes/cpan_build.bbclass
> +++ b/meta/classes/cpan_build.bbclass
> @@ -23,8 +23,9 @@ cpan_build_do_configure () {
>   	if [ ${@is_target(d)} == "yes" ]; then
>   		# build for target
>   		. ${STAGING_LIBDIR}/perl/config.sh
> +	fi
>
> -			perl Build.PL --installdirs vendor \
> +	perl Build.PL --installdirs vendor \
>   				--destdir ${D} \
>   				--install_path lib="${datadir}/perl" \
>   				--install_path arch="${libdir}/perl" \
> @@ -32,10 +33,6 @@ cpan_build_do_configure () {
>   				--install_path bin=${bindir} \
>   				--install_path bindoc=${mandir}/man1 \
>   				--install_path libdoc=${mandir}/man3
> -	else
> -		# build for host
> -		perl Build.PL --installdirs site --destdir ${D}
> -	fi
>   }
>
>   cpan_build_do_compile () {
>

Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2012-10-18 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 21:33 [PATCH] cpan_build: Unify directory layout for native and target builds Phil Blundell
2012-10-18 19:51 ` 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=50805DCF.3060104@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