Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding post image hook
Date: Wed, 13 May 2020 22:16:28 +0200	[thread overview]
Message-ID: <20200513221628.42c07184@windsurf.home> (raw)
In-Reply-To: <ea-mime-5ebc52f4-7a9b-60b07d84@www-1.mailo.com>

Hello Louis-Paul,

You should consider changing your e-mail client, or configure it
better. Indeed, the plain text version of your e-mail is not properly
quoted, i.e the text from me you are replying to was not quoted with
">" signs.

On Wed, 13 May 2020 22:05:08 +0200 (CEST)
lpdev at cordier.org wrote:

> You can actually do that, by running:
> 
> make VARS=<some-variable-name> printvars
> 
> from your post-image script.
> 
> If what you need to retrieve is the version of the different packages,
> you can also run:
> 
> make show-info
> 
> from your post-image script, and parse the JSON output.
> 
> 
> 

> Thank you for the tip. However this method seems to be very slow
> because of the makefile parsing (takes between 5 to 10sec on my PC).
> I would not recommend that for retrieving values of a lot of
> variables.

You can do:

  make VARS=FOO% printvars

if the different variables you want to get match a wildcard.

Or alternatively, you can do just:

  make printvars

pay the one-time price of dumping all variables, and then grab what you
need from the output.

But otherwise, I agree that indeed it is quite slow.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-05-13 20:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 14:35 [Buildroot] Adding post image hook lpdev at cordier.org
2020-05-11 15:50 ` Thomas Petazzoni
2020-05-13 20:05   ` lpdev at cordier.org
2020-05-13 20:16     ` Thomas Petazzoni [this message]
2020-05-13 20:35       ` Patrick Mochel
2020-05-13 21:09       ` Patrick Mochel
2020-05-13 21:29         ` Yann E. MORIN
2020-05-13 21:32           ` Yann E. MORIN
2020-05-13 21:46           ` Patrick Mochel
2020-05-13 23:27             ` LP C

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=20200513221628.42c07184@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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