From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2013.01.0 released
Date: Wed, 09 Jan 2013 18:03:55 +0100 [thread overview]
Message-ID: <1921199.3oymQ4BniQ@dabox> (raw)
In-Reply-To: <20130109152339.GK13335@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?
>
> No, but I'd like to get to the point where adding sysroot-host/lib/wrapper/
> to PATH is enough.
Well sounds reasonable but still its usability is inferior to just have these
settings within qmake.conf for development of projects with ptxdist as base.
When switching projects you just call a different qmake from a different ptxdist
tree. Done. With the wrapper you have to adapt the $PATH otherwise you will
end up with probably strange builds?
Best reagards
Tim
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-01-09 17:03 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
2013-01-09 15:23 ` Michael Olbrich
2013-01-09 17:03 ` Tim Sander [this message]
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=1921199.3oymQ4BniQ@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