Fix vs200x_vcproj to properly handle NoManifest#2461
Merged
nickclark2016 merged 1 commit intopremake:masterfrom Apr 26, 2025
Merged
Fix vs200x_vcproj to properly handle NoManifest#2461nickclark2016 merged 1 commit intopremake:masterfrom
nickclark2016 merged 1 commit intopremake:masterfrom
Conversation
Jarod42
approved these changes
Apr 16, 2025
nickclark2016
approved these changes
Apr 20, 2025
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
3 participants
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 vs200x_vcproj to handle NoManifest properly.
How does this PR change Premake's behavior?
Makes premake follow NoManifest properly, since premake used to
GenerateManifest="false", no matter what.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
Existing one should be fine
Follow our coding conventions
Minimize the number of commits
Align documentation to your changes