Seems editing the clang_64/mkspecs/qdevice.pri will allow you to get around this without rebuilding Qt, you just have to do a clean rebuild also.
http://stackoverflow.com/questions/25940368/qt5-target-conditionals-not-found/25962088#25962088 On Wed, Oct 7, 2015 at 8:37 AM, Sherif Ghali <sherif.ghal...@gmail.com> wrote: > Thanks, Thiago. Let me summarize what it was about on my side. > > A couple of issues are at play once one upgrades to XCode 7.0.x. The > following solved them on Yosemite (10.10); YMMV. > > First off, to solve a problem that I no longer recall, I needed to add one > of > mac::QMAKE_MAC_SDK = macosx10.9 > mac::QMAKE_MAC_SDK = macosx10.10 > to some .pro files, as well as > export > SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk > to .bash_profile. Neither should be there. > > After the update to XCode, you'll see that > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/ > has replaced > > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk > > In the existing Qt (5.4.2) there were pointers to > (/Applications/.../MacOSX10.10.sdk) that Qt inserted during its > installation. I don't know if it's possible to remedy this in place, but > re-installing Qt (still 5.4.2) after the XCode update made Qt point to > .../SDKs/MacOSX10.11.sdk/. Notice that XCode 7 uses MacOSX10.11.sdk even if > one is still on Yosemite. > > Sherif > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
