From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH
Date: Fri, 22 Jul 2011 16:11:36 +0100 [thread overview]
Message-ID: <1311347496.2344.144.camel@rex> (raw)
In-Reply-To: <29D487E1-5E59-4A53-B518-3692FF11C70C@dominion.thruhere.net>
On Fri, 2011-07-22 at 16:54 +0200, Koen Kooi wrote:
> Op 22 jul. 2011, om 16:49 heeft Richard Purdie het volgende geschreven:
>
> > Since we're updating the tune file format, it makes sense to abstract
> > the compiler tune arguments at this point too. This means that should
> > these need to be overridden at any point, the original values can
> > still be obtained in a similar manner to the other TUNE* variables.
> >
> > Whilst this isn't strictly necessary for any current need, its likely
> > good practise to standardise this behaviour.
>
> So if I'm reading the patch correctly this doesn't result in a
> behaviour change, it just shuffles the definitions around in
> preparation for Mark's tune overhaul.
Yes.
I'm trying to split the work Mark and I have done into logical chunks we
can review and these are the pieces to setup the externally facing
variables we need.
I've not yet finished the patches which change the tune files themselves
but we have a pretty good idea of what the finished result needs to look
like to get all this working which we have experimented and tested with.
Cheers,
Richard
next prev parent reply other threads:[~2011-07-22 15:15 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
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 [this message]
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=1311347496.2344.144.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