Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Cc: <tim.hammer@nav-timing.safrangroup.com>,
	<nicolas.carrier@nav-timing.safrangroup.com>,
	<buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/4] package/libxmlsec1: Add libxmlsec1 used by openSCAP
Date: Wed, 30 Jul 2025 19:18:59 +0200	[thread overview]
Message-ID: <DBPK7ZI4PYVW.WNI5DTRPIL69@bootlin.com> (raw)
In-Reply-To: <20250730185358.61d2f04c@windsurf>

Hi Thomas,

thanks for the review !
On Wed Jul 30, 2025 at 6:53 PM CEST, Thomas Petazzoni via buildroot wrote:
> Hello Alexis,
>> +LIBXMLSEC1_CONF_OPTS =	--disable-static \
>> +			--enable-crypto-dl=no \
>> +			--with-openssl \
>> +			--with-gnutls=no \
>> +			--with-gcrypt=no \
>> +			--with-nss=no
>
> This should be a bit more nicely formatted, and use --disable/--without
> instead of --enable-..=no and --with-...=no. Also, you shouldn't pass
> --disable-static unless you have a very good reason to. Indeed,
> Buildroot is passing --{enable,disable}-{shared,static} automatically
> based on the BR2_SHARED_LIBS/BR2_STATIC_LIBS settings.
>
> So:
>
> LIBXMLSEC1_CONF_OPTS = \
> 	--disable-crypto-dl \
> 	--with-openssl \
> 	--without-gnutls \
> 	--without-gcrypt \
> 	--without-nss

Yes, I must confess that I did not thoroughly reviewed those conf opts
before including them. I'll give a try without the static, remove it if not
needed, and use proper BR mechanisms if it is actually needed.

[...]

>> +HOST_LIBXMLSEC1_CONF_OPTS = $(LIBXMLSEC1_CONF_OPTS)
>
> I'm not sure I like re-using like this target options for the host
> variant. I think I'd prefer them to be duplicated.

You right, and this pattern actually bit me in one of the other packages
brought in this series !

Alexis


-- 
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-07-30 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 12:47 [Buildroot] [PATCH 0/4] package/compliance-as-code: introduce new package Alexis Lothoré via buildroot
2025-07-30 12:47 ` [Buildroot] [PATCH 1/4] package/libxmlsec1: Add libxmlsec1 used by openSCAP Alexis Lothoré via buildroot
2025-07-30 16:53   ` Thomas Petazzoni via buildroot
2025-07-30 17:18     ` Alexis Lothoré via buildroot [this message]
2025-07-30 12:47 ` [Buildroot] [PATCH 2/4] package/libcurl: Reapply "libcurl: add host variant" Alexis Lothoré via buildroot
2025-07-30 16:55   ` Thomas Petazzoni via buildroot
2025-07-30 12:47 ` [Buildroot] [PATCH 3/4] package/openscap: add openscap package Alexis Lothoré via buildroot
2025-07-30 17:02   ` Thomas Petazzoni via buildroot
2025-07-31 12:34     ` Alexis Lothoré via buildroot
2025-07-31 12:48       ` Thomas Petazzoni via buildroot
2025-07-31 13:14         ` Alexis Lothoré via buildroot
2025-07-31 14:39           ` Thomas Petazzoni via buildroot
2025-07-30 12:47 ` [Buildroot] [PATCH 4/4] package/compliance-as-code: add new package Alexis Lothoré via buildroot
2025-07-30 17:18   ` Thomas Petazzoni via buildroot
2025-07-30 18:09     ` Alexis Lothoré via buildroot
2025-07-30 19:29       ` Thomas Petazzoni via buildroot

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=DBPK7ZI4PYVW.WNI5DTRPIL69@bootlin.com \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --cc=nicolas.carrier@nav-timing.safrangroup.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tim.hammer@nav-timing.safrangroup.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