Add TargetDescriptionXmlOverride extension
#43
Merged
Conversation
This file contains 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
daniel5151
changed the title
TargetDescriptionXmlOverride extension
DrChat
approved these changes
Mar 19, 2021
|
Alrighty, I'll go ahead and merge this into master, and I'll push out a |
|
Perfect! Appreciate it. |
|
Alright, gdbstub |
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.
Building off of @DrChat's work in #42 (closes #42)
Remember how I said I'd try and tackle #12 as part of this PR as well? Well... after refreshing myself on the details of the underlying
qXfer:features:readAPI, I realized that my idea wouldn't actually work. The changes will require a bit more thought and effort, and aren't something I'd be able to hack out in an afternoon.As such, I've kept this PR's scope limited to just allowing target-dependent target description XML files.