Meson Configuration #259
Open
Meson Configuration #259
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
…ld. Make Launch configuration generate the Release build.
…ild all targets" Launch configuration.
Contributor
Author
|
I suppose gutting MSBuild also includes removing it from continuous integration and such. |
HeliumAnt
approved these changes
Jan 8, 2026
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.
Meson configurations should be generally usable now. Removed conditional builds from all Meson build paths, removed expectations of differentiated executables from Meson tasks, renamed all tasks to accurately read either "Launch" or "Configure & Launch" depending on specifics, and created parity. Now the project can be either built and run or configured, built, and run, for both Windows and Unix configurations.
I have neglected to gut the MSBuild stuff because I dunno exactly how to do that besides just cutting it from the
tasks.jsonandlaunch.jsonfiles. That can be a separate PR, I think.