From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/pugixml: add support for a limited set of configuration options
Date: Wed, 30 Jan 2019 21:34:51 +0100 [thread overview]
Message-ID: <20190130213451.6c45821d@windsurf> (raw)
In-Reply-To: <20190130201416.9078-1-patrickdepinguin@gmail.com>
Hello,
Quick comments, not a full review.
On Wed, 30 Jan 2019 21:14:16 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> +config BR2_PACKAGE_PUGIXML_NO_XPATH_SUPPORT
> + bool "Disable XPath support"
> + help
> + Disables XPath support in pugixml. Both XPath interfaces and
> + XPath implementation are excluded from compilation. This
> + option is provided in case you do not need XPath functionality
> + and need to save code space.
> +
> +config BR2_PACKAGE_PUGIXML_NO_STL_SUPPORT
> + bool "Disable STL support"
> + help
> + Disables use of STL in pugixml. The functions that operate on
> + STL types are no longer present (i.e. load/save via iostream)
> + if this macro is defined. This option is provided in case
> + your target platform does not have a standard-compliant STL
> + implementation.
> +
> +config BR2_PACKAGE_PUGIXML_NO_EXCEPTIONS
> + bool "Disable exceptions"
> + help
> + Disables use of exceptions in pugixml. This option is provided
> + in case your target platform does not have exception handling
> + capabilities.
These options that you enable to disable something are backwards. Could
you turn them over to actual enabling options, with "default y" if you
want to keep backward compatibility.
> +config BR2_PACKAGE_PUGIXML_HEADER_ONLY
> + bool "Enable header-only version"
> + help
> + All source code for pugixml will be included in every
> + translation unit that includes pugixml.hpp. This is how most
> + of Boost and STL libraries work.
> +
> + http://pugixml.org/docs/manual.html#install.building.header
> +
> +config BR2_PACKAGE_PUGIXML_HAS_LONG_LONG
"HAS_LONG_LONG" doesn't read like an enabling option, but like "does
this package has long long".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-30 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:14 [Buildroot] [PATCH 1/1] package/pugixml: add support for a limited set of configuration options Thomas De Schampheleire
2019-01-30 20:34 ` Thomas Petazzoni [this message]
2019-01-31 7:38 ` Thomas De Schampheleire
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=20190130213451.6c45821d@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