Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@radarhere
Copy link
Member

Resolves #5827

#5624 changed setup.py on macOS to prefer the command line tools SDK over xcrun --show-sdk-path. Apparently that was too far however, as conda-forge would like to specify the SDK path.

So instead, this PR scales back #5624 to only use the command line tools SDK when xcrun --show-sdk-path returns the default path of /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk

@hugovk
Copy link
Member

hugovk commented Nov 11, 2021

build_extensions() is 500 lines long, shall we put this changed chunk into its own function?

@radarhere
Copy link
Member Author

Ok, sure, done.

@h-vetinari
Copy link

I tested this PR in conda-forge/pillow-feedstock#102, and it works fine! 🥳

Thanks a lot for the quick handling, much appreciated! :)

@hugovk
Copy link
Member

hugovk commented Nov 12, 2021

Installs fine and tests pass for me on macOS Monterey 12.0.1 with defaults:

$  xcrun --show-sdk-path
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk

Thanks both!

The next scheduled release is 9.0.0 on 2nd January.

@hugovk hugovk merged commit 4fca3b4 into python-pillow:main Nov 12, 2021
@radarhere radarhere deleted the macos_sdk_path branch November 12, 2021 12:01
@radarhere radarhere changed the title Only prefer command line tools SDK on macOS over the default Only prefer command line tools SDK on macOS over default MacOSX SDK Nov 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow setting specific SDK on macOS

3 participants