mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2013.01.0 released
Date: Wed, 09 Jan 2013 10:41:43 +0100	[thread overview]
Message-ID: <1534407.ouy6H2vxQj@dabox> (raw)
In-Reply-To: <20130108211031.GG13335@pengutronix.de>

Hi MIchael
> > I just found out that the qt4 package does not contain any isystem flags
> > in
> > qmake conf flags anymore (QMAKE_CFLAGS,QMAKE_CXXFLAGS,QMAKE_LFLAGS).
> > 
> > So a external build with the qmake-cross fails. If i remember correctly
> > there where some changes in the library handling? I guess this is
> > related?
> This was changed in the November release with the toolchain wrapper.
> Basically gcc and friends are no longer called directly, but via wrapper
> scripts that add those flags.
> Hmmm, you could try adding sysroot-host/lib/wrapper/ to PATH and set some
> environment variables. Probably all PTXDIST_* variables in
> <ptxdist>/scripts/wrapper/libwrapper.sh
> "ptxdist print <VARIABLE_NAME>" should give you the value to set.
That works but i found the old solution where the config has been imprinted 
into the qmake.conf much more comfortable. Any chance to get these back into 
the qmake.conf?

I had to set the path and the following variables:
$PTXDIST_CROSS_CPPFLAGS  $PTXDIST_CROSS_LDFLAGS   $PTXDIST_PLATFORMCONFIG

Best regards
Tim

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-01-09  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 10:40 Michael Olbrich
2013-01-08 16:00 ` Tim Sander
2013-01-08 21:10   ` Michael Olbrich
2013-01-09  9:41     ` Tim Sander [this message]
2013-01-09 15:23       ` Michael Olbrich
2013-01-09 17:03         ` Tim Sander

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=1534407.ouy6H2vxQj@dabox \
    --to=tim@krieglstein.org \
    --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