Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-devel@lists.openembedded.org
Subject: How can I make recipes conditionally enabled?
Date: Tue, 27 Aug 2013 09:12:15 +0200	[thread overview]
Message-ID: <521C514F.1000405@pseudoterminal.org> (raw)

Hello,

I have a question about a problem I've had several times in the past:

if I write a layer, and add .bbappends, then the layers with the 
corresponding .bb files become hard dependencies.
But lets say I want to write a BSP layer, and I add some machine 
specific Qt5 patches. Now everybody who wants to use
my layer must also include meta-qt5, even when they don't really want to 
use Qt5 anywhere. This is made even worse
if I have a dependency on meta-oe, which itself brings in a lot of 
modifications.

In short, I'd like to be able to make .bbappends and .bb files dependend 
on whether or not a layer is available. The hard
dependency is fine if it concerns things that are essential in my layer. 
But if its about optional things, it shouldn't cause
a build failure.

Thoughts?


             reply	other threads:[~2013-08-27  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  7:12 Carlos Rafael Giani [this message]
2013-08-27  7:54 ` How can I make recipes conditionally enabled? Martin Jansa
2013-08-27 13:56   ` Erik Botö
2013-08-27 15:32     ` Martin Jansa

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=521C514F.1000405@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=openembedded-devel@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