Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: bitbake-devel@lists.openembedded.org
Subject: Graphviz folder
Date: Thu, 24 Jan 2013 11:12:55 +0000	[thread overview]
Message-ID: <51011737.8020501@communistcode.co.uk> (raw)

I was wondering if there would be support or interest for a patch which 
puts generated graphviz and dependancy files into their own folder.

Currently bitbake -g image creates a multitude of files in the root 
folder and I feel it just gets a bit messy. I think a better solution 
would either be to put the files in their own folder e.g. graphviz (name 
to be decided) or in tmp/graphviz.

On the topic of graphviz I can't seem to find a supported application 
for viewing the files as a nice graph, is this format still relevant 
these days?

Thoughts?

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




             reply	other threads:[~2013-01-24 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 11:12 Jack Mitchell [this message]
2013-01-24 14:12 ` Graphviz folder Paul Eggleton

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=51011737.8020501@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=bitbake-devel@lists.openembedded.org \
    /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