From: "Markus Wolters" <MarkusWolters@gmx.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] qmake broken after ptxdist version switch?
Date: Mon, 21 Oct 2013 13:19:46 +0200 (CEST) [thread overview]
Message-ID: <trinity-3d6e0646-9ec1-4bea-b469-96c1a0f91d8b-1382354386046@3capp-gmx-bs46> (raw)
In-Reply-To: <201310211239.07227.jbe@pengutronix.de>
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...
> Gesendet: Montag, 21. Oktober 2013 um 12:39 Uhr
> Von: "Jürgen Beisert" <jbe@pengutronix.de>
> An: ptxdist@pengutronix.de
> Cc: "Markus Wolters" <MarkusWolters@gmx.de>
> Betreff: Re: [ptxdist] qmake broken after ptxdist version switch?
>
> Hi Markus,
>
> On Monday 21 October 2013 11:55:21 Markus Wolters wrote:
> > [...]
> > Does anyone have an idea what I'm doing wrong/ how to fix this?
>
> Did you re-build the whole project after the PTXdist version switch?
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K. | Juergen Beisert |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-10-21 11:19 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 [this message]
2013-10-21 13:26 ` Tim Sander
2013-10-24 8:49 ` Michael Olbrich
2013-10-24 12:10 ` Markus Wolters
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-3d6e0646-9ec1-4bea-b469-96c1a0f91d8b-1382354386046@3capp-gmx-bs46 \
--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