Enhance omitframepointer.md documentation #2512
Merged
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?
Updates the documentation for the
omitframepointerAPI, replacing placeholder text with clear explanations of each parameter (Default,On,Off). Also adds practical usage examples for common scenarios (debug vs release builds).How does this PR change Premake's behavior?
This PR does not change Premake’s behavior. It only improves the generated documentation so users understand what the
omitframepointersetting does.Are there any breaking changes? Will any existing behavior change?
No breaking changes. This is a documentation-only update.
Anything else we should know?
This update makes the documentation more approachable for users who aren’t familiar with compiler frame pointer options. It explains the trade-off between performance optimizations and debugging convenience.
Did you check all the boxes?
closes #XXXXin comment to auto-close issue when PR is merged)