Re: [gdal-dev] GDAL 3.5.0alpha1 available
Forgot to mention that the GDAL specific options to control the CMake build are documented in https://gdal.org/build_hints.html (of course general CMake variables that control builds, like the ones listed at https://cmake.org/cmake/help/latest/manual/cmake-variables.7.html, can also generally be used) Practical examples of build recipees as used by CI can be found in https://github.com/OSGeo/gdal/blob/master/.github/workflows/cmake_builds.yml and https://github.com/OSGeo/gdal/blob/master/.github/workflows/android_cmake/start.sh (although for the later this is probably done in the most idiomatic way to cross-compile for Android) Even Le 21/03/2022 à 00:05, Even Rouault a écrit : Hi, As discussed a few weeks ago, here's a GDAL 3.5.0alpha1 snapshot, mostly for the sake of exercising the new CMake build system (thanks to all early testers and contributors!). The libtool numbers have *not* been updated (I believe they are still the same as the 3.3.0 release). This is not meant as being pushed to any distribution channel yet. Download links: http://download.osgeo.org/gdal/3.5.0/gdal-3.5.0alpha1.tar.gz http://download.osgeo.org/gdal/3.5.0/gdal-3.5.0alpha1.tar.xz http://download.osgeo.org/gdal/3.5.0/gdal350alpha1.zip Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 3.5.0alpha1 available
Le 21/03/2022 à 18:39, Sebastiaan Couwenberg a écrit : Quite a lot of new files which suggests that CPACK_SOURCE_IGNORE_FILES needs more work. CPack hasn't been used at all to generate the tarball. This is the traditionnal mkgdaldist.sh script. I suspect this comes from gdal/ content having been moved to topdir, and now things like .github/ or doc/ are included and should probably be cleaned up. Other things you spotted ? | Also quite a lot of noise in the diff due $Id$ expansion changes like: I suspect this is also due to the gdal/ moving, which must breaks the history. That $Id$ expansion could probably be just removed. I filed https://github.com/OSGeo/gdal/issues/5483 about those é topics Kind Regards, Bas -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 3.5.0alpha1 available
On 3/21/22 18:39, Sebastiaan Couwenberg wrote: Quite a lot of new files which suggests that CPACK_SOURCE_IGNORE_FILES needs more work. Also quite a lot of noise in the diff due $Id$ expansion changes like: - * $Id: armadillo_headers.h dd1e0e25c2d41bbb0b63061751483276ab5da090 2019-04-27 15:27:04 +0200 Even Rouault $ + * $Id: armadillo_headers.h $ Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 3.5.0alpha1 available
Quite a lot of new files which suggests that CPACK_SOURCE_IGNORE_FILES needs more work. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Why does ogrinfo use backtics in the output?
Hi Jukka, those backtics are there from day one: https://github.com/OSGeo/gdal/commit/3359e3f9f2b1d4c1197ab14395efe652eded37da . I suppose this is just for aesthetics. I assume this should be fine to change that to single quotes (although some downstream consumers that would dump ogrinfo output and do exact comparison with reference files would probably be unhappy, but we have regularly do changes that affect the exact output of ogrinfo through the years). If you want to do that, a few expected results in autotest/utilities/test_ogrinfo.py will need to be adapted as well as https://github.com/OSGeo/gdal/blob/master/apps/ogrinfo.cpp Even Le 21/03/2022 à 12:43, Rahkonen Jukka (MML) a écrit : Hi, I have been wondering for a long time why orginfo is using backtics/backquotes in the output. In this example before “foo” and “ESRI” ogrinfo foo.shp INFO: Open of `foo.shp' using driver `ESRI Shapefile' successful. Not so big problem but in markup the backtick means the beginning/end of a code block and copy-pasting ogrinfo report may require some hand editing. Would it make any harm to use single quotes at both ends? -Jukka Rahkonen- ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] Why does ogrinfo use backtics in the output?
Hi, I have been wondering for a long time why orginfo is using backtics/backquotes in the output. In this example before "foo" and "ESRI" ogrinfo foo.shp INFO: Open of `foo.shp' using driver `ESRI Shapefile' successful. Not so big problem but in markup the backtick means the beginning/end of a code block and copy-pasting ogrinfo report may require some hand editing. Would it make any harm to use single quotes at both ends? -Jukka Rahkonen- ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
