From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: qt4e-demo-image with meta-fsl-arm: successful build?
Date: Mon, 10 Jun 2013 16:52:04 +0100 [thread overview]
Message-ID: <2108518.UseegX70O5@helios> (raw)
In-Reply-To: <CAGDS+nkNmA+BctPBDVoH_dHxKJqJ+ECLy5Rv0Yy=9HgOnd=+zg@mail.gmail.com>
On Monday 10 June 2013 08:43:38 Steve Sakoman wrote:
> On Mon, Jun 10, 2013 at 6:07 AM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Mon, 10 Jun 2013 05:58:42 -0700,
> >
> > Steve Sakoman <sakoman@gmail.com> a écrit :
> >> I haven't begun debugging yet, but I had 2 initial thoughts as to why
> >> the X error message:
> >>
> >> 1. The qtdemo init seems to be written to support both x and x-free
> >> setups, so perhaps the init is getting confused
> >> 2. I had built the x11-free version of qt prior to the qte version, so
> >> perhaps that causes the issue
> >>
> >> I started a clean build just in case #2 is the cause.
> >
> > OK #2 is clearly a situation I avoid here as this created me some
> > troubles in the past.
>
> And it created issues for me too :-)
>
> A clean build of qt4e-demo-image works. A clean build of a similar
> image based on qt4-x11-free however is broken as described in my
> original post.
>
> Clearly one must choose either qt4-x11-free or qt4e, having both in
> the same build setup is broken (perhaps by design)
I can say this is not by design. The two should be able to coexist (which is
why the library names are different); if they currently cannot we need to figure
out why that is and get it fixed.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-06-10 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 3:19 qt4e-demo-image with meta-fsl-arm: successful build? Steve Sakoman
2013-06-10 7:45 ` Eric Bénard
2013-06-10 12:58 ` Steve Sakoman
2013-06-10 13:03 ` Steve Sakoman
2013-06-10 13:07 ` Eric Bénard
2013-06-10 15:43 ` Steve Sakoman
2013-06-10 15:52 ` Paul Eggleton [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=2108518.UseegX70O5@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sakoman@gmail.com \
/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