Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt problems
Date: Tue, 25 Aug 2009 13:27:16 +0300	[thread overview]
Message-ID: <4A93BC84.7070106@gmail.com> (raw)
In-Reply-To: <91283b620908250245t1ab4fde2xef8e9b9344dfb3b7@mail.gmail.com>

Stuart Gray wrote:
> Can you show me an example of what you mean please.
>
> I know its a mess and that is part of my problem.
>
> 2009/8/25 Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
>
> > Stuart Gray wrote:
> > > Here are the bb files.
> > >
> > > qt4-embedded is the standard bb file.
> > >
> > > libmusicbrainz is the latest version of this software - to get this to
> > work
> > > I had to use oe_soinstall to include libstdc++.so.6
> > >
> > > dockamp is my own software which is the code written on Fedora Linux. I
> > > chnaged a lot of the include paths as it could not locate the files. For
> > > example:
> > >
> > > #include
> > >
> > </home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r14.1/qt-embedded-linux-opensource-src-4.5.2/include/QtNetwork/QNetworkReply>
> > > #include
> > >
> > </home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r14.1/qt-embedded-linux-opensource-src-4.5.2/include/QtNetwork/QNetworkAccessManager>
> > > #include
> > >
> > </home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r14.1/qt-embedded-linux-opensource-src-4.5.2/include/QtNetwork/QNetworkRequest>
> > >
> > > these were originally
> > > #include <QNetworkReply>
> > > etc...
> > >
> > > and then for Qt libraries I had to change:
> > >
> > > QT += QtDBusE QtNetworkE QtSqlE phononE QtXmlE
> > >
> > > from
> > >
> > > QT += dbus network sql phonon xml
> > >
> > > I have been told that qmake should take care of this.
> > >
> > > Thanks,
> > > Stuart
> > >
> > > 2009/8/24 Henning Heinold <heinold@inf.fu-berlin.de>
> > >
> > > > Hi,
> > > >
> > > > wihtout the recipe there is no chance to help you.
> > > >
> > > > Bye Henning
> > > >
> > > > _______________________________________________
> > > > Openembedded-devel mailing list
> > > > Openembedded-devel@lists.openembedded.org
> > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > > >
> > >
> > > ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >
> > You should regenerate your Makefile with oe-staged qmake.
> > PS: Your full-path includes are dirty hacks which shouldn't be used any
> > time. It's a mess.
> >
>   
Have you tried OpenEmbedded Qt/Embedded SDK [1] for building your software?

[1]: http://docs.openembedded.org/usermanual/usermanual.html#id491630



  reply	other threads:[~2009-08-25 10:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 17:55 Qt problems Stuart Gray
2009-08-24 18:30 ` Henning Heinold
2009-08-24 20:13   ` Stuart Gray
2009-08-25  9:10     ` Ihar Hrachyshka
2009-08-25  9:45       ` Stuart Gray
2009-08-25 10:27         ` Ihar Hrachyshka [this message]
2009-08-25 11:54           ` Stuart Gray
2009-08-25 14:09             ` Holger Hans Peter Freyther
2009-09-11  5:32               ` Stuart Gray
2009-09-11  8:13                 ` Ihar Hrachyshka
2009-09-11 10:51                   ` Stuart Gray
2009-09-11 11:26                     ` Ihar Hrachyshka
     [not found]                       ` <91283b620909110506p5768a960o6bf4abab421cb1b3@mail.gmail.com>
2009-09-11 12:23                         ` Stuart Gray
2009-09-11 13:01                           ` Ihar Hrachyshka
2009-09-14 11:31                             ` Stuart Gray
2009-09-14 19:02                               ` Krzysztof Kotlenga
2009-09-11 12:50                         ` Henning Heinold

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=4A93BC84.7070106@gmail.com \
    --to=ihar.hrachyshka@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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