From: JNY <jny0@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot, busybox and kernal config
Date: Fri, 9 Jul 2010 00:07:35 -0700 (PDT) [thread overview]
Message-ID: <29108097.post@talk.nabble.com> (raw)
I have used buildroot several times before, but never with busybox. I have
been given the 3 above config files, and need to use buildroot to make a
working system. In the past all I've had to do is 'make menuconfig', point
to the buildroot.config file, to load the previous project's settings, alter
them according to the new project, save and 'make'. I've followed the
instructions to do the same thing using 'make busybox-menuconfig' loading
the busybox.config, and saving. I'm slightly unsure what to do with the
kernal.config file, and what to do next. Any help would be recieved
gratefully.
--
View this message in context: http://old.nabble.com/buildroot%2C-busybox-and-kernal-config-tp29108097p29108097.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2010-07-09 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 7:07 JNY [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-09 7:07 [Buildroot] buildroot, busybox and kernal config JNY
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=29108097.post@talk.nabble.com \
--to=jny0@hotmail.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