From: "Markus Wolters" <MarkusWolters@gmx.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] qmake broken after ptxdist version switch?
Date: Thu, 24 Oct 2013 14:10:47 +0200 (CEST) [thread overview]
Message-ID: <trinity-63383875-a993-438d-ac5a-5e57d83bc836-1382616647816@3capp-gmx-bs31> (raw)
In-Reply-To: <20131024084959.GC9225@pengutronix.de>
Hello Michael,
I though choosing the right toolchain isn't "my problem", as I use the ptxdist g++ specs:
".../sysroot-cross/bin/qmake $1 -spec .../sysroot-target/usr/mkspecs/qws/linux-ptx-g++ -r"
Wouldn't it be better to fix it at that point?
Markus
> Gesendet: Donnerstag, 24. Oktober 2013 um 10:49 Uhr
> Von: "Michael Olbrich" <m.olbrich@pengutronix.de>
> An: ptxdist@pengutronix.de
> Betreff: Re: [ptxdist] qmake broken after ptxdist version switch?
>
> Hi,
>
> On Mon, Oct 21, 2013 at 03:26:22PM +0200, Tim Sander wrote:
> > Am Montag, 21. Oktober 2013, 13:19:46 schrieb Markus Wolters:
> > > Yes, I did.
> > > I just figured out, that providing the necessary libs in my pro file fix the
> > > problem. But that can't be the right way to fix it, I think?! And it seems
> > > to be no qmake problem...
> > I think the older qt mkspecs got their include path patched. This changed
> > somehow in newer qt versions. So you might need to restore the old behavior
> > by copying the old rules sed statement to the new file or add some ptxdist env
> > variables.
> >
> > I have no idea why the pengutronix guys changed the behavior. But i think its
> > annoying as you can't just use the right qmake and be happy without env vars.
>
> Are you talking about building Qt project outside PTXdist? If that is the
> case then you need to use <BSP>/platform-<something>/sysroot-host/lib/wrapper
> in PATH instead of the toolchain.
>
> Michael
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-10-24 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 9:55 Markus Wolters
2013-10-21 10:39 ` Jürgen Beisert
2013-10-21 11:19 ` Markus Wolters
2013-10-21 13:26 ` Tim Sander
2013-10-24 8:49 ` Michael Olbrich
2013-10-24 12:10 ` Markus Wolters [this message]
2013-10-24 22:11 ` Michael Olbrich
2013-10-26 12:14 ` Markus Wolters
2013-10-28 8:18 ` Schenk, Gavin
2013-11-04 7:38 ` Markus Wolters
2013-11-04 8:17 ` Schenk, Gavin
2013-12-03 8:37 ` Markus Wolters
2013-12-04 7:52 ` Schenk, Gavin
2013-12-04 8:37 ` Jürgen Beisert
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=trinity-63383875-a993-438d-ac5a-5e57d83bc836-1382616647816@3capp-gmx-bs31 \
--to=markuswolters@gmx.de \
--cc=ptxdist@pengutronix.de \
/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