From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: menuconfig task for kernels
Date: Mon, 09 Nov 2009 10:40:36 -0500 [thread overview]
Message-ID: <4AF837F4.1050501@cbnco.com> (raw)
In-Reply-To: <4AF74838.6020308@cs.put.poznan.pl>
Przemyslaw Wesolek wrote:
>> Is this the "right" way to do? If so, maybe menuconfig should be added
>> as 'after do_configure', instead of 'after do_patch'?
>
> Anyone?
Hi Przemek,
I find if I'm configuring for a new machine, I need to do_patch, copy a
"close" defconfig into place, run make menuconfig, and copy the .config
back to the filesdir where it belongs. The menuconfig task doesn't save
much, as you still have to copy the defconfigs around. I don't use the
task for that reason, and maybe others are in the same boat.
I think you're right about the order, though; if you sent a patch, I
would ack it, for what it's worth.
Mike
next prev parent reply other threads:[~2009-11-09 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 22:38 menuconfig task for kernels Przemyslaw Wesolek
2009-11-08 22:37 ` Przemyslaw Wesolek
2009-11-09 15:40 ` Michael Smith [this message]
2009-11-09 16:10 ` Martin Jansa
2009-11-10 13:14 ` Przemyslaw Wesolek
2009-11-10 16:06 ` Leon Woestenberg
2009-11-10 17:05 ` Otavio Salvador
2009-11-12 15:15 ` Leon Woestenberg
2009-11-12 19:29 ` Przemyslaw Wesolek
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=4AF837F4.1050501@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.