From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot GUI
Date: Fri, 27 Mar 2009 15:32:35 +0100 [thread overview]
Message-ID: <20090327153235.27e7bc22@surf> (raw)
In-Reply-To: <1238163903.6667.28.camel@ess-roelvp>
Le Fri, 27 Mar 2009 15:25:03 +0100,
Roeland Van Praet <roelvp@mind.be> a ?crit :
> As far as implementation goes, I don't think it will be difficult.
> The GUI should just be able to read the Config.in files and the tree
> structure, show the contents and generate a .config file.
> This will continue to work independently of any changes to the
> packages.
You mean just like xconfig/gconfig in the kernel source tree, which
already does that ? :-)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-03-27 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 13:55 [Buildroot] Buildroot GUI Lloyd Sargent
2009-03-27 14:25 ` Roeland Van Praet
2009-03-27 14:32 ` Thomas Petazzoni [this message]
2009-03-27 14:45 ` Roeland Van Praet
2009-03-29 1:12 ` Lloyd Sargent
2009-03-29 21:33 ` Peter Korsgaard
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=20090327153235.27e7bc22@surf \
--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