All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH] meta-toolchain-arago-qte: Fix location for host Qt tools
Date: Thu, 21 Nov 2013 12:47:42 -0500	[thread overview]
Message-ID: <20131121174742.GQ29952@edge> (raw)
In-Reply-To: <20131121044356.GH29952@edge>

On Wed, Nov 20, 2013 at 11:43:56PM -0500, Denys Dmytriyenko wrote:
> On Mon, Nov 18, 2013 at 04:20:14PM -0500, Denys Dmytriyenko wrote:
> > On Mon, Nov 18, 2013 at 01:41:00PM -0500, Cooper Jr., Franklin wrote:
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Dmytriyenko, Denys
> > > > Sent: Monday, November 18, 2013 12:33 PM
> > > > To: Cooper Jr., Franklin
> > > > Cc: meta-arago@arago-project.org
> > > > Subject: Re: [meta-arago] [PATCH] meta-toolchain-arago-qte: Fix location for
> > > > host Qt tools
> > > > 
> > > > On Sun, Nov 17, 2013 at 12:06:53PM -0600, Franklin S. Cooper Jr wrote:
> > > > > * By default Qt5 is looking at cortexa8hf-vfp-neon-oe-linux-gnueabi/bin
> > > > instead
> > > > >   of the proper location i686-arago-linux/usr/bin/qt5.
> > > > > * Update qmake.conf to insure qmake looks at the proper location for host
> > > > >   binaries.
> > > > 
> > > > What is this needed for exactly? I hadn't had any issues using qmake and
> > > > command-line build with the v3 of the patches. Is it specific to QtCreator?
> > 
> > > [Franklin] Building via command line. Some reason qmake thinks moc is 
> > > located at cortexa8hf-vfp-neon-oe-linux-gnueabi/bin which resulted in a file 
> > > not found error. Im not sure when moc is needed but when I tried to build 
> > > the thermostat demo from src I ran into this issue.
> > 
> > I'm looking into this now and playing with the idea of packaging qt.conf that 
> > gets created during the nativesdk build. Although that one maybe an overkill. 
> > If that doesn't work, I'll push an updated version of this patch...
> 
> Sorry, took me a bit longer due to some extra testing, but it appears I can't 
> re-use the generated qt.conf in this Canadian cross-compilation when 3 archs 
> are involved - config file for A->B cross is different from B->C. I just sent 
> the updated patch that sets couple host variables in qt.conf inside SDK, that 
> should cover most of other cases.

Franklin,

Have you been able to do any tests with the updated patch I sent last night? 
If it works for you, I'd like to push it along with the initial Qt5 SDK 
patches to meta-arago/master.

-- 
Denys


> > > > > Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
> > > > > ---
> > > > >  .../recipes-core/meta/meta-toolchain-arago-qte.bb  |    8 +++++++-
> > > > >  1 files changed, 7 insertions(+), 1 deletions(-)
> > > > >
> > > > > diff --git a/meta-arago-extras/recipes-core/meta/meta-toolchain-arago-qte.bb
> > > > b/meta-arago-extras/recipes-core/meta/meta-toolchain-arago-qte.bb
> > > > > index e3bf80f..6220578 100644
> > > > > --- a/meta-arago-extras/recipes-core/meta/meta-toolchain-arago-qte.bb
> > > > > +++ b/meta-arago-extras/recipes-core/meta/meta-toolchain-arago-qte.bb
> > > > > @@ -5,7 +5,7 @@ TOOLCHAIN_SUFFIX ?= "-qte-sdk"
> > > > >
> > > > >  require meta-toolchain-arago.bb
> > > > >
> > > > > -PR = "r16"
> > > > > +PR = "r17"
> > > > >
> > > > >  # There could be qt5, qt4e and qt4x11 providers, but we don't support
> > > > qt4x11 for now
> > > > >  QT_DIR_NAME = "${@base_conditional('QT_PROVIDER', 'qt5', 'qt5', 'qtopia',
> > > > d)}"
> > > > > @@ -46,6 +46,12 @@ toolchain_create_sdk_env_script_append() {
> > > > >  	echo 'Libraries = $(OE_QMAKE_LIBDIR_QT)' >> $qt_conf
> > > > >  	echo 'Headers = $(OE_QMAKE_INCDIR_QT)' >> $qt_conf
> > > > >
> > > > > +	if [ "${QT_PROVIDER}" = "qt5" ]
> > > > > +	then
> > > > > +		echo 'HostBinaries = ../${SDK_SYS}/usr/bin/qt5' >> $qt_conf
> > > > > +	fi
> > > > > +
> > > > > +
> > > > >  	# make a symbolic link to mkspecs for compatibility with Nokia's SDK
> > > > >  	# and QTCreator
> > > > >  	(cd ${SDK_OUTPUT}/${SDKTARGETSYSROOT}; ln -sf
> > > > .${QT_MKSPECS_LOCATION}/${QT_DIR_NAME}/mkspecs mkspecs;)
> > > > > --
> > > > > 1.7.0.4
> > > > >
> > > > > _______________________________________________
> > > > > meta-arago mailing list
> > > > > meta-arago@arago-project.org
> > > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2013-11-21 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 18:06 [PATCH] meta-toolchain-arago-qte: Fix location for host Qt tools Franklin S. Cooper Jr
2013-11-17 17:07 ` Cooper Jr., Franklin
2013-11-18 18:32 ` Denys Dmytriyenko
2013-11-18 18:41   ` Cooper Jr., Franklin
2013-11-18 21:20     ` Denys Dmytriyenko
2013-11-21  4:43       ` Denys Dmytriyenko
2013-11-21 17:47         ` Denys Dmytriyenko [this message]
2013-11-21 18:20           ` Cooper Jr., Franklin

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=20131121174742.GQ29952@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.