From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org,
Olivier Schonken <olivier.schonken@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/qpdf: bump to version 11.9.1
Date: Sat, 26 Oct 2024 15:01:16 +0200 [thread overview]
Message-ID: <20241026150116.691974d5@windsurf> (raw)
In-Reply-To: <20240930223133.1202389-1-james.hilliard1@gmail.com>
Hello James,
On Mon, 30 Sep 2024 16:31:30 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/qpdf/qpdf.hash | 4 ++--
> package/qpdf/qpdf.mk | 31 ++++++++++++++++++++++++-------
> 2 files changed, 26 insertions(+), 9 deletions(-)
Thanks for this patch. However, I am not sure this conversion to
cmake-package is really complete.
> -QPDF_CONF_OPTS = --with-random=/dev/urandom
> +QPDF_CONF_OPTS = \
> + -DBUILD_DOC=OFF \
This is already done by cmake-package.
> ifeq ($(BR2_USE_WCHAR),)
> QPDF_CONF_ENV += CXXFLAGS="$(TARGET_CXXFLAGS) -DQPDF_NO_WCHAR_T"
Are you sure this still has an effect with cmake-package?
> ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)
> QPDF_CONF_ENV += LIBS=-latomic
> endif
Same question (and I believe it doesn't have any effect).
Could you review qpdf.mk more thoroughly and check that what was done
for autotools-package is either removed if no longer needed, or
properly converted to have the same effect for cmake-package?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-26 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 22:31 [Buildroot] [PATCH 1/4] package/qpdf: bump to version 11.9.1 James Hilliard
2024-09-30 22:31 ` [Buildroot] [PATCH 2/4] package/libcupsfilters: new package James Hilliard
2024-10-01 20:16 ` Peter Korsgaard
2024-10-01 20:49 ` James Hilliard
2024-10-02 6:07 ` Peter Korsgaard
2024-10-02 6:11 ` James Hilliard
2024-10-26 13:16 ` Thomas Petazzoni via buildroot
2024-09-30 22:31 ` [Buildroot] [PATCH 3/4] package/libppd: " James Hilliard
2024-10-01 20:17 ` Peter Korsgaard
2024-09-30 22:31 ` [Buildroot] [PATCH 4/4] package/cups-filters: bump to version 2.0.1 James Hilliard
2024-10-26 13:01 ` Thomas Petazzoni via buildroot [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=20241026150116.691974d5@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=olivier.schonken@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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