Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add Qt5 packages
Date: Fri, 1 Mar 2013 17:54:37 +0100	[thread overview]
Message-ID: <20130301175437.085605b5@skate> (raw)
In-Reply-To: <5130D9D8.5000603@je-eigen-domein.nl>

Dear Floris Bos,

On Fri, 01 Mar 2013 17:39:52 +0100, Floris Bos wrote:

> > If so, then I can include a path that makes fonts.path be 
> > $$[QT_INSTALL_PREFIX]/share/fonts/. But Qt has some fonts in 
> > lib/fonts/, so maybe we should research how to install them, at least 
> > optionally, because they have some fonts in the special Qt format, 
> > which may be useful if you don't have a TTF font renderer available. 
> 
> Sounds good to me.

Do you plan on researching how to get the fonts bundled with Qt
installed, or you want me to look into that?


> Well, I never really understood the need for the glue code in the first 
> place either.
> Would rather have seen that they filled a bug report with the GPU 
> vendor, and questioned why one needs to call some vendor specific 
> function like bcm_host_init(), instead of just the standardized function 
> eglInitialize() before
> any EGL/OpenGL ES function works...
> And used some runtime detection system for vendor specific extras like 
> hardware accelerated mouse cursor.
> So that ARM Linux distributions could ship universal Qt packages that 
> could work on more then one device.

Indeed.

> Anyway, just filling in the location of the glue code in the buildroot 
> qmake.conf when the rpi-userland package is selected might be the most 
> practical solution.
> Will submit a sample patch to illustrate shortly.

That would be very nice!

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-03-01 16:54 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 23:25 [Buildroot] [PATCH] Add Qt5 packages Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 01/30] pcre: add support for 16 bits and 32 bits variants Thomas Petazzoni
2013-02-28  0:00   ` Gustavo Zacarias
2013-02-28  8:28     ` Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 02/30] x11r7/xcb-util: bump to 0.3.9 Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 03/30] x11r7/xcb-util-wm: new package Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 04/30] x11r7/xcb-util-image: " Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 05/30] package: create virtual package for libGLES, libOpenVG and libEGL Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 06/30] rpi-userland: provides OpenGL ES, EGL and OpenVG Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 07/30] rpi-userland: add .pc files for OpenGLESv2 and EGL libs Thomas Petazzoni
2013-02-27 23:25 ` [Buildroot] [PATCH 08/30] jpeg: convert to a real package Thomas Petazzoni
2013-02-28 22:13   ` Samuel Martin
2013-02-28 23:13     ` Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 09/30] qt5: base infrastructure Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 10/30] qt5: add macro to fixup Qt5 .la and .prl files Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 11/30] qt5base: new package Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 12/30] qt5base: add GUI support Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 13/30] qt5base: support debug or release modes Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 14/30] qt5base: add OpenSSL support Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 15/30] qt5base: add eglfs graphics backend Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 16/30] qt5base: add support for fontconfig, png, jpeg, gif Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 17/30] qt5base: add D-Bus support Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 18/30] qt5base: add glib support Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 19/30] qt5base: add support to build against ICU Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 20/30] qt5: factor Qt5 version Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 21/30] qt5/qt5svg: new package Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 22/30] qt5/qt5script: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 23/30] qt5/qt5imageformats: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 24/30] qt5/qt5xmlpatterns: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 25/30] qt5/qt5jsbackend: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 26/30] qt5/qt5declarative: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 27/30] qt5/qt5graphicaleffects: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 28/30] qt5/qt5multimedia: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 29/30] qt5/qt5quick1: " Thomas Petazzoni
2013-02-27 23:26 ` [Buildroot] [PATCH 30/30] qt5/qt5webkit: " Thomas Petazzoni
2013-03-01  2:26 ` [Buildroot] [PATCH] Add Qt5 packages Floris Bos
2013-03-01  4:25   ` Daniel Price
2013-03-01  9:19     ` Thomas Petazzoni
2013-03-01  9:08   ` Thomas Petazzoni
2013-03-01 16:39     ` Floris Bos
2013-03-01 16:54       ` Thomas Petazzoni [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=20130301175437.085605b5@skate \
    --to=thomas.petazzoni@free-electrons.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