From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: addtask menuconfig after do_configure (instead of do_patch)?
Date: Mon, 16 Nov 2009 11:38:27 +0100 [thread overview]
Message-ID: <4B012BA3.5080309@kernelconcepts.de> (raw)
In-Reply-To: <c384c5ea0911100825s66f64234s8d1c27b66221faca@mail.gmail.com>
Hi,
Leon Woestenberg schrieb:
> classes/kernel.bbclass:
>
> -addtask menuconfig after do_patch
> +addtask menuconfig after do_configure
>
> This will make sure the OE default configuration is used as the
> default config before going into the menu.
this might be a good idea. I guess this would be the desired starting point.
> Downside is that menuconfig will probably not work for new kernel
> recipes without defconfig.
Yes true, but to be honest: Do we really need to support this? I am willing to
learn but currently I do not see much of use in kernel recipes without defconfig.
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
next prev parent reply other threads:[~2009-11-16 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:25 addtask menuconfig after do_configure (instead of do_patch)? Leon Woestenberg
2009-11-16 10:38 ` Florian Boor [this message]
2009-11-16 22:18 ` [PATCH] Reorganized kernel class to run 'menuconfig' after 'configure' Przemyslaw Wesolek
2009-11-18 10:25 ` Phil Blundell
2009-11-18 10:32 ` Koen Kooi
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=4B012BA3.5080309@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--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.