From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libffi: Copy headers to more common include path.
Date: Thu, 12 Dec 2013 12:04:48 -0600 [thread overview]
Message-ID: <52A9FAC0.4030606@windriver.com> (raw)
In-Reply-To: <1386871038.504.19.camel@ted>
On 12/12/13, 11:57 AM, Richard Purdie wrote:
> On Thu, 2013-12-12 at 22:47 +0500, Fahad Arslan wrote:
>> Signed-off-by: Fahad Arslan <fahad_arslan@mentor.com>
>> ---
>> meta/recipes-gnome/libffi/libffi_3.0.13.bb | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/meta/recipes-gnome/libffi/libffi_3.0.13.bb b/meta/recipes-gnome/libffi/libffi_3.0.13.bb
>> index db0841e..07dd7d1 100644
>> --- a/meta/recipes-gnome/libffi/libffi_3.0.13.bb
>> +++ b/meta/recipes-gnome/libffi/libffi_3.0.13.bb
>> @@ -22,3 +22,8 @@ inherit autotools
>> FILES_${PN}-dev += "${libdir}/libffi-${PV}"
>>
>> BBCLASSEXTEND = "native nativesdk"
>> +
>> +do_install_append() {
>> + install -d ${D}${includedir}
>> + cp -r ${D}${libdir}/libffi-${PV}/include/* ${D}${includedir}/ || true
>> +}
>
> Why? Shouldn't whatever is using them look for them in the correct
> location?
Correct, I think this is wrong as well. Most of the time when versions are
included into the include path, the system may allow for multiple versions to be
installed and used at the same time.
--Mark
> Cheers,
>
> Richard
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-12-12 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 17:47 [PATCH] libffi: Copy headers to more common include path Fahad Arslan
2013-12-12 17:57 ` Richard Purdie
2013-12-12 18:04 ` Mark Hatle [this message]
2013-12-13 11:49 ` Arslan, Fahad
2013-12-13 12:09 ` Burton, Ross
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=52A9FAC0.4030606@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