All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt and detecting iWMMXT
Date: Sat, 25 Sep 2010 10:29:20 +0200	[thread overview]
Message-ID: <4C9DB2E0.9050004@eukrea.com> (raw)
In-Reply-To: <AANLkTimWTmhU6Kh65wLGpLzbOmAQKb3BKfRnH+tBKa0k@mail.gmail.com>

Le 25/09/2010 10:18, Frans Meulenbroeks a écrit :
> 2010/9/25 Frans Meulenbroeks<fransmeulenbroeks@gmail.com>:
>> 2010/9/25 Koen Kooi<k.kooi@student.utwente.nl>:
>>> #build with support for the iwmmxt instruction (pxa270 and up)
>>> MY_ARCH := "${PACKAGE_ARCH}"
>>> PACKAGE_ARCH = "${@base_contains('MACHINE_FEATURES', 'iwmmxt', 'iwmmxt',
>>> '${MY_ARCH}',d)}"
>>>
>>> QT_CONFIG_FLAGS_append = " ${@base_contains('MACHINE_FEATURES',
>>> 'iwmmxt', ' -iwmmxt', '',d)} "
>>>
>>> regards,
>>>
>>> Koen
>>
>> Nice solution.
>> Guess it would be useful to have a list of all possible
>> MACHINE_FEATURES and DISTRO_FEATURES somewhere (e.g. wiki)
>>
>> Frans
>>
> Rethinking the issue: assuming we *do* want SOC_FAMILY would it not be
> more appropriate to use that here?
>
you can have a SOC which supports iwmmx and wish not using it so 
MACHINE_FEATURES seems sane here.

Eric



  reply	other threads:[~2010-09-25  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 20:59 Qt and detecting iWMMXT Holger Freyther
2010-09-24 21:06 ` Frans Meulenbroeks
2010-09-24 21:28   ` Holger Freyther
2010-09-24 22:11 ` Koen Kooi
2010-09-25  7:09   ` Frans Meulenbroeks
2010-09-25  8:18     ` Frans Meulenbroeks
2010-09-25  8:29       ` Eric Bénard [this message]
2010-09-25 14:21 ` Enrico Scholz

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=4C9DB2E0.9050004@eukrea.com \
    --to=eric@eukrea.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.