Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: yocto <yocto@yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: --conf Was: Features in Yocto Project 1.7
Date: Wed, 26 Mar 2014 10:33:04 -0400	[thread overview]
Message-ID: <5332E520.5050005@linaro.org> (raw)
In-Reply-To: <20140325055028.GA3710@jama>

On 03/25/14 01:50, Martin Jansa wrote:
> Can you show some example of config you need to have wor wayland and
> cannot have for core-image-minimal? 

Okay, good point. I should have thought harder to come up with a better
example :-) It's funny, actually, that you're the one pressing me on
this, I first encountered this issue and started thinking about it while
trying to reproduce your "State of bitbake world" tests :-)

Let's say you're a board maintainer; some people want to run gstreamer,
some people want to try out systemd, some want to run wayland. Each of
these requires tweaks to a conf/local.conf, no? I'm constantly changing
my set of IMAGE_INSTALL_append's, fiddling with preferred versions, and
distro features.

If I'm just doing a one-off build then sure, adjust conf/local.conf
manually. But if I'm perpetually rotating between a bunch of tests as
repositories are modified, it would be easier to just specify which
configuration I want from the bitbake cmdline.

As I mentioned, maybe I'm doing things wrong? Maybe others have separate
build locations, or maybe others define their own images which
incorporate these adjustments? But I'd be quite surprised to find I'm
the only one having to edit conf/local.conf to comment/un-comment blocks
before every build.

As a concrete example, currently I'm flipping between dora and master
builds. For some reason I can't seem to reuse the same TMPDIR between
them. So every time I "repo init -b <newbranch>" I then also have to
edit conf/local.conf before bitbaking.


  reply	other threads:[~2014-03-26 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 16:00 Features in Yocto Project 1.7 Richard Purdie
     [not found] ` <533058C1.3000102@arm.com>
2014-03-24 16:18   ` [yocto] " Richard Purdie
2014-03-24 19:40 ` Rifenbark, Scott M
2014-03-25  0:11 ` --conf Was: " Trevor Woerner
2014-03-25  5:50   ` Martin Jansa
2014-03-26 14:33     ` Trevor Woerner [this message]
2014-03-26 14:38       ` Otavio Salvador
2014-03-26 20:45         ` Nicolas Dechesne
2014-03-27 16:33           ` Trevor Woerner
2014-03-26 14:46       ` Martin Jansa
2014-03-25 12:22 ` Otavio Salvador
2014-03-25 15:14   ` Mark Hatle
2014-03-25 14:31 ` David Nyström
2014-03-25 15:16   ` Mark Hatle
2014-03-25 17:37   ` [yocto] " Philip Balister
2014-03-27 10:47   ` David Nyström
2014-03-28 15:23     ` Otavio Salvador
2014-03-28 18:00       ` David Nystrom

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=5332E520.5050005@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto@yoctoproject.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