From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libproxy: utilize base_libdir when configured
Date: Wed, 03 Aug 2011 10:46:19 -0700 [thread overview]
Message-ID: <4E39896B.1000102@linux.intel.com> (raw)
In-Reply-To: <1312385196-14664-1-git-send-email-galak@kernel.crashing.org>
On 08/03/2011 08:26 AM, Kumar Gala wrote:
> Pass $base_libdir through when we configure to support a location other
> than /lib.
>
> Signed-off-by: Kumar Gala<galak@kernel.crashing.org>
> ---
> meta/recipes-support/libproxy/libproxy_0.4.6.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-support/libproxy/libproxy_0.4.6.bb b/meta/recipes-support/libproxy/libproxy_0.4.6.bb
> index b24e8ba..8d9a332 100644
> --- a/meta/recipes-support/libproxy/libproxy_0.4.6.bb
> +++ b/meta/recipes-support/libproxy/libproxy_0.4.6.bb
> @@ -14,12 +14,12 @@ SRC_URI = "http://libproxy.googlecode.com/files/libproxy-${PV}.tar.gz"
> SRC_URI[md5sum] = "199c6b120baf1f7258a55f38d5ec74f5"
> SRC_URI[sha256sum] = "9ad912e63b1efca98fb442240a2bc7302e6021c1d0b1b9363327729f29462f30"
>
> -PR = "r1"
> +PR = "r2"
>
> inherit cmake pkgconfig
>
> EXTRA_OECMAKE = "-DWITH_WEBKIT=no -DWITH_GNOME=yes -DWITH_KDE4=no \
> - -DWITH_PYTHON=no -DWITH_PERL=no -DWITH_MOZJS=no -DWITH_NM=no"
> + -DWITH_PYTHON=no -DWITH_PERL=no -DWITH_MOZJS=no -DWITH_NM=no -DLIB_INSTALL_DIR=${base_libdir}"
Should this be ${base_libdir} as in /lib* or ${libdir} as in /usr/lib*?
I think libproxy should be installed to the ${libdir}
>
> FILES_${PN}-dbg += "${libdir}/libproxy/${PV}/plugins/.debug/ ${libdir}/libproxy/${PV}/modules/.debug/"
>
prev parent reply other threads:[~2011-08-03 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 15:26 [PATCH] libproxy: utilize base_libdir when configured Kumar Gala
2011-08-03 17:46 ` Saul Wold [this message]
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=4E39896B.1000102@linux.intel.com \
--to=sgw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.