Le 22/05/2024 à 16:59, Greg Troxel a écrit :
I got 3.5 to work, so I'm focusing on the 3.9 upgrade. It seems that
3.9, vs 3.5, has withdrawn the swig generated files from the distfile.
With 3.9, you could also do a more manual approach (not sure the
python_generated_files target is avai
I got 3.5 to work, so I'm focusing on the 3.9 upgrade. It seems that
3.9, vs 3.5, has withdrawn the swig generated files from the distfile.
With 3.9, you could also do a more manual approach (not sure the
python_generated_files target is available in 3.5)
cmake ..
make GDAL # build the
Even Rouault writes:
> If the build requirements for the Python bindings are met (python +
> swig available), then a "make && make install" cycle will build and
> install libgdal and the python bindings, like it did in autoconf
> era. The CMake build target "python_binding" has libgdal as a
> dep
Greg,
If the build requirements for the Python bindings are met (python + swig
available), then a "make && make install" cycle will build and install
libgdal and the python bindings, like it did in autoconf era. The CMake
build target "python_binding" has libgdal as a dependency.
The idea fo
I had not gotten to converting the pkgsrc package to cmake, because it
seemed like it would take a long time. So gdal is at 3.5.3, the last
one that works with autoconf. Yes, I know that 3.5 was about two years
ago. It turns out that it is taking hours to do the conversion, and the
good news is
