Force Xcode SDK instead of CLI SDK?

Ryan Schmidt ryandesign at
Fri Nov 20 22:51:08 UTC 2020

On Nov 20, 2020, at 16:30, Aaron Madlon-Kay wrote:

> On Fri, Nov 20, 2020 at 11:47 PM Joshua Root wrote:
>> Unfortunately it isn't really. The result of not using an SDK matching
>> your OS version is that autoconf (and cmake etc.) detects functions that
>> aren't available at runtime, causing crashes because checking for
>> weak-linked symbols is very uncommon in the world outside of Mac-centric
>> developers.
> Pardon my ignorance: We're talking about a `use_xcode yes` port


> (presumably built with xcodebuild);

That's not a given.

> are autoconf and cmake going to be a problem?

If the port uses them, quite possibly.

> (I actually don't know if xcodebuild uses these under the
> hood or something.)

It doesn't.

> If the problem is then that vendored dependencies might be built with
> autoconf or cmake,

I don't think we had thought of such a situation, but I guess it could arise.

> would it make sense to have something like a
> `use_xcode_only yes` flag, to allow ports that *don't* have such deps
> and are Mac-centric to opt into the behavior?

I don't know.

More information about the macports-dev mailing list