All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Per-machine DEPENDS
Date: Thu, 17 May 2012 21:27:52 +0100	[thread overview]
Message-ID: <4904220.mFpDsjEpuq@helios> (raw)
In-Reply-To: <0A3A31D3-D0DF-4C56-8896-1075F801C8BD@keylevel.com>

On Thursday 17 May 2012 21:10:10 Chris Tapp wrote:
> Is it possible to have the (R)DEPENDS list vary depending on the machine
> being built?
> 
> For example, I want 'this-bit' to be included for a 'machine-1' build, but
> not 'machine-2'.
> 
> Something like:
> 
> DEPENDS = "common-stuff"
> 
> DEPENDS_machine-1 = "${DEPENDS} this-stuff"

Yes, that will work. If the DEPENDS change implies some different configuration 
I'd recommend being explicit about it as well e.g. via EXTRA_OECONF or 
whatever is appropriate; this is particularly important for the case where the 
extra dependency is not included and the configure script for the application 
would auto-detect the presence of the additional dependency in the absence of 
an explicit configure option.

Also, ideally these machine-specific bits should live in a bbappend within the 
BSP for that machine, thus keeping the recipe itself more or less generic.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2012-05-17 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 20:10 Per-machine DEPENDS Chris Tapp
2012-05-17 20:27 ` Paul Eggleton [this message]
2012-05-17 21:07   ` Chris Tapp
2012-05-17 21:22     ` Paul Eggleton
2012-05-23  7:55       ` Chris Tapp
2012-05-23  8:31         ` Tomas Frydrych
2012-05-23 19:02           ` Chris Tapp
2012-05-23 19:30             ` Andrei Gherzan

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=4904220.mFpDsjEpuq@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=opensource@keylevel.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.