From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] siteinfo.bbclass re-merge
Date: Wed, 13 Jul 2011 14:42:06 -0500 [thread overview]
Message-ID: <4E1DF50E.7080305@windriver.com> (raw)
In-Reply-To: <cover.1310583666.git.tom_rini@mentor.com>
On 7/13/11 2:05 PM, Tom Rini wrote:
> Hey all,
>
> This is the second of two pull requests. This doesn't depend on the first
> request, it's just splitting changes up. There's three changes here. First,
> site/ix86-common was setting the wrong value for unsigned int. Second,
> change perl to use SITEINFO variables rather than functions. Third, bring
> in the various changes in siteinfo.bbclass that have been in oe.dev. This
> last part will, I hope, also make dealing with multilib-specific siteinfo
> stuff easier (also alternative ABIs like x32).
Note, this is NOT an objection to the changes. However, one thing to keep in mind.
(In fact I like the changes being suggested)
We have a dynamic site-configuation mechanism already in place. So it's
important that we don't duplicate things within the site/* files.
Currently the recipes: glibc, zlib, eglibc, and uclibc contain dynamic
site_config files. (See ./recipes-core/glibc/site_config/* for an example)
The output of these files get placed into a target arch specific site config
directory: ${STAGING_DATADIR}/${TARGET_SYS}_config_site.d
These are automatically loaded as well as the predefined "common" items. By
using the dynamically generated versions we can change the configuration options
for glibc, uclibc, etc and the site config will automatically get updated based
on the existing checks.
So instead of updating the various site/* files, if the value can be discovered
-- or is defined by a given package.. we should be using the dynamic method as
it'll be safer over the long-haul. Someone might need to go over the existing
ones and see if there is anything that falls under this.
BTW, I did notice that ncurses is supposed to have a dynamic site_config, but it
somehow got checked into the wrong location. I'll submit a pull request for
that shortly.
--Mark
> My next step is to work on merging and verifying as much as possible
> the site files in oe-core and oe.dev.
>
> The following changes since commit e66c2999afa2b3efbce8bb46c89f9db5e15f35c7:
> Saul Wold (1):
> libx11: ensure nativesdk uses correct DEPENDS and XCB flags
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib trini/update-siteinfo
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/update-siteinfo
>
> Tom Rini (3):
> site/ix86-common: Fix ac_cv_sizeof_unsigned_char definition
> perl: Use SITEINFO variables not functions
> siteinfo.bbclass: Port over oe.dev logic for site files
>
> meta/classes/autotools.bbclass | 2 +-
> meta/classes/siteinfo.bbclass | 202 +++++++++++++---------------
> meta/classes/toolchain-scripts.bbclass | 2 +-
> meta/recipes-core/meta/meta-environment.bb | 2 +-
> meta/recipes-core/meta/meta-toolchain.bb | 2 +-
> meta/recipes-devtools/perl/perl_5.12.3.bb | 4 +-
> meta/site/ix86-common | 2 +-
> 7 files changed, 103 insertions(+), 113 deletions(-)
> create mode 100644 meta/site/common-linux
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-07-13 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 19:05 [PATCH 0/3] siteinfo.bbclass re-merge Tom Rini
2011-07-13 19:06 ` [PATCH 1/3] site/ix86-common: Fix ac_cv_sizeof_unsigned_char definition Tom Rini
2011-07-13 19:06 ` [PATCH 2/3] perl: Use SITEINFO variables not functions Tom Rini
2011-07-13 19:06 ` [PATCH 3/3] siteinfo.bbclass: Port over oe.dev logic for site files Tom Rini
2011-07-20 15:07 ` Richard Purdie
2011-07-13 19:42 ` Mark Hatle [this message]
2011-07-13 20:40 ` [PATCH 0/3] siteinfo.bbclass re-merge Tom Rini
2011-07-14 14:42 ` Richard Purdie
2011-07-14 16:58 ` Tom Rini
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=4E1DF50E.7080305@windriver.com \
--to=mark.hatle@windriver.com \
--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