Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5][PATCH 1/2] nativesdk-qtbase: add nativesdk version of qtbase necessary for SDK tools
Date: Thu, 6 Feb 2014 20:54:14 -0500	[thread overview]
Message-ID: <20140207015414.GL31128@edge> (raw)
In-Reply-To: <CAP71Wjx52AHWurONaP7Fsq9A9jGKuy1S9+xviYQ7+iCUGYnRdw@mail.gmail.com>

On Fri, Feb 07, 2014 at 01:15:34AM +0100, Nicolas Dechesne wrote:
> hi,
> 
> On Tue, Nov 26, 2013 at 2:47 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> > +do_install() {
> > +    # Fix install paths for all
> > +    find -name "Makefile*" | xargs sed -i "s,(INSTALL_ROOT)${STAGING_DIR_NATIVE}${STAGING_DIR_NATIVE},(INSTALL_ROOT)${STAGING_DIR_NATIVE},g"
> > +
> > +    # switch back the proper qmake
> > +    rm ${B}/bin/qmake
> > +    mv ${B}/bin/qmake-real ${B}/bin/qmake
> > +
> > +    oe_runmake install INSTALL_ROOT=${D}
> > +
> > +    # for modules which are still using syncqt and call qtPrepareTool(QMAKE_SYNCQT, syncqt)
> > +    # e.g. qt3d, qtwayland
> > +    ln -sf syncqt.pl ${D}${OE_QMAKE_PATH_QT_BINS}/syncqt
> > +}
> 
> about this patch (which was merged already), i am wondering if this is
> okay to do something like above. basically in the do_install task we
> are 'corrupting' the output of the do_compile task. Here we remove
> ${B}/bin/qmake for example. so if the do_install fails for whatever
> reason, it will never be able to resume properly, since ${B} is no
> longer what it should be after a legitimate do_compile. i was
> debugging some weird build issues, and I am wondering if my problem
> doesn't come from that...

Hmm, never thought of it like that. I guess there are couple options:

1. Make the qmake switch above at the end of do_compile instead
2. Keep it in do_install, but manipulate ${D} instead of ${B} by installing 
${B}/qmake-real into ${D}/qmake

-- 
Denys


  reply	other threads:[~2014-02-07  1:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  1:47 [meta-qt5][PATCH 0/2] Add nativesdk tools for Qt5 SDK Denys Dmytriyenko
2013-11-26  1:47 ` [meta-qt5][PATCH 1/2] nativesdk-qtbase: add nativesdk version of qtbase necessary for SDK tools Denys Dmytriyenko
2013-12-12 14:40   ` Martin Jansa
2013-12-12 14:45     ` Denys Dmytriyenko
2013-12-12 14:58       ` Martin Jansa
2013-12-12 15:14         ` Denys Dmytriyenko
2013-12-12 15:31           ` Martin Jansa
2013-12-12 15:36             ` Denys Dmytriyenko
2014-02-07  0:15   ` Nicolas Dechesne
2014-02-07  1:54     ` Denys Dmytriyenko [this message]
2014-02-07  9:27       ` Nicolas Dechesne
2013-11-26  1:47 ` [meta-qt5][PATCH 2/2] nativesdk-qttools: add nativesdk version of qttools " Denys Dmytriyenko
2013-11-26  2:14   ` Martin Jansa
2013-11-26  4:33   ` [meta-qt5][PATCHv2 " Denys Dmytriyenko

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=20140207015414.GL31128@edge \
    --to=denys@ti.com \
    --cc=nicolas.dechesne@linaro.org \
    --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