Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt library difference between E.so and just .so
Date: Tue, 4 Dec 2012 18:19:48 +0100	[thread overview]
Message-ID: <20121204181948.60bfbd4e@eb-e6520> (raw)
In-Reply-To: <CADKZYYJFAKFs5KmSbcU7o=wkWi1_wOVc6MhgZrOdALgr_iva+A@mail.gmail.com>

Hi Santhosh,

Le Sat, 1 Dec 2012 16:27:54 -0600,
Santhosh Ramani <srcoolz@gmail.com> a ?crit :
> I'm using buildroot 2012.08 to create rootfs for AM335x device and would
> like to compile in Qt libraries. I went through make menuconfig and I get
> libraries for Qt 4.8.2. However, when I try and run some of the same
> examples from the TI SDK it complains that it can't find *libQtGuiE.so.4.7.2
> *.
> 
TI'SDK is generated using Yocto/OpenEmbedded which allows the creation
of both Qt Embedded _and_ Qt for Xorg librairies. In order to make
the difference between both libraries which may both be integrated in
the same SDK, the Qt Embedded libraries have the 'E' suffix and the
SDK provides the right config files to make qmake happy.
So if you generate a rootfs using buildroot, you need to compile the
examples with buildroot's toolchain to have a consistent library naming.

Best regards,
Eric

  parent reply	other threads:[~2012-12-04 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01 22:27 [Buildroot] Qt library difference between E.so and just .so Santhosh Ramani
2012-12-02  1:06 ` Thiago A. Corrêa
2012-12-02  1:44   ` Santhosh Ramani
2012-12-04 16:25     ` Santhosh Ramani
2012-12-04 16:43     ` Thiago A. Corrêa
2012-12-04 17:19 ` Eric Bénard [this message]
2012-12-05 18:46   ` Santhosh Ramani
2012-12-05 20:07     ` Santhosh Ramani

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=20121204181948.60bfbd4e@eb-e6520 \
    --to=eric@eukrea.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