All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH v4 3/3] amd-gpu-bin-mx51: new recipe
Date: Thu, 30 May 2013 14:02:33 +0200	[thread overview]
Message-ID: <51A73FD9.7040308@digi.com> (raw)
In-Reply-To: <20130530122926.42e03239@e6520eb>

Hi Eric,

On 30/05/13 12:29, Eric Bénard wrote:
> This raise an other problem :
> - when x11 is not in DISTRO_FEATURES, we shouldn't have the x11-bin
> package.

Well, this probably is solved by something like:

amd-gpu-x11-bin-mx51:
COMPATIBLE_MACHINE = "${@base_contains('DISTRO_FEATURES', 'x11', '(mx5)', 'Invalid!', d)}"

If x11 is not in DISTRO_FEATURES, then COMPATIBLE_MACHINE becomes
'Invalid!' and that does not match your machine (unless you have a
machine named "Invalid!" :-) )

> - when x11 is in DISTRO_FEATURES, we could have the non x11 package
> as nothing prevents users to have x11 in their distro features _and_ to
> build non x11 images : how to handle that (same problem in the mx6 gpu
> package) ?

Agree with you that this is a real problem, but unfortunately my
yocto skills are not good enough to know how to solve it. Hopefully
someone in the list will shed some light.

- 
Javier Viguera
Software Engineer
Digi International® Spain S.A.U.


  reply	other threads:[~2013-05-30 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 18:01 [meta-fsl-arm][PATCH v4 1/3] amd-gpu-x11-bin-mx51: only enable when x11 is in DISTRO_FEATURES Eric Bénard
2013-05-29 18:01 ` [meta-fsl-arm][PATCH v4 2/3] amd-gpu-x11-bin-mx51: factorize the recipes Eric Bénard
2013-05-29 18:01 ` [meta-fsl-arm][PATCH v4 3/3] amd-gpu-bin-mx51: new recipe Eric Bénard
2013-05-30  9:49   ` [PATCH " Javier Viguera
2013-05-30 10:29     ` Eric Bénard
2013-05-30 12:02       ` Javier Viguera [this message]
2013-05-30 12:07         ` Eric Bénard
2013-05-31 13:21           ` Otavio Salvador
2013-05-31 20:38     ` Eric Bénard

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=51A73FD9.7040308@digi.com \
    --to=javier.viguera@digi.com \
    --cc=eric@eukrea.com \
    --cc=meta-freescale@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.