I made an initial attempt on gdal with cmake for vcpkg:
https://github.com/microsoft/vcpkg/pull/22392
Now vcpkg's default is static linkage on Linux and macOS. AFAICT static
linkage is not covered very well. Fixing this needs a lot of work either
on the find modules, or on getting dependencies
FWIW, I'll cast my +0.5 (not a full +1 because I didn't get to test
myself, but I'm supportive because the feedback I've read so far sounds
great)
On 2022-01-17 08:37, Even Rouault wrote:
Hi,
The new CMake build system
(https://gdal.org/development/rfc/rfc84_cmake.html) has made excellent
Le 25/01/2022 à 01:27, Joaquim Manuel Freire Luís a écrit :
Hi,
I made also an attempt on Windows and so far my findings are:
The docs say that the PROJ variables should be
PROJ_INCLUDE_DIR
PROJ_LIBRARY_RELEASE
But the lib var must in fact be
PROJ_LIBRARY
How do you build exactly ?
If yo
Hi,
I made also an attempt on Windows and so far my findings are:
The docs say that the PROJ variables should be
PROJ_INCLUDE_DIR
PROJ_LIBRARY_RELEASE
But the lib var must in fact be
PROJ_LIBRARY
Couldn't yet find a way to build with HDF5, ECW and MRSID, which I can do with
no problems with
I have started testing cmake support on gdal master.
My approach is
1) Build gdal from git using cmake.
2) Be able to create a release tarball (not actually a release of
course) from master in order to use for building with pkgsrc.
3) Build the release using autoconf, basically unchange
