-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix sysroot on macOS when cross-compiling and SDKROOT is set #64254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
691f645
Fix sysroot on macOS when cross-compiling and SDKROOT is set
aleksijuvani 6dc763e
Fix nits
aleksijuvani 995d985
Fix cross-compilation to macOS
aleksijuvani 2e9eba7
Set environment variables for linker instead of sysroot
aleksijuvani e715d03
Remove env vars instead of setting them to an empty string
aleksijuvani fe6d626
Ignore linker env vars set for macOS on iOS targets
aleksijuvani File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a bit of an odd interface since it actually only returns env vars which should be cleared out, not env vars which should be set. Do we know what the various tools will behave right when set to blank values which effectively disables them? The alternative would be to extend
link_env
with the ability to delete env vars as well (e.g.env_remove
).Additionally, it seems like this would also want to encompass the ios targets perhaps? For example if you set
SDKROOT
for osx orMACOSX_DEPLOYMENT_TARGET
, should those values be automatically cleared out for ios compliation in addition to macos compilation?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the variable is set to an empty string, the linker behaves as if the environment variable wasn't set. We can rework this to remove environment variables instead if that feels better.
Yes, this makes sense. We should clear
SDKROOT
if it's set to the wrong platform when targeting iOS. The value ofMACOSX_DEPLOYMENT_TARGET
doesn't appear to be meaningful in the same way thatIPHONEOS_DEPLOYMENT_TARGET
is (i.e. it doesn't appear to be used by the linker to infer the target platform), so perhaps we don't need to clear this one.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scratch that last bit actually—
MACOSX_DEPLOYMENT_TARGET
is used, but it doesn't manifest until you actually try running the executable on the simulator, which will fail withdyld: program was built for a platform that is not supported by this runtime
if the environment variable was set.