From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: TIAN Yuanhao <tianyuanhao3@163.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 4/6] package/libsolv: new package
Date: Tue, 7 Feb 2023 17:14:01 +0100 [thread overview]
Message-ID: <20230207171401.54d75d16@windsurf> (raw)
In-Reply-To: <20221128123418.2197-4-tianyuanhao3@163.com>
Hello,
On Mon, 28 Nov 2022 12:34:16 +0000
TIAN Yuanhao <tianyuanhao3@163.com> wrote:
> +ifeq ($(BR2_STATIC_LIBS),y)
> +LIBSOLV_CONF_OPTS += -DDISABLE_SHARED=ON
> +else ifeq ($(BR2_SHARED_STATIC_LIBS),y)
> +LIBSOLV_CONF_OPTS += -DENABLE_STATIC=ON
> +endif
Changed to:
ifeq ($(BR2_STATIC_LIBS)$(BR2_SHARED_STATIC_LIBS),y)
LIBSOLV_CONF_OPTS += -DENABLE_STATIC=ON
else
LIBSOLV_CONF_OPTS += -DDISABLE_STATIC=ON
endif
ifeq ($(BR2_SHARED_LIBS)$(BR2_SHARED_STATIC_LIBS),y)
LIBSOLV_CONF_OPTS += -DENABLE_SHARED=ON
else
LIBSOLV_CONF_OPTS += -DDISABLE_SHARED=ON
endif
To explicitly handle all cases.
> +ifeq ($(BR2_PACKAGE_MICROMAMBA),y)
> +LIBSOLV_CONF_OPTS += -DENABLE_CONDA=ON
> +endif
This isn't really nice, as we generally don't want packages to look at
their reverse dependencies to decide which features should be enabled
or not.
So here, I would prefer to have a BR2_PACKAGE_LIBSOLV_CONDA option,
which the micromamba package can select if it needs this feature from
libsolv. For now, I've dropped this part, so if we need it for
micromamba, could you send a patch just adding this new option,
together with the new iteration of the micromamba package?
Best regards,
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
next prev parent reply other threads:[~2023-02-07 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:34 [Buildroot] [PATCH/next 1/6] package/cli11: new package TIAN Yuanhao
2022-11-28 12:34 ` [Buildroot] [PATCH/next 2/6] package/termcolor: " TIAN Yuanhao
2023-02-07 16:04 ` Thomas Petazzoni via buildroot
2022-11-28 12:34 ` [Buildroot] [PATCH/next 3/6] package/tl-expected: " TIAN Yuanhao
2023-02-07 16:04 ` Thomas Petazzoni via buildroot
2022-11-28 12:34 ` [Buildroot] [PATCH/next 4/6] package/libsolv: " TIAN Yuanhao
2023-02-07 16:14 ` Thomas Petazzoni via buildroot [this message]
2022-11-28 12:34 ` [Buildroot] [PATCH/next 5/6] package/reproc: " TIAN Yuanhao
2023-02-07 16:14 ` Thomas Petazzoni via buildroot
2022-11-28 12:34 ` [Buildroot] [PATCH/next 6/6] package/micromamba: " TIAN Yuanhao
2023-02-07 16:26 ` Thomas Petazzoni via buildroot
2023-02-07 16:03 ` [Buildroot] [PATCH/next 1/6] package/cli11: " 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=20230207171401.54d75d16@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tianyuanhao3@163.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