PR proposed related to this https://github.com/OSGeo/gdal/pull/6843
On Fri, 2 Dec 2022 at 13:18, Paul Harwood wrote:
> BTW - I am fairly certain that the error messages are because the .NET SDK
> release default is still set as .NET 5 and reading your email - you don't
> have .NET 5. Since you
Hi,
I declare this motion passed with +1 from PSC members KurtS and me.
Even
Le 24/11/2022 à 09:39, ElPaso a écrit :
Hi,
Motion:
Adopt RFC88: RFC69 C/C++ Code Formatting [1]
I have updated the RFC [1] to use pre-commit and I have created a
draft implementation of the pre-commit hook and th
BTW - I am fairly certain that the error messages are because the .NET SDK
release default is still set as .NET 5 and reading your email - you don't
have .NET 5. Since you did not set the .NET release - it is trying to use
the default.
I think the error messages could be a lot better! I can have
sorry - cut and paste error. That should have been
-DBUILD_CSHARP_BINDINGS=OFF
On Fri, 2 Dec 2022 at 12:53, Paul Harwood wrote:
> I can have a think about what is causing the problem - but the simplest
> fix if you don't want the c# bindings is to build with
> -DBUILD_CSHARP_BINDINGS:BOOLOFF
>
I can have a think about what is causing the problem - but the simplest fix
if you don't want the c# bindings is to build with
-DBUILD_CSHARP_BINDINGS:BOOLOFF
More on the compile switches here
https://gdal.org/development/building_from_source.html#cmdoption-arg-BUILD_CSHARP_BINDINGS-BOOL
On Fri,
I am very new to building out GIS tools on the MacOS platform,
so I apologize for my rather turgid description below.
I am trying to build gdal 3.6.0 (git cloned)
on macos catalina 10.15.7 on a macbook pro 2017
On this machine I have various versions of Msoft dotnet core sdks installed
(7.0.100,
Hi,
I've been working on a SQL query callback for GDALDataset [1], I wasn't
sure if that deserves an RFC, but since I've prepared one [2] I'd like
to read your comments.
Please note that I've also tested the implementation in QGIS logging
panel and it works just fine, we can now see which S
