From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] glib-2.0: use the system libpcre
Date: Fri, 05 Feb 2016 13:32:52 +0000 [thread overview]
Message-ID: <1454679172.3210.10.camel@linux.intel.com> (raw)
In-Reply-To: <1454672856-13680-3-git-send-email-ross.burton@intel.com>
On Fri, 2016-02-05 at 11:47 +0000, Ross Burton wrote:
> Instead of using the internal copy of libpcre, use one that we
> build. Note that
> this requires libpcre enables Unicode properties.
We could do with a convention for documenting this kind of trap (where
a PACKAGECONFIG in foo requires one in bar).
Maybe you could a comment here in this case?
Regards,
Joshua
>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
> ---
> meta/recipes-core/glib-2.0/glib.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-core/glib-2.0/glib.inc b/meta/recipes-
> core/glib-2.0/glib.inc
> index dc88d19..7a6a4ce 100644
> --- a/meta/recipes-core/glib-2.0/glib.inc
> +++ b/meta/recipes-core/glib-2.0/glib.inc
> @@ -31,6 +31,9 @@ inherit autotools gettext gtk-doc pkgconfig ptest-
> gnome upstream-version-is-even
>
> S = "${WORKDIR}/glib-${PV}"
>
> +PACKAGECONFIG ??= "system-pcre"
> +PACKAGECONFIG[system-pcre] = "--with-pcre=system,--with-
> pcre=internal,libpcre"
> +
> CORECONF = "--disable-dtrace --disable-fam --disable-libelf --
> disable-systemtap --disable-man"
>
> PRINTF = "--enable-included-printf=no"
> --
> 2.7.0
>
next prev parent reply other threads:[~2016-02-05 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 11:47 [PATCH 1/3] python3: remove optimize by default patch Ross Burton
2016-02-05 11:47 ` [PATCH 2/3] libpcre: enable unicode properties by default Ross Burton
2016-02-05 11:47 ` [PATCH 3/3] glib-2.0: use the system libpcre Ross Burton
2016-02-05 13:32 ` Joshua G Lock [this message]
2016-02-05 14:35 ` 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=1454679172.3210.10.camel@linux.intel.com \
--to=joshua.g.lock@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.