SDK (isysroot) selection "rules"? (Qt5 related)

[Ryan Schmidt]

On Jun 18, 2015, at 4:50 AM, René J.V. Bertin wrote:

> I've ran into a symbol (NSMetadataQueryUpdateAddedItemsKey) visibility issue that I can most likely trace back to the fact that for some reason I don't grasp, the build process decided to use the 10.10 SDK while I'm running 10.9 . I don't see anything in the options I used that would have caused this explicitly, so I'm guessing this is some form of default behaviour.
> 
> The question is, is that assessment correct and if so, who's default is this? Xcode's, or MacPorts'?
> 
> BTW, I'm seeing this with Qt Creator 3.4.1 built against Qt 5.4.2 through MacPorts. The official snapshot builds do not show this issue, which suggests that either they're built with explicit specification of the SDK to use, or it's a MacPorts issue. I tried an archivefetch of qt5-creator-mac, but 3.4.1 isn't available in binary build...

In most cases, MacPorts doesn't tell build systems to use an SDK.

The cmake portgroup is an exception, because the cmake build system requires that an SDK be specified if a MACOSX_DEPLOYMENT_TARGET is specified, which MacPorts does do.

Xcode projects often include hardcoded values for the SDK, deployment target, and architectures, so if this is using an Xcode project file, check for that. If not, check the project's build system.