All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with Qt when using commit libglib2: Bump libglib2 to 2.36.1 ( no touchscreen )
Date: Fri, 23 Aug 2013 13:18:19 +0200	[thread overview]
Message-ID: <20130823131819.6035af8e@skate> (raw)
In-Reply-To: <16F215BDBD9D49C49E858122318082E4@JohanW7>

Dear Sagaert Johan,

On Fri, 23 Aug 2013 10:28:46 +0200, Sagaert Johan wrote:

> For some unknown reason, this commit (1232fe4d22e15a31385c69f02570f036b738b6b2) seems to break Qt484 at runtime.
> Qt just does not react any longer to the touchscreen.There are no warnings.
> Everything else is the same, i see no obvious relation between this commit and the trouble i have.
> Just have no clue what the binding is between libglib2 and Qt ?

Qt has a glib integration. If you're not using it, you could disable it
by replacing:

ifeq ($(BR2_PACKAGE_LIBGLIB2),y)
QT_CONFIGURE_OPTS += -glib
QT_DEPENDENCIES += libglib2
else
QT_CONFIGURE_OPTS += -no-glib
endif

by just:

QT_CONFIGURE_OPTS += -no-glib

This would at least help us confirm that the problem is indeed here.

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-08-23 11:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  8:28 [Buildroot] Problem with Qt when using commit libglib2: Bump libglib2 to 2.36.1 ( no touchscreen ) Sagaert Johan
2013-08-23 11:18 ` Thomas Petazzoni [this message]
2013-08-23 12:19   ` Sagaert Johan
2013-08-23 14:50   ` Sagaert Johan
2013-08-23 15:46   ` Sagaert Johan

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=20130823131819.6035af8e@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 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.