Add dynamic debugging support for MSC (VS, Ninja)#2626
Merged
samsinsane merged 1 commit intopremake:masterfrom Feb 24, 2026
Merged
Add dynamic debugging support for MSC (VS, Ninja)#2626samsinsane merged 1 commit intopremake:masterfrom
samsinsane merged 1 commit intopremake:masterfrom
Conversation
samsinsane
approved these changes
Feb 24, 2026
Jarod42
reviewed
Feb 24, 2026
|
|
||
| ### Availability ### | ||
|
|
||
| Premake 5.0.0 or later for Visual Studio 2022 and later or MSC toolsets. |
Member
Author
There was a problem hiding this comment.
Nope. Next release is full release.
| | Value | Description | Notes | | ||
| |-------|-------------|-------| | ||
| | Default | Uses the default dynamic debugging behavior. | | | ||
| | On | Allows dynamic debugging of source code. | For MSVC, debug [symbols](symbols.md) must be present. [Edit and Continue](editandcontinue.md) is not allowed. For a full list of flags that are required, see the [Microsoft Docs](https://learn.microsoft.com/en-us/cpp/build/reference/dynamic-deopt?view=msvc-170). | |
Contributor
There was a problem hiding this comment.
Does msvc warn for incompatible flags?
Else we should probably emit a warning.
Member
Author
There was a problem hiding this comment.
It errors, I believe. That said, this would break paradigm. We don't do that anywhere else.
| dynamicdebugging "Off" | ||
| prepare() | ||
| test.excludes("/dynamicdeopt", msc.getcxxflags(cfg)) | ||
| end |
Member
Author
There was a problem hiding this comment.
I'm torn on this, personally. I typically treat default as "do whatever the default for the toolset/exporter is" -- So nothing should be emitted at all. We could test that we don't put /dynamicdeopt in there, but we don't typically test the "default" case (though the argument could be made that we should)
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?
Adds support for Dynamic Debugging (/dynamicdeopt) for Visual Studio and MSC via Ninja.
How does this PR change Premake's behavior?
No breaking changes. Adds new API.
Anything else we should know?
Context: https://devblogs.microsoft.com/cppblog/cpp-dynamic-debugging-full-debuggability-for-optimized-builds/
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!