All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@busybox.net, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v1 7/8] support/kconfig: reference environment variables directly (remove 'option env=')
Date: Wed, 8 May 2024 21:18:14 +0200	[thread overview]
Message-ID: <ZjvP9vE_Yszu9CLd@landeda> (raw)
In-Reply-To: <20240508165357.0a3ead1d@gmx.net>

Peter, All,

On 2024-05-08 16:53 +0200, Peter Seiderer via buildroot spake thusly:
> On Mon, 6 May 2024 21:06:23 +0200, Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> > On Mon,  6 May 2024 16:45:50 +0200
> > Peter Seiderer via buildroot <buildroot@buildroot.org> wrote:
> > > -	default "$(TOPDIR)/dl"
> > > +	default "\$(TOPDIR)/dl"
> > So here the "\$(TOPDIR)" is because we actually don't want the "new"
> > feature to kick in, and we want the value of this variable to be
> > expanded not by kconfig, but by the makefile machinery?
> Yes (sorry, the explaining sentence in the commit log got lost while
> rebasing/squashing)..., without the escape the expanded value is
> written out to the .config file...
> > So this also means that when we do $(BR2_EXTERNAL_BLABLA_PATH) in our
> > .config, it now also need to be \$(BR2_EXTERNAL_BLABLA_PATH) ? If so
> > that's going to break a *lot* of things...

This would also impact BR2_TARGET_GENERIC_ROOT_PASSWD, see the help
text: it can contain a literal string that starts with a $ sign.

> Needs to be tested ;-), but the problem is not in the .config files
> but in the Config.in* files...

So, that only impacts the 'default' entries, right? If a user actually
enters '$FOO' in a configurator, the appropriate, unexpanded value ends
up in the .config?

What would happen with:

    $ cat Config.in
    config BR2_FOO
        string "$(FOO)"

    $ FOO=27 BAR=42 make defconfig
    $ cat .config
    BR2_FOO=????

    $ FOO=27 BAR=42 make menuconfig
        BR2_FOO -> enter literal:  "$(BAR)"
    $ cat .config
    BR2_FOO=????

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-08 19:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 14:45 [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version Peter Seiderer via buildroot
2024-05-06 14:45 ` [Buildroot] [PATCH v1 1/8] boot/barebox/Config.in: source argument needs quotation marks Peter Seiderer via buildroot
2024-05-26 20:45   ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 2/8] package/cmocka/Config.in: bool " Peter Seiderer via buildroot
2024-05-26 20:46   ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 3/8] package/dovecot/Config.in: source " Peter Seiderer via buildroot
2024-05-26 20:46   ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 4/8] package/python-pydal/Config.in: bool " Peter Seiderer via buildroot
2024-05-26 20:45   ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 5/8] package/x11r7/Config.in: source " Peter Seiderer via buildroot
2024-05-26 20:46   ` Peter Korsgaard
2024-05-06 14:45 ` [Buildroot] [PATCH v1 6/8] support/kconfig: bump to linux-v6.9-rc5 version Peter Seiderer via buildroot
2024-05-08 21:41   ` Petr Vorel
2024-05-08 21:54     ` Peter Seiderer via buildroot
2024-05-09 10:51       ` Yann E. MORIN
2024-05-06 14:45 ` [Buildroot] [PATCH v1 7/8] support/kconfig: reference environment variables directly (remove 'option env=') Peter Seiderer via buildroot
2024-05-06 19:06   ` Thomas Petazzoni via buildroot
2024-05-08 14:53     ` Peter Seiderer via buildroot
2024-05-08 19:18       ` Yann E. MORIN [this message]
2024-05-06 14:45 ` [Buildroot] [PATCH v1 8/8] package/openssl: move libopenssl/libressl source statemetns outside of the choice Peter Seiderer via buildroot
2024-05-06 20:11   ` Yann E. MORIN
2024-05-08 15:07     ` Peter Seiderer via buildroot
2024-05-08 18:57       ` Yann E. MORIN
2024-05-06 19:04 ` [Buildroot] [PATCH v1 0/8] support/kconfig: bump to linux-v6.9-rc5 version Thomas Petazzoni via buildroot
2024-05-06 20:19   ` Yann E. MORIN
2024-05-06 20:21     ` Thomas Petazzoni via buildroot
2024-05-08 15:21     ` Peter Seiderer via buildroot
2024-05-08 19:08       ` Yann E. MORIN
2024-05-08 15:16   ` Peter Seiderer via buildroot
2025-05-18 14:55 ` Thomas Petazzoni via buildroot
2025-05-21  7:40   ` Peter Seiderer 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=ZjvP9vE_Yszu9CLd@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    --cc=ps.report@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.