Open cyanreg opened 6 months ago
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?
Not really. But I wouldn't say adding a line or two when adding files is a high maintenance burden.
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?
Meson can automatically use in-tree versions of libraries by cloning them into a
submodules
folder, but I haven't documented that.