Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] multilib_header.bbclass: Add oe_multilib_header wrapper
Date: Mon, 25 Jul 2011 15:35:58 +0100	[thread overview]
Message-ID: <1311604560.30326.234.camel@phil-desktop> (raw)
In-Reply-To: <bd2e16888f6520e2d02d3ff6c43b360d217572e4.1311601422.git.richard.purdie@linuxfoundation.org>

On Mon, 2011-07-25 at 14:47 +0100, Richard Purdie wrote:
> +oe_multilib_header() {
> +	for each_header in "$@" ; do
> +	   if [ ! -f "${D}/${includedir}/$each_header" ]; then
> +	      bberror "oe_multilib_header: Unable to find header $each_header."
> +	      continue
> +	   fi
> +	   stem=$(echo $each_header | sed 's#\.h$##')
> +	   mv ${D}/${includedir}/$each_header ${D}/${includedir}/${stem}-${SITEINFO_BITS}.h
> +
> +	   sed -e "s#ENTER_HEADER_FILENAME_HERE#${stem}#g" ${COREBASE}/scripts/multilib_header_wrapper.h > ${D}/${includedir}/$each_header
> +	done
> +}

I guess it would also be nice if this was conditionalized in some way so
that it only triggered if one was trying to do a multilib build (or, at
least, had a TARGET_ARCH which supported multiple different wordsizes).
I don't especially want to have all the headers on, say, arm wrapped in
wordsize conditionals since the word size is basically invariant there.

po.





  parent reply	other threads:[~2011-07-25 14:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 13:47 [PATCH 0/5] Various multilib related fixes Richard Purdie
2011-07-25 13:47 ` [PATCH 1/5] multilib_header.bbclass: Add oe_multilib_header wrapper Richard Purdie
2011-07-25 13:54   ` Phil Blundell
2011-07-25 17:11     ` Mark Hatle
2011-07-25 20:06       ` Phil Blundell
2011-07-26 15:25       ` Mark Hatle
2011-07-25 14:35   ` Phil Blundell [this message]
2011-07-25 13:47 ` [PATCH 2/5] Fix recipe multilib header conflicts Richard Purdie
2011-07-25 14:08   ` Phil Blundell
2011-07-25 19:11     ` Mark Hatle
2011-07-25 13:47 ` [PATCH 3/5] eglibc: Update 2.13 to avoid multilib conflicts Richard Purdie
2011-07-25 13:59   ` Phil Blundell
2011-07-25 19:04     ` Mark Hatle
2011-07-25 20:04       ` Phil Blundell
2011-07-25 13:47 ` [PATCH 4/5] ncurses: Uncompress man pages Richard Purdie
2011-07-25 14:13   ` Phil Blundell
2011-07-25 19:14     ` Mark Hatle
2011-07-25 14:42   ` Enrico Scholz
2011-07-25 15:28     ` Phil Blundell
2011-07-25 13:47 ` [PATCH 5/5] package.bbclass: fixup_perms - symlink bug fix Richard Purdie
2011-07-25 14:05   ` Phil Blundell
2011-07-25 14:14     ` Enrico Scholz
2011-07-25 14:15       ` Phil Blundell
2011-07-25 19:08     ` Mark Hatle
2011-07-25 19:42       ` Phil Blundell

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=1311604560.30326.234.camel@phil-desktop \
    --to=philb@gnu.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