Skip to content

Conversation

@nickclark2016
Copy link
Member

What does this PR do?

Resolves #2416 by making it so that behavior for bundles does not affect the binary extension, instead providing an API to set the bundle's extension.

How does this PR change Premake's behavior?

No changes to XCode functionality, changes gmake's behavior to follow the expected pattern binary target extensions. Bundle extensions API is provided to instead provide functionality to the bundle name and path, rather than the binary itself.

Anything else we should know?

No

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

@nickclark2016 nickclark2016 requested a review from a team May 23, 2025 05:18
Jarod42

This comment was marked as outdated.

@nickclark2016 nickclark2016 merged commit b0d5363 into premake:master May 28, 2025
93 of 96 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Built macOS binaries should not have any file extension

3 participants