[OE-core] [PATCH] libffi: Copy headers to more common include path.
Arslan, Fahad
Fahad_Arslan at mentor.com
Fri Dec 13 11:49:44 UTC 2013
My understanding was that headers should be placed under ${includedir} instead of
${libdir}. Isn't it the practice or am I missing something?
Thanks,
Fahad
________________________________________
From: Richard Purdie [richard.purdie at linuxfoundation.org]
Sent: Thursday, December 12, 2013 10:57 PM
To: Arslan, Fahad
Cc: openembedded-core at lists.openembedded.org
Subject: Re: [OE-core] [PATCH] libffi: Copy headers to more common include path.
On Thu, 2013-12-12 at 22:47 +0500, Fahad Arslan wrote:
> Signed-off-by: Fahad Arslan <fahad_arslan at 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?
Cheers,
Richard
More information about the Openembedded-core
mailing list