All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: qt5 toolchain
Date: Fri, 16 Oct 2015 00:03:07 +0200	[thread overview]
Message-ID: <5620229B.9020700@webthatworks.it> (raw)
In-Reply-To: <CAP9ODKocdXSX1Dpm48yhskMcwnYmt76ZP9Wb55KksR3m8x1=vg@mail.gmail.com>

On 10/15/2015 06:48 PM, Otavio Salvador wrote:

>> I'll subscribe to openembedded ML and move the topic there to see what would
>> be the quality level required for a patch to
>> packagegroup-qt5-toolchain-target.bb
>> or if I should just write my own layer to _remove stuff from there.

>>  From my point of view disabling opengl (and other things strictly HW
>> related) should be something set in the lowest layer and be passed on to
>> higher software layer so to make it clearer to higher layers that they
>> should take it into account ASAP and not as a "retro-fit".

>> qtlocation doesn't seem to depend on qt3d anymore, but it still depends on
>> qtquickcontrols that up to my memory depends on opengl.

> All your feedback is valuable and I agree with it. We welcome patches
> to improve the support for opengl-less CPUs or you can hire someone
> (us - O.S. Systems, or other software vendor) to do the work.
> Personally I do my best to address as many things as my free time can
> fit so I apologize for your turn-key experience not being as good as
> you wished but you can help to improve it (in one way or another).

That's my free time as well, if I had to make things "just work" I'd 
build the sdk and then just ./configure and copy stuff to the image by hand.
Unfortunately I'm pretty new to qt and yocto and sooner or later things 
will have to "just work". I'm concerned that the solution I'll come up 
with will be substandard to be merged to meta-qt5, especially if I'll be 
left alone in the cold, before the time I'll have to make things "just 
work" will come and all my efforts will be lost in time like tears in 
the rain.

Still putting together the right knowledge to try to contribute a bit back.

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it



  reply	other threads:[~2015-10-15 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 20:31 qt5 toolchain Ivan Sergio Borgonovo
2015-10-13 13:11 ` Otavio Salvador
2015-10-15 16:26   ` Ivan Sergio Borgonovo
2015-10-15 16:48     ` Otavio Salvador
2015-10-15 22:03       ` Ivan Sergio Borgonovo [this message]
2015-10-16 13:59         ` Otavio Salvador

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=5620229B.9020700@webthatworks.it \
    --to=mail@webthatworks.it \
    --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.