From: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Qt problems
Date: Fri, 11 Sep 2009 11:13:03 +0300 [thread overview]
Message-ID: <20090911081303.GA18964@localhost.minsk.epam.com> (raw)
In-Reply-To: <91283b620909102232me9db8dck490abb53a8ba8fff@mail.gmail.com>
On Fri, Sep 11, 2009 at 06:32:48AM +0100, Stuart Gray wrote:
> Right. I took your advice and recoded my bb file. As suggested it uses the
> standard do_compile and it is only the do_unpack that I have overridden. I
> have attached my latest .inc file.
>
> I have posted my latest problem that is very close to working, but I have
> found libraries that are not installed. The debug output basically states
> that it cannot find directory /usr/lib/qtopia. The output is shown below.
>
> NOTE: Running task 2663 of 3643 (ID: 117, /home/stuart/overo-oe/org.
> openembedded.dev/recipes/x-load/x-load_git.bb, do_compile)
> NOTE: Running task 2664 of 3643 (ID: 718,
> /home/stuart/overo-oe/user.collection/recipes/qt4/qt4-embedded_4.5.2.bb,
> do_populate_staging)
> NOTE: Running task 2665 of 3643 (ID: 720,
> /home/stuart/overo-oe/user.collection/recipes/qt4/qt4-embedded_4.5.2.bb,
> do_package)
> NOTE: The path does not
> exist:/home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r16.1/image/usr/lib/qtopia/plugins/accessible/
> NOTE: The path does not
> exist:/home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r16.1/image/usr/lib/qtopia/plugins/codecs/
> NOTE: The path does not
> exist:/home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r16.1/image/usr/lib/qtopia/plugins/graphicssystems/
> NOTE: The path does not
> exist:/home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r16.1/image/usr/lib/qtopia/plugins/inputmethods/
> NOTE: The path does not
> exist:/home/stuart/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-4.5.2-r16.1/image/usr/lib/qtopia/plugins/styles/
> NOTE: Running task 2666 of 3643 (ID: 118,
> /home/stuart/overo-oe/org.openembedded.dev/recipes/x-load/x-load_git.bb,
> do_install)
> NOTE: Running task 2673 of 3643 (ID: 9,
> /home/stuart/overo-oe/user.collection/recipes/images/omap3-console-image.bb,
> do_populate_staging)
>
> Can you please tell me how I instruct bitbake to install these directories.
>
> Regards,
> Stuart
>
>
>
> 2009/8/25 Holger Hans Peter Freyther
> <holger+oe@freyther.de<holger%2Boe@freyther.de>
> >
>
> > On Tuesday 25 August 2009 13:54:26 Stuart Gray wrote:
> > > Hi we have just solved the problem
> > .
> > No, you have not "solved" the problem. Your next problems will be uic, moc,
> > etc. not working...
> >
> >
> > >do_compile() {
> > > oenote Running our qmake work dir is $WORKING_DIR
> > > cd ${WORKING_DIR}
> > > qmake2 ${WORKING_DIR}/dockamp.pro
> > > oenote Running our libinstall SGNOTE
> > > oe_libinstall -s libQtGuiE ${OVEROTOP}/tmp/work/armv7a-angstrom-linux-
> > gnueabi/qt4-embedded-4.5.2-r14.1/qt-embedded-linux-opensource-src-4.5.2/lib
> > > oenote Running our make current dir is $PWD
> > > cd ${WORKING_DIR}
> > > make
> > > oenote Finished our qmake
> >
> >
> > Comments:
> > - Using oe_libinstall in do_compile is never ever the right thing..
> > there is
> > no need for that. Forget about the existance of oe_libinstall...
> > you
> > are just increasing the hole you are sitting in.
> > - You should add a separate recipe for the statemachine framework,
> > stage it..
> > and build a package. I might just do that now...
> >
> > Some remarks on tasks:
> > - In do_configure you configure
> > - In do_compile one is compiling
> > - In do_install one is installing to ${D}
> > - In do_stage one is staging
> >
> > The good:
> > - You are already doing "Inherit qmake2" and "inherit qt4e"... this
> > should
> > setup things correctly.
> >
> > The bad:
> > - You are invoking qmake yourself.. You should at least invoke:
> > qmake_base_do_configure... this will have QMAKESPEC set
> >
> > The ugly:
> > - I don't understand why stock do_configure is not good enough...
> > you have
> > copied everything to ${S} anyway. So the stock do_configure should
> > find your pro file? Is that not the case? Which initial problem
> > did
> > you try to solve?
> >
> >
> > do you hang out on irc? it might be more easy to go through all these in
> > real
> > time.
> >
> > z.
> >
There is nothing wrong in log snipper you've shown us. Describe your
problem correctly and show us the code (.bb I mean).
next prev parent reply other threads:[~2009-09-11 8:14 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
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 [this message]
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=20090911081303.GA18964@localhost.minsk.epam.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