Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 4/4] Renamed prefix_native, bindir_native, etc using 	hyphens
Date: Thu, 18 Mar 2010 10:38:56 +0000	[thread overview]
Message-ID: <1268908736.14566.1422.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <ac9c93b11003180018u761e78f6l67b3f76869a95612@mail.gmail.com>

On Thu, 2010-03-18 at 08:18 +0100, Frans Meulenbroeks wrote:
> 2010/3/18 Douglas Royds <douglas.royds@tait.co.nz>:
> >   - Avoids clashing with the machine override when MACHINE=native
> >   - bindir_cross similarly renamed for consistency
> >
> [...]
> >
> >  # Path prefixes
> >  base_prefix = "${STAGING_DIR_NATIVE}"
> > -prefix = "${STAGING_DIR_NATIVE}${prefix_native}"
> > -exec_prefix = "${STAGING_DIR_NATIVE}${prefix_native}"
> > +prefix = "${STAGING_DIR_NATIVE}${prefix-native}"
> > +exec_prefix = "${STAGING_DIR_NATIVE}${prefix-native}"
> 
> [...]
> 
> Shouldn't we then for consistent naming also go to exex-prefix etc ?

That would need to be done carefully since ${exec_prefix} is exported.
I am not sure it would be worth the effort to get it right at the
moment.  This would probably be better done as a part of a larger effort
to tidy up the semantics of the bitbake variable namespace.

p.





  reply	other threads:[~2010-03-18 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  4:56 [PATCH 4/4] Renamed prefix_native, bindir_native, etc using hyphens Douglas Royds
2010-03-18  7:18 ` Frans Meulenbroeks
2010-03-18 10:38   ` Phil Blundell [this message]
2010-03-18 20:48   ` Douglas Royds
2010-03-18 21:13     ` Richard Purdie

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=1268908736.14566.1422.camel@mill.internal.reciva.com \
    --to=philb@gnu.org \
    --cc=openembedded-devel@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