All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: developing with devshell and effect of the bitbake.conf file
Date: Wed, 20 Jun 2012 07:04:01 +0100	[thread overview]
Message-ID: <4FE167D1.9010907@r-finger.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A11736@ORSMSX101.amr.corp.intel.com>

Hi Scott,

On 19/06/12 19:13, Rifenbark, Scott M wrote:
> Hi, I want to throw this out for discussion.  I recently was looking
> at a section in the YP Reference manual
> (http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#platdev-appdev-devshell)
> where it talks about developing using devshell.  I asked Darren Hart
> if this was a valid development model and he says it is.

Absolutely, without devshell poky would be just a distro image builder,
devshell makes into a proper development tool, e.g. devshell is by far
the easiest way to develop/maintain patches (together with quilt) or to
tweak applications when debugging and testing.


> There is a
> part of the section though that talks about the bitbake.conf file.
> That section in the conf file does not seem to exist anymore.  And,
> Darren (after some testing) doesn't see how what is in the
> bitbake.conf file affects development with devshell.  Any comments
> welcome.

I think that bit of the manual is leftover from days of distant past.
The terminal selection it mentions generally happens automatically, but
can be forced by the OE_TERMINAL variable from local.conf, where it is
also documented.

Tomas



  parent reply	other threads:[~2012-06-20  6:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 18:13 developing with devshell and effect of the bitbake.conf file Rifenbark, Scott M
2012-06-20  1:09 ` Stewart, David C
2012-06-20  6:04 ` Tomas Frydrych [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 15:46 Rifenbark, Scott M
2012-09-06 14:01 ` Paul Eggleton

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=4FE167D1.9010907@r-finger.com \
    --to=tf+lists.yocto@r-finger.com \
    --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 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.