adding meson-build to the linux VM provisioning script #12858
Conversation
also: - updated meson version in `vcpkg_find_acquire_program` to 0.54.3 - added a `PIP3_PACKAGE_NAME` option to the `vcpkg_find_acquire_program` help message generator - updated `ports/tool-meson/CONTROL` version to 0.54.3
|
as said previously we cannot rely on the system package manager for meson due to it being to low in version. As soon as meson hits 0.55.1 i will continue #12393 which will simply download the version specified by vcpkg and use that instead of system provided meson. |
Where? am I supposed to know what you're talking about? Are you saying that this PR isn't necessary then? If so, I'm happy to close it. I don't really want to maintain this. |
see discussion in #12224.
according to the discussion in #12224 (comment) I would say yes since we will use a different approach to fix the meson version in the future. |
|
None of your points in that PR suggest that, except maybe the one about |
|
Actually, never mind. If your PR brings meson up to a newer version, then I don't really care much for the details ^_^ |
This PR is an exact replay of #12224, but from a branch other than master. See the discussion on that PR for context etc.
A number of minor things relating to the use of the meson build system:
vcpkg_find_acquire_programsuggesting that linux users useaptto install meson, instead ofpip3vcpkg_find_acquire_programmeson version to 0.54.3ports/tool-meson/CONTROLversion to 0.54.3What does your PR fix?
Doesn't fix, but contributes to, the resolution of #10786. A quick search of the issues for
mesonsuggests that it would be useful for a number of others, too.Which triplets are supported/not supported? Have you updated the CI baseline?
I don't think this question is relevant to my change, since I'm not submitting a port.
Does your PR follow the maintainer guide?
I believe so.