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 [email protected]
