On 12.09.2024 at 06:46, Pierre Joye wrote: > I mentioned that long ago, but a maybe faster way to get windows ready > sources is vcpkg: > > https://vcpkg.roundtrip.dev/ports/libxpm > > only changes required are for static lib names, as we use _a to > differentiate. lib for dll or static links.
Dropping our own builds in favor of some package manager is a worthwhile goal, but might be much harder than it seems. There was a discussion about CMake builds[1] a few years ago, and vcpkg and Conan have been shortly discussed there. The OP even started to provide some PRs regarding adding further libraries to Conan, but that apparently came to nothing. I can't remember if I ever had a closer look at Conan, but when I was looking into vcpkg a while ago, I've noticed a couple of problems: besides some missing packages (even for bundled extensions), and the naming conventions you've mentioned, maybe the biggest problem was their build style, namely to package a library with all it's dependencies. We would need to remove the dependencies after building and packaging to be able to stick to our distribution style. It seems to me that vcpkg is a great tool for applications, but not necessarily suitable for for us. [1] <https://externals.io/message/116655> Christoph
