From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: yann.morin@orange.com, ps.report@gmx.net, petr.vorel@gmail.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 7/9] package/openssl: move libopenssl/libressl/.br2-external.in.openssl source statements outside of the choice
Date: Sun, 31 May 2026 18:22:43 +0200 [thread overview]
Message-ID: <ahxgJkG0qqeRJf29@windsurf> (raw)
In-Reply-To: <20260531153557.2375580-8-titouan.christophe@mind.be>
On Sun, May 31, 2026 at 05:35:51PM +0200, Titouan Christophe wrote:
> +config BR2_PACKAGE_OPENSSL_EXTERNAL
> + bool "from an external tree"
> + depends on "$(BR2_EXTERNAL)" != ""
Hu? What is this thing?
And what about the other packages that are like openssl, i.e virtual
packages that may have providers in BR2_EXTERNAL trees?
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
next prev parent reply other threads:[~2026-05-31 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 15:35 [Buildroot] [PATCH v4 0/9] Update kconfig infrastructure to Linux 6.9 Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 1/9] Makefile: always use a base config file for defconfig Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 2/9] support/kconfig: fix invalid filenames in patch 23 Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 3/9] Config.in: do not expand TOPDIR, BASE_DIR and CONFIG_DIR Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 4/9] toolchain-external: do not expand ARCH Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 6/9] support/kconfig: reference environment variables directly (remove 'option env=') Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 7/9] package/openssl: move libopenssl/libressl/.br2-external.in.openssl source statements outside of the choice Titouan Christophe via buildroot
2026-05-31 16:22 ` Thomas Petazzoni via buildroot [this message]
2026-06-01 6:50 ` Titouan Christophe via buildroot
2026-06-01 7:51 ` Thomas Petazzoni via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 8/9] docs: update the Buildroot manual for kconfig variables expansion Titouan Christophe via buildroot
2026-05-31 15:35 ` [Buildroot] [PATCH v4 9/9] Makefile: add new target "yellowconfig" based on kconfiglib Titouan Christophe 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=ahxgJkG0qqeRJf29@windsurf \
--to=buildroot@buildroot.org \
--cc=petr.vorel@gmail.com \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
--cc=yann.morin@orange.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