Open
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.
Dev containers are an incredibly useful feature of VSCode, and allow automatic setup of a complete working dev environment without any necessary input from the user.
The Gen 3 repos aren't the easiest things in the world to get working, and this PR automates the configuration of the dev environment to build both matching roms using the legacy toolchain, as well as full support for the modern toolchain. It also provides full C/C++ intellisense linting, selectable build targets, and full configuration for the step debugger to be used with mGBA.
I have also added a readme with full instructions on how to use the dev container.
Notable issues
gnu99instead ofgnu89in the configurations for a similar reasonAs a note, I have a more advanced version of this configuration that additionally includes full support and linting for poryscript. I will submit that too if relevant, but thought it best to keep this PR focused on the core functionality of the repo.