All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: menuconfig task for kernels
Date: Tue, 10 Nov 2009 17:06:01 +0100	[thread overview]
Message-ID: <c384c5ea0911100806r7b163600l9adb62a23f1877a4@mail.gmail.com> (raw)
In-Reply-To: <4AF353C8.80904@cs.put.poznan.pl>

Hello,

On Thu, Nov 5, 2009 at 11:38 PM, Przemyslaw Wesolek
<przemyslaw.wesolek@cs.put.poznan.pl> wrote:
>
> The order of tasks to do menuconfig is, more or less: fetch, patch,
> menuconfig. It means that when menuconfig is run, there is no .config*
> files in linux build dir, and generated .config is far different than
> defconfig resulting from applying OE patches.
> [...]
> Is this the "right" way to do? If so, maybe menuconfig should be added
> as 'after do_configure', instead of 'after do_patch'?
>

Look in classes/kernel.bbclass, line ~221:

addtask menuconfig after do_patch

change it to:

addtask menuconfig after do_configure


and see if that helps.

I wonder if this can go upstream.


Regards,
-- 
Leon



  parent reply	other threads:[~2009-11-10 16:13 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
2009-11-09 16:10     ` Martin Jansa
2009-11-10 13:14       ` Przemyslaw Wesolek
2009-11-10 16:06 ` Leon Woestenberg [this message]
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=c384c5ea0911100806r7b163600l9adb62a23f1877a4@mail.gmail.com \
    --to=leon.woestenberg@gmail.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.