From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Makefile: expose 'graph-depends' to generate a graph of the dependency tree
Date: Tue, 7 Jan 2014 08:37:23 +0800 [thread overview]
Message-ID: <20140107083723.2cc506c5@skate> (raw)
In-Reply-To: <20131229111620.90FC09C227@busybox.osuosl.org>
Yann,
On Sun, 29 Dec 2013 12:13:19 +0100, Thomas Petazzoni wrote:
> Generate the graph of the complete dependency tree by calling:
> make graph-depends
>
> It's also possible to generate the graph-depends for a single package:
> make PKG-graph-depends
I just tested this in an out-of-tree situation... and it doesn't work.
It generates the dependency graph of the configuration that is in the
Buildroot source tree (I happened to have one) and not the one of the
Buildroot build tree.
To reproduce:
cd buildroot-sources/
make menuconfig
# create some configuration 1
mkdir ../buildroot-build
cd ../buildroot-build
make -C ../buildroot-sources O=$(pwd) menuconfig
# create some configuration 2
make graph-depends
The generated graph will correspond to "configuration 1" and not the
expected "configuration 2".
I suspect it's a problem in the graph-depends script itself rather than
the integration you made, but I haven't looked in detail.
Cheers,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-07 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 11:13 [Buildroot] [git commit] Makefile: expose 'graph-depends' to generate a graph of the dependency tree Thomas Petazzoni
2014-01-07 0:37 ` Thomas Petazzoni [this message]
2014-01-07 18:08 ` Yann E. MORIN
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=20140107083723.2cc506c5@skate \
--to=thomas.petazzoni@free-electrons.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