Cmake vs Meson
#51375
Replies: 2 comments
-
|
vcpkg needs to integrate with whatever exists upstream. There are various different ways to build something which includes buildsystems like CMake, Meson, Autotools, MSBuild, qmake, etc. If you want to package you package what exists and dont want to reinvent the buildsystem of upstream which otherwise becomes a maintenance burden for the packager. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ah, I get it now. Thanks for clarifying. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This isn't a bug report or anything. Just something I've always been curious about... why does vcpkg offer two different build systems? Is it some kind of safety feature / fallback option? i.e. if someone was having problems with one system, then there's an alternative one they could try. Or are some ports better suited to building with Cmake and others are more suited to Meson?
Beta Was this translation helpful? Give feedback.
All reactions