Open
Conversation
sbrass
force-pushed
the
add-meson-build-support
branch
from
3023f7d to
c7c7f4a
Compare
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
1 participant
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.
I propose to add the meson build system, concurrently, to the autotools build chain.
The addition of meson is completely orthogonal to autotools setup, thus, both can exist side-by-side.
However, at the cost of higher build system maintenance.
In order to build with meson, one requires meson and ninja (both can be downloaded as binaries).
An advantage of the meson build system, we use Vftrace as subproject to any project using meson, hence, no need for a standalone installation of Vftrace and manual addition of linker flags.