You don't need to set QMAKE_MAC_SDK unless you require a specific SDK version. The SDK is resolved a qmake time to the latest SDK installed, and the result is cached in .qmake.stash. If you upgrade your Xcode, you'll likely have a newer SDK, and may miss the original SDK that was resolved and cached, in which case you need to do a clean build. A clean build means wiping your entire build dir, eg rm -Rf builddir. Or if you want to be a bit more precise, rm .qmake.stash .qmake.cache
tor arne On 07/10/15 17:37, Sherif Ghali 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 [email protected] http://lists.qt-project.org/mailman/listinfo/interest
