Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] Add something like bitbake -cmenuconfig <recipe> ?
Date: Sat, 16 May 2015 22:34:10 +0100	[thread overview]
Message-ID: <1431812050.4956.5.camel@linuxfoundation.org> (raw)
In-Reply-To: <55555B65.80600@windriver.com>

On Fri, 2015-05-15 at 10:35 +0800, Robert Yang wrote:
> Hello,
> 
> Is is useful/possible if we add something like bitbake <recipe> -cmenuconfig,
> just like kernel's make menuconfig ?
> 
> We can use the menuconfig to config the vars such as MACHINE, DL_DIR,
> DISTRO_FEATURES, MACHINE_FEATURES and all the variables which are
> configurable, I think that this would help the newbie a lot.
> 
> I think that we can add a menuconfig.bbclass (or other names) to do this,
> and I'd like to work on it.

Why would you want to specify a <recipe> when configuring MACHINE? I
understand why you're thinking this but it isn't well thought out and in
this form would confuse users more than help them.

I don't think the system will even parse without a valid MACHINE, let
alone execute tasks.

Cheers,

Richard



  reply	other threads:[~2015-05-16 21:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  2:35 [RFC] Add something like bitbake -cmenuconfig <recipe> ? Robert Yang
2015-05-16 21:34 ` Richard Purdie [this message]
2015-05-18  1:52   ` Robert Yang
2015-05-18  8:45     ` Paul Eggleton
2015-05-18 11:52       ` Otavio Salvador
2015-05-18 12:04         ` Paul Eggleton
2015-05-18 15:15           ` Christopher Larson
2015-05-18 15:32             ` Paul Eggleton
2015-05-19  7:09               ` Robert Yang
2015-05-19  8:35                 ` [RFC] Add something like bitbake -cmenuconfig <recipe>? Paul Eggleton
2015-05-19  9:19                   ` Robert Yang
2015-06-01 15:18                     ` Christopher Larson
2015-05-19 19:56                   ` Bernhard Reutner-Fischer
2015-06-01 13:29                   ` Trevor Woerner

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=1431812050.4956.5.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox