fix Clang LTO archiver selection on Apple platforms - #2761
Merged
Conversation
Jarod42
approved these changes
Aug 5, 2026
samsinsane
approved these changes
Aug 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Fixes Clang LTO builds on Apple platforms where Premake incorrectly selected
llvm-ar, which is not provided by the default Apple toolchain. The Apple toolchain already uses LLVM, but the executable name isar.How does this PR change Premake's behavior?
On macOS, Premake now uses the system
arfor static libraries. Other versioned toolsets, such asclang-16, retain the existing behavior. Other platforms continue to usellvm-arwhen LTO is enabled.Anything else we should know?
I just made my project build pass with LTO on, didn't test it fully.
Did you check all the boxes?
closes #XXXXin comment to auto-close issue when PR is merged)You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!