A custom build of fwtools sounds like the perfect solution, here. Then my
bootstrap procedure consists of downloading my FWTools build, opening it up,
running ./install.sh and adding the directory to the path (to allow access
to the libraries).
Thanks, Even, this is great!
On Fri, Feb 25, 2011 at
Le vendredi 25 février 2011 21:02:06, Sam Ritchie a écrit :
> Even,
>
> Thanks for the response, and sorry for my late reply, here.
>
> What you write makes sense, especially after processing this problem a bit
> further. As you mentioned, libgdal1- was installed by apt-get... the
> problem h
Even,
Thanks for the response, and sorry for my late reply, here.
What you write makes sense, especially after processing this problem a bit
further. As you mentioned, libgdal1- was installed by apt-get... the
problem here is that apt-get has libgdal1-1.5.0, and I was building java
bindings f
Le jeudi 24 février 2011 16:51:12, Sam Ritchie a écrit :
> Hey all,
>
> QUICK VERSION:
> When I build the java bindings for gdal, what native dependencies do I need
> to transfer over to another machine (with an identical install location) to
> get them to run?
>
> LONG VERSION:
> I'm working on
Hey all,
QUICK VERSION:
When I build the java bindings for gdal, what native dependencies do I need
to transfer over to another machine (with an identical install location) to
get them to run?
LONG VERSION:
I'm working on an application that requires the java bindings for gdal 1.8.0
to be package
