Add meson buildsystem support#2
Open
cyanreg wants to merge 1 commit into
Open
Conversation
Contributor
|
Wouldn't this require us to maintain the source code list in two different build systems at the same time? Is there no other way? |
Author
|
Not really. But I wouldn't say adding a line or two when adding files is a high maintenance burden. |
Contributor
|
OK well before I add the PR we're going to need a CI pipeline to test the meson build on at least one platform to ensure we keep it up to date and working properly. |
|
Why not FetchContent with the existing CMakeLists setup, instead of adding yet another build system? |
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
3 participants
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 can automatically use in-tree versions of libraries by cloning them into a
submodulesfolder, but I haven't documented that.