[WIP] [Engine Details] Add details about .debugsymbols changes - #12306
Draft
AThousandShips wants to merge 1 commit into
Draft
[WIP] [Engine Details] Add details about .debugsymbols changes#12306AThousandShips wants to merge 1 commit into
.debugsymbols changes#12306AThousandShips wants to merge 1 commit into
Conversation
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.
Still work in progress and waiting for the final details in:
.debugsymbolssearch in crash handler godot#122764As well as a future macOS PR, and a possible future PR to integrate downloading debug symbols in the template manager
Not sure exactly where to detail this but I've added notes to the areas where it makes sense to me to place notes. Not sure about the best scope for this but will focus on the distribution and compilation details for now, might be good to add a note in the scripting/debug section as well as a follow-up for general crash handling but I think that's out of scope for this
Much of the specifics of the templates and the export process are in the respective export plugin pages (linked at the bottom of each
Exporting Forpage) so currently not planning to add anything there to reduce duplicationCurrently this is limited to a minor correction to the documentation I found when I was looking at what documentation already existed in preparation for making this PR.
Todo: