All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: What's the purpose of "BDIR" in oe-buildenv-internal?
Date: Thu, 27 Oct 2011 14:00:38 -0700	[thread overview]
Message-ID: <4EA9C676.7000408@intel.com> (raw)
In-Reply-To: <20111027162751.fbwguloe84sooggc@crashcourse.ca>

On 10/27/2011 01:27 PM, Robert P. J. Day wrote:
> prepping to give a yocto talk to my local (ottawa) LUG next week, and
> was reviewing the logic of the setup starting with oe-init-build-env,
> and noticed in scripts/oe-buildenv-internal a test of the variable
> BDIR for the name of the build directory. but there's no mention of
> that variable in the calling oe-init-build-env, and i see no mention
> of it in the intro-level docs.
>
> clearly, one could use that shell env variable if one wanted to name
> the build directory to be used, but given that there's absolutely no
> explanation of it anywhere for a new user, what exactly is its purpose?
>
> rday

This allows you to specify a build directory that lives elsewhere on 
your filesystem, rather than in poky/build. This is handy in case you 
want to keep the build system source tree pristine.

Simply source the build init script with the desired build directory as 
an argument. I'm quite sure we have this documented, although BDIR isn't 
explicitly mentioned.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


  reply	other threads:[~2011-10-27 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 20:27 What's the purpose of "BDIR" in oe-buildenv-internal? Robert P. J. Day
2011-10-27 21:00 ` Scott Garman [this message]
2011-10-28  0:58   ` Robert P. J. Day

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=4EA9C676.7000408@intel.com \
    --to=scott.a.garman@intel.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.