From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] graphs: add option to remove transitive dependencies in dependency graph
Date: Fri, 9 May 2014 15:34:41 +0200 [thread overview]
Message-ID: <20140509133441.GE3173@free.fr> (raw)
In-Reply-To: <CAHXCMMK9Y-bReA=vij5ti0ZKeehXEx45nsw8H-+G01LUcF1RMw@mail.gmail.com>
Samuel, All,
On 2014-05-09 13:16 +0200, Samuel Martin spake thusly:
> > On 2014-05-09 12:00 +0200, Peter Korsgaard spake thusly:
[--SNIP--]
> >> Thanks. Like I mentioned on IRC I do like the looks of the graphs, but
> >> I'm not really happy with the use of environment variables to control
> >> it, as it isn't intuitive.
>
> I'm not a big fan of env. vars. either.
[--SNIP--]
> An alternaitve solution could be using a config file; Python has some
> packages for this [1] ;-).
> This way, the config file could be initialized with what is set in the
> menuconfig, so used as defaults.
> If some options are passed on the command line, they will override
> these defaults.
> If someone wants to do something more fancy and automatic, then one
> just could update the config file.
Well, this does not solve the issue at hand: how do we pass options on
the command line in the first place?
We added 'graph-depends' and 'PKG-graph-depends' (and 'graph-build'
too) as make targets so it was easier for users to generate the graphs
rather than directly call the scripts (since the scripts could even
reside in another dir when building out-of-tree, and it would be more
complex to reach for the scripts).
Adding a config file would not help much either: modifying the config
file can't easily be automated, which is all the point in being able to
pass extra args when generating the graphs.
There are people out there using a bunch of graphs to include in their
projects' documentations, in an automated way.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-05-09 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:44 [Buildroot] [PATCH] graphs: add option to remove transitive dependencies in dependency graph Yann E. MORIN
2014-05-09 9:52 ` Yann E. MORIN
2014-05-09 10:00 ` Peter Korsgaard
2014-05-09 10:20 ` Yann E. MORIN
2014-05-09 11:16 ` Samuel Martin
2014-05-09 13:34 ` Yann E. MORIN [this message]
2014-05-09 14:09 ` Samuel Martin
2014-05-09 14:38 ` Yann E. MORIN
2014-05-09 15:07 ` Samuel Martin
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=20140509133441.GE3173@free.fr \
--to=yann.morin.1998@free.fr \
--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