All of lore.kernel.org
 help / color / mirror / Atom feed
* Qt commercial support
@ 2012-12-12  0:56 Felipe Ferreri Tonello
  2012-12-12 15:58 ` Paul Eggleton
  0 siblings, 1 reply; 2+ messages in thread
From: Felipe Ferreri Tonello @ 2012-12-12  0:56 UTC (permalink / raw)
  To: poky

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.

Is there a better way to fix that? Maybe a patch idea.

Regards

Felipe Tonello


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Qt commercial support
  2012-12-12  0:56 Qt commercial support Felipe Ferreri Tonello
@ 2012-12-12 15:58 ` Paul Eggleton
  0 siblings, 0 replies; 2+ messages in thread
From: Paul Eggleton @ 2012-12-12 15:58 UTC (permalink / raw)
  To: Felipe Ferreri Tonello; +Cc: poky

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-12-12 15:58 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-12  0:56 Qt commercial support Felipe Ferreri Tonello
2012-12-12 15:58 ` Paul Eggleton

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.