Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	denys@ti.com
Subject: Re: [PATCH] nativesdk-qt4-tools: remove nativesdk-libx11 for qt-embedded
Date: Mon, 12 Aug 2013 13:09:22 -0700	[thread overview]
Message-ID: <520940F2.7040508@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKqf=FhdAzq1q_Dj1Hppcub9C4aGyYGGt587or-7fOmcdQ@mail.gmail.com>

On 08/12/2013 12:26 PM, Otavio Salvador wrote:
> Hello Eric,
>
> On Mon, Aug 12, 2013 at 10:58 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>>> I'm afraid we can't do this since you just broke any other kind of
>>> override which might get used anywhere by any recipe using this .inc
>>> file. I'd also be wary of adding something as simple as "qt" into
>>> overrides since it can match things more widely than you might want.
>>>
>>
>> I'm a bit of an OE n00b, and I'm not quite sure how to express this
>> conditional.
>>
>> meta-toolchain-qte shouldn't depend on nativesdk-libx11, and I'm
>> not sure how the dependency can be moved to the X11 recipe
>> recipes_qt/meta/meta-toolchain-qt.bb.
>
> I think you're looking for to:
>
> http://privatepaste.com/cc22a68c56
>
> The missing part for merging it is to /force/ it to be disabled in qt
> configure. This was last Richard complain about this patch when I sent
> it.
>
Thanks Otavio,

I saw the ${@base_contains('DISTRO_FEATURES', construct elsewhere
but got lost in the Python (scratching my head over the trailing 'd').



      reply	other threads:[~2013-08-12 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 21:36 [PATCH] nativesdk-qt4-tools: remove nativesdk-libx11 for qt-embedded Eric Nelson
2013-08-12  7:08 ` Richard Purdie
2013-08-12 13:58   ` Eric Nelson
2013-08-12 19:26     ` Otavio Salvador
2013-08-12 20:09       ` Eric Nelson [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=520940F2.7040508@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=denys@ti.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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