All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How can I make recipes conditionally enabled?
Date: Tue, 27 Aug 2013 17:32:52 +0200	[thread overview]
Message-ID: <20130827153252.GY3544@jama> (raw)
In-Reply-To: <CA+AhUGwh7dX=6Cw98xzdmgr=W9=J2h7y7iuQjmDTM_HOW1hUCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]

On Tue, Aug 27, 2013 at 03:56:40PM +0200, Erik Botö wrote:
> Hi,
> 
> On Tue, Aug 27, 2013 at 9:54 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Tue, Aug 27, 2013 at 09:12:15AM +0200, Carlos Rafael Giani wrote:
> >> 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.
> >
> > BB_DANGLINGAPPENDS_WARNONLY is the magic word.
> 
> I also saw some nice use of inspecting BBFILE_COLLECTIONS in the layer
> configuration done by Mentor, see
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/tree/conf/layer.conf#n9
> 
> Then you would place the files you only want to enable for e.g.
> meta-qt5 in a qt5-layer directory in your layer. Those files would
> then just be used if BBFILE_COLLECTIONS contains qt5-layer, which is
> only the case if you have added meta-qt5.
> 
> I know meta-fsl-arm uses this for meta-qt5 bbappends.

Something similar was also used in meta-systemd layer (you need to check
older revision than 8b465f791a5ef3d9ef138a206c6fb9c3bbcb55b1)

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-08-27 15:31 UTC|newest]

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

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=20130827153252.GY3544@jama \
    --to=martin.jansa@gmail.com \
    --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 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.