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 2/3] conf/machine/tune: Overhaul tune include file variables
Date: Fri, 22 Jul 2011 16:13:07 +0100	[thread overview]
Message-ID: <1311347587.2344.146.camel@rex> (raw)
In-Reply-To: <6FB5127C-35E2-42F7-9763-65BF73085B1E@kernel.crashing.org>

On Fri, 2011-07-22 at 10:03 -0500, Kumar Gala wrote:
> On Jul 22, 2011, at 9:49 AM, Richard Purdie wrote:
> 
> > There is currently consideradble confusion over how the tune files operate
> > and how these interact with the rest of the build system. This update/overhaul
> > changes things so the tune files are primarily resonsible for setting:
> > 
> > TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that
> > represents the architecture we're targetting.
> > 
> > TUNE_PKGARCH - The value that represents the tune confuration that this set
> > of tune parameters results in.
> > 
> > This allows the significant improvement that the core can now always determine
> > the target architecture value, even when TARGET_ARCH needs to be reset to
> > something different and likewise, there is one package architecture variable
> > the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH
> > and FEED_ARCH variables.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> 
> Can you give an example of how this will work for multilib?

These are setting the scene for multilib, it doesn't directly enable it.
For an example of the end result see this branch:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/oe-core/ml

but this isn't in a form suitable for submission yet which is what I'm
working towards.

Cheers,

Richard








  reply	other threads:[~2011-07-22 15:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 14:49 [PATCH 0/3] First round of tune config file updates Richard Purdie
2011-07-22 14:49 ` [PATCH 1/3] bitbake.conf/cross.bbclass: Add ability to dynamically change library location Richard Purdie
2011-07-22 14:49 ` [PATCH 2/3] conf/machine/tune: Overhaul tune include file variables Richard Purdie
2011-07-22 15:03   ` Kumar Gala
2011-07-22 15:13     ` Richard Purdie [this message]
2011-07-22 14:49 ` [PATCH 3/3] conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH Richard Purdie
2011-07-22 14:54   ` Koen Kooi
2011-07-22 15:11     ` Richard Purdie
2011-07-22 15:15       ` Koen Kooi
2011-07-22 18:00 ` [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features Richard Purdie
2011-07-22 18:14   ` Tom Rini
2011-07-25 18:55     ` Mark Hatle
2011-07-25 19:34       ` Tom Rini
2011-07-25 19:39         ` Mark Hatle
2011-07-25 20:39         ` Phil Blundell
2011-07-25 20:43           ` Tom Rini
2011-07-22 18:00 ` [PATCH 4/3] bitbake.conf/classes: Variable cleanup Richard Purdie
2011-07-22 18:01 ` [PATCH 6/3] Move architecture specific TARGET_OS mangling into tune files Richard Purdie
2011-07-25 13:42   ` Richard Purdie
2011-07-25 16:23     ` Phil Blundell
2011-07-27 16:37       ` 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=1311347587.2344.146.camel@rex \
    --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