On Tue, November 06, 2012 08:21:24 PM Oswald Buddenhagen wrote: > On Tue, Nov 06, 2012 at 06:17:04PM +0100, Thomas Senyk wrote: > > I got a self-written mkspec for the rasp-pi and everything is working as > > expected. > > > > With one exception, for external applications he is not adding the proper > > > > -Wl,-rpath,<prefix> > > > > The problem is that: > > cat /usr/local/Trolltech/Qt5-rasp-pi-2/mkspecs/modules/qt_lib_* |grep > > rpath > > > > returns nothing. > > that's not the problem. > > > If you add a module to "QT" in your project file, qt_functions.prf:93 will add: > > -Wl,-rpath,<SYSROOT!!>/<prefix> > > *that* is the problem. > the fallback path doesn't account for sysroots. and it cannot do that > cleanly. so it should be scrapped.
but isn't that what the patch tried to do by using $$[QT_INSTALL_LIBS/raw] ? QT_.../raw variables are variables "without SYSROOT-prefix", right? I've no real clue about what qt_module.prf does and how it works ... but if it's the one taking care about preparing the installed versions of module-pri- files then the second part of the patch looks like dealing with the root problem. (the fact that QT.module.rpath) is missing. IMO the problem is not the fallback in qt_function.prf, it's the fact that the fallback is trigger. ... but hey, I'm clearly no expert on the whole module-mkspecs-architecture .. what ever you decide is good with me as long as I get a proper -rpath in the end ;) Greest Thomas > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
