From: "Émeric Vigier" <emeric.vigier@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] Makefile: add variable print capabilities
Date: Thu, 19 Jul 2012 18:25:59 -0400 (EDT) [thread overview]
Message-ID: <928152212.982383.1342736759185.JavaMail.root@mail.savoirfairelinux.com> (raw)
In-Reply-To: <20120719220825.584bfb03@skate>
----- Mail original -----
> Le Thu, 19 Jul 2012 15:01:17 -0400,
> Emeric Vigier <emeric.vigier@savoirfairelinux.com> a ?crit :
>
> > I just got started with buildroot yesterday, and like it :-).
> > I am no Makefile expert, then often I turn into wanting to check
> > Makefile variables.
> > This patch adds a capability to do so by issuing:
> >
> > $ make print-<myvariable>
> >
> > e.g.
> >
> > $ make print-DL_DIR
> > DL_DIR = /home/evigier/buildroot/dl
>
> Hum, is this really useful? What are the use cases? What do other
> thinks about this?
It is somehow similar to Android's "get_build_var" which is very useful to me.
$ get_build_var TARGET_OUT
out/target/product/panda/system
But maybe there are other convenient ways to retrieve those INKTV (I never know the value) variables without grepping or reading Makefile and included ones?
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
--
Emeric
next prev parent reply other threads:[~2012-07-19 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 19:01 [Buildroot] [PATCH 0/1] Makefile: add variable print capabilities Emeric Vigier
2012-07-19 19:01 ` [Buildroot] [PATCH] " Emeric Vigier
2012-07-19 20:08 ` [Buildroot] [PATCH 0/1] " Thomas Petazzoni
2012-07-19 22:25 ` Émeric Vigier [this message]
2013-05-26 19:40 ` Yann E. MORIN
2013-05-26 19:44 ` Thomas Petazzoni
2013-05-26 19:48 ` Yann E. MORIN
2013-05-26 20:03 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2012-07-19 18:29 Emeric Vigier
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=928152212.982383.1342736759185.JavaMail.root@mail.savoirfairelinux.com \
--to=emeric.vigier@savoirfairelinux.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