From: prabindh <prabu@ti.com>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Mon, 18 Feb 2013 20:18:49 -0800 (PST) [thread overview]
Message-ID: <1361247529229-40702.post@n4.nabble.com> (raw)
In-Reply-To: <20130114120416.42b34d77@skate>
Hello Thomas,
On below - how can I help ? Note that sgxconfiguro, while useful in
autoconfigure for egl/gles2, for Qt5 is not especially useful as it fails
because of missing icu detection via autoconfig. So I reverted back to
regular configurations via qmake.conf at this time.
Thomas Petazzoni-2 wrote
> Dear Daniel Nystr?m,
>
> On Mon, 14 Jan 2013 11:50:48 +0100, Daniel Nystr?m wrote:
>> Very appreciated! Do you know if there is OpenGL support for i.e. OMAP
>> (PowerVR) in Buildroot and, if that's the case, will Qt5 make use of
>> that?
>>
>> I once started with a PowerVR package for BR, but got interrupted and
>> never
>> had time to catch up. :/
>
> For now, I have added support for the eglfs backend of Qt5, by using
> the OpenGLESv2 and EGL implementations for the RasberryPi. I've also
> added in the process virtual packages for libglesv2, libegl and
> libopenvg, so that multiple implementations can be packaged for those
> APIs.
>
> However, I haven't looked at packaging the OMAP PowerVR stuff for now.
> So if anyone wants to have a look, would be nice.
>
> I currently have https://github.com/prabindh/sgxconfiguro (a set of
> pkg-config files that apparently make it a bit easier to use the SGX
> stuff), and http://gpupowered.org/node/8 opened in my browser, as
> useful links regarding SGX stuff. Just in case someone wants to start
> working on this.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
> _______________________________________________
> buildroot mailing list
> buildroot@
> http://lists.busybox.net/mailman/listinfo/buildroot
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Currently-packaging-Qt5-tp38584p40702.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-02-19 4:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04 ` Thomas Petazzoni
2013-02-19 4:18 ` prabindh [this message]
2013-02-19 15:29 ` Thomas Petazzoni
2013-05-20 3:31 ` prabindh
2013-05-22 11:55 ` Sundareson, Prabindh
2013-05-22 12:17 ` Thomas Petazzoni
2013-05-22 12:23 ` prabindh
2013-05-22 12:31 ` Thomas Petazzoni
2013-05-22 12:36 ` prabindh
2013-05-22 13:06 ` Thomas Petazzoni
2013-05-22 13:26 ` Sundareson, Prabindh
2013-05-22 13:30 ` Thomas Petazzoni
2013-05-22 13:35 ` prabindh
2013-05-22 14:04 ` Thomas Petazzoni
2013-05-22 14:18 ` Spenser Gilliland
2013-05-22 14:39 ` Thomas Petazzoni
2013-05-22 15:57 ` prabindh
2013-05-22 17:33 ` Spenser Gilliland
2013-05-23 20:38 ` Wojciech Sleńska
2013-05-22 12:16 ` Thomas Petazzoni
2013-05-22 12:21 ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45 ` Thomas Petazzoni
2013-01-14 12:48 ` Sagaert Johan
2013-01-14 13:10 ` Thomas Petazzoni
2013-01-17 9:03 ` Arnout Vandecappelle
2013-02-06 9:56 ` Daniel Nyström
2013-02-06 10:04 ` Thomas Petazzoni
2013-02-06 10:12 ` Frédéric COIFFIER
2013-02-06 10:43 ` Thomas Petazzoni
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=1361247529229-40702.post@n4.nabble.com \
--to=prabu@ti.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox