Change environment to use VSCode development containers #2
+45
−14
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
Container provides Zig and ZLS Update build.zig to use linker directly inside container Update build settings to put output files in build folder
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.
This PR moves the zig-wii development environment into a VSCode development container.
Opening the workspace in vscode will ask you to re-open the workspace inside the container.
From here on, everything works as if you're developing locally, without requiring docker compose to spin up the container for the link and conversion steps.
The container comes with Zig and ZLS pre installed. The versions for both can be changed through the provided environmental variables in the Dockerfile.
I've also updated the builder to output the
.map.doland.elffiles into thebuildfolder.