Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: why conditional assignment of DEPLOY_DIR_IMAGE in bitbake.conf?
Date: Tue, 22 Jul 2014 12:36:10 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407221229210.8547@localhost> (raw)


  quite possibly another silly question, but i'm perusing poky's
version of bitbake.conf and i see this:

DEPLOY_DIR ?= "${TMPDIR}/deploy"
DEPLOY_DIR_TAR = "${DEPLOY_DIR}/tar"
DEPLOY_DIR_IPK = "${DEPLOY_DIR}/ipk"
DEPLOY_DIR_RPM = "${DEPLOY_DIR}/rpm"
DEPLOY_DIR_DEB = "${DEPLOY_DIR}/deb"
DEPLOY_DIR_IMAGE ?= "${DEPLOY_DIR}/images/${MACHINE}"
DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"

  now, what is the value of using "?=" to set DEPLOY_DIR_IMAGE, rather
than just "=". i know what "?=" represents, but i normally expect to
see it in a context where someone might have set it earlier to some
other value, but this is in bitbake.conf, before any of the "include"
or "require" directives to pull in any of the other .conf files. so in
the midst of all those other DEPLOY_DIR_* hard assignments, why is the
images directory a conditional install?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



             reply	other threads:[~2014-07-22 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 16:36 Robert P. J. Day [this message]
2014-07-22 16:43 ` why conditional assignment of DEPLOY_DIR_IMAGE in bitbake.conf? Christopher Larson
2014-07-22 16:53   ` Robert P. J. Day
2014-07-22 17:04     ` Mark Hatle

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=alpine.LFD.2.11.1407221229210.8547@localhost \
    --to=rpjday@crashcourse.ca \
    --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