From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Felipe Ferreri Tonello <eu@felipetonello.com>
Cc: poky@yoctoproject.org
Subject: Re: Qt commercial support
Date: Wed, 12 Dec 2012 15:58:34 +0000 [thread overview]
Message-ID: <4279118.9X6CKSTVLQ@helios> (raw)
In-Reply-To: <50C7D64A.2090403@felipetonello.com>
Hi Felipe,
On Tuesday 11 December 2012 16:56:42 Felipe Ferreri Tonello wrote:
> Basically there is still no easy way to support commercial Qt versions.
> Yocto Bug #2505 fixes part of it but not all.
>
> In my case I have to provide, not just a qt4-x11-commercial recipe, but
> all others native and sdk recipes basically because the OE-Core ones
> enforces the download of the opensource version.
>
> It would be perfect if we can provide our own .tar.gz or git repo with
> our modified Qt version.
>
> I know that we can provide a bbappend to change that but still not a
> perfect solution.
There are two solutions I can think of:
a) Use a bbappend for the native and nativesdk recipes as you mentioned
b) Copy the qt4-native recipe to qt4-commercial-native and add PROVIDES +=
"qt4-native" to it; copy the nativesdk-qt4-tools recipe to nativesdk-qt4-
commercial-tools and add PROVIDES += "nativesdk-qt4-tools" to it; then set
PREFERRED_PROVIDER_qt4-native = "qt4-commercial-native" and
PREFERRED_PROVIDER_nativesdk-qt4-tools = "nativesdk-qt4-commercial-tools" in
your distro or local configuration. [Replace nativesdk-qt4-tools with qt4-
tools-nativesdk if you are using the denzil release or earlier].
Ultimately I don't have access to the commercial version of Qt and nor do most
people, so we can't provide recipes for the commercial version out of the box;
however just as with bug 2505 if we can make things easier for people who do
want to build it then we will try our best to do so, as long as you can
provide us with feedback on improvements.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-12-12 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 0:56 Qt commercial support Felipe Ferreri Tonello
2012-12-12 15:58 ` Paul Eggleton [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=4279118.9X6CKSTVLQ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=eu@felipetonello.com \
--cc=poky@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.