On Saturday, 9 November 2024 4:59:17 AM AEDT Barry DeZonia wrote:
> If (totally fake example) I set the dependency in my jar to gdal 3.0.0 and
> I only make calls within the 3.0.0 java bindings api in my code, then if
> someone has gdal 3.7.x installed, will my code be able to interact with the
> i
If (totally fake example) I set the dependency in my jar to gdal 3.0.0 and
I only make calls within the 3.0.0 java bindings api in my code, then if
someone has gdal 3.7.x installed, will my code be able to interact with the
installed gdal?
On Fri, Nov 8, 2024 at 2:50 AM Brad Hards wrote:
> On Fr
On Friday, 8 November 2024 1:39:47 PM AEDT Barry DeZonia via gdal-dev wrote:
> I am really curious how people are solving this kind of problem
> without pulling out their hair.
What is the minimum version of GDAL you actually need?
I would suggest to just specify that as your dependency, and al
Hi Even,
Maybe I should be more clear.
My java project (built with Maven) has this dependency:
org.gdal
gdal
3.8.0
So if someone has installed gdal 3.8.x (including the java bindings)
my code will work with it. But this seems to imply that if I want to
support 3.4.x I need to change the
Barry,
I'm not totally sure to have the full picture of what you
deploy/distribute. I'd assume the main difficulty for the end users of
your Java component is to get the GDAL native library, and probably even
more tricky, the libgdaljni.so/dll/dylib. If you assume they have
managed libgdal it
Hey all,
I hope this is the right place for this email. I am a developer that has
written a java component that interfaces with the java bindings and allows
my app users to access gdal data.
The problem I have is that gdal seems to release somewhat often. I wrote my
code initially for 3.7 but lat
