From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] package/pugixml: enable install of pugixml.pc
Date: Mon, 17 Jun 2019 12:51:06 +0200 [thread overview]
Message-ID: <20190617125106.67d8ccf1@windsurf> (raw)
In-Reply-To: <20190616201621.23912-2-bernd.kuhls@t-online.de>
On Sun, 16 Jun 2019 22:16:20 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Needed for waylandpp >= 0.2.4 to detect pugixml:
> https://github.com/NilsBrause/waylandpp/commit/0a61175003a0a34038e39092918768360d2dd1da#diff-af3b638bc2a3e6c650974192a53c7291R39
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v3: no changes
> v2: changed variables for HOST_PUGIXML_CONF_OPTS (Thomas)
>
> package/pugixml/pugixml.mk | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/package/pugixml/pugixml.mk b/package/pugixml/pugixml.mk
> index 6f214c4de8..368f958920 100644
> --- a/package/pugixml/pugixml.mk
> +++ b/package/pugixml/pugixml.mk
> @@ -15,6 +15,7 @@ PUGIXML_INSTALL_STAGING = YES
> # force-enable this option to support older gcc versions. See also:
> # https://gcc.gnu.org/onlinedocs/gcc/Long-Long.html
> PUGIXML_BUILD_DEFINES += PUGIXML_HAS_LONG_LONG
> +HOST_PUGIXML_BUILD_DEFINES += PUGIXML_HAS_LONG_LONG
How is this related to install the .pc file ? Shouldn't this go in PATCH 1/3 ?
>
> ifeq ($(BR2_PACKAGE_PUGIXML_XPATH_SUPPORT),)
> PUGIXML_BUILD_DEFINES += PUGIXML_NO_XPATH
> @@ -30,5 +31,9 @@ ifdef PUGIXML_BUILD_DEFINES
> PUGIXML_CONF_OPTS += -DBUILD_DEFINES="$(subst $(space),;,$(PUGIXML_BUILD_DEFINES))"
> endif
>
> +HOST_PUGIXML_CONF_OPTS += \
> + -DBUILD_PKGCONFIG=ON \
I understand why this is in this patch.
> + -DBUILD_DEFINES="$(subst $(space),;,$(HOST_PUGIXML_BUILD_DEFINES))"
But this should be in PATCH 1/3, no ?
In fact, is it really useful to split PATCH 1/3 and 2/3 ? Both are just
about enabling the host variant of pugixml, we don't really need to
separate the installation of the .pc file in another patch.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-17 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 20:16 [Buildroot] [PATCH v3 1/3] package/pugixml: Enable host build Bernd Kuhls
2019-06-16 20:16 ` [Buildroot] [PATCH v3 2/3] package/pugixml: enable install of pugixml.pc Bernd Kuhls
2019-06-17 10:51 ` Thomas Petazzoni [this message]
2019-06-16 20:16 ` [Buildroot] [PATCH v3 3/3] package/waylandpp: bump version Bernd Kuhls
2019-06-17 18:25 ` Thomas Petazzoni
2019-06-17 18:24 ` [Buildroot] [PATCH v3 1/3] package/pugixml: Enable host build Thomas Petazzoni
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=20190617125106.67d8ccf1@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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