Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I would say this is an argument against dropping autotools from CI. Either way, you want to test meson in CI because you do not want meson's support to regress, surely?
Both autotools and meson are tested on Linux by CI, this is for Windows mingw builds which have never had meson builds on CI before. Agree at this stage it should not replace autotools CI as I said above, but it seems to do so IIUC.
Surely, if both build systems install the same files -- which they do on Linux at least, right?
Actually no, on Linux the Geany Autotools installs libs in in $prefix/lib but the Meson build uses the correct place, $prefix/lib/x86_64-linux-gnu (or i386-linux-gnu or aarch64 or whatever as appropriate). But so long as the plugin Autotools uses pkg-config to find them (as I assume it does on Linux) it should work on windows as well.
Perhaps it was unclear in the initial port what the optimal approach was.
Most probably, IIUC the guy who did the original port is on holidays, so he is forgiven for no input until he returns.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.