Ciao Justin,
long story short, atm imagieo-ext works with its own modified version
of gdal bindings which you can get from the imageio-ext site.
1.1 should use 1.7.x instead.

Generally speaking I doubt we will ever run after gdal trunk for
anything different than local experiments since I tend to be cautious
and use older versions
of gdal where a memory leak is less likely to occur.

Regards,
Simone Giannecchini
-------------------------------------------------------
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:      +39 0584 962313
mob:    +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/simonegiannecchini
http://twitter.com/simogeo

-------------------------------------------------------



On Sat, Feb 26, 2011 at 1:46 AM, Justin Deoliveira <jdeol...@opengeo.org> wrote:
> Hi all,
> I am trying to load up some mrsid files via the imageio-ext readers and
> running into some issues. My overall question is will the imageio-ext libs
> work with gdal 1.8?
> I know I have made this work with gdal-1.7. But it seems lizardtech is not
> making available the Geo_SDK version 7. Only the version 8 sdk is available.
> I tried compiling gdal 1.7 against it and it did not work. What I can find
> online seems to confirm that i need gdal 1.8 to use the mrsid version 8 sdk.
> So I am just wondering if it is a problem on my side... or if the
> imageio-ext libs won't work with gdal 1.8. For reference the error I get is:
> java.lang.UnsatisfiedLinkError: org.gdal.gdal.gdalJNI.Open
> And indeed if I list the symbols in the version 1.8 jni library I don't see
> it:
>                  U GDALOpen
>                  U GDALOpenShared
> 00000000000289d0 T Java_org_gdal_gdal_gdalJNI_OpenShared_1_1SWIG_10
> 0000000000028940 T Java_org_gdal_gdal_gdalJNI_OpenShared_1_1SWIG_11
> 0000000000028ae0 T Java_org_gdal_gdal_gdalJNI_Open_1_1SWIG_10
> 000000000002f570 T Java_org_gdal_gdal_gdalJNI_Open_1_1SWIG_11
> 00000000000288d0 T _Z10OpenSharedPKc10GDALAccess
> 0000000000028b80 T _Z4OpenPKc
> 0000000000028a70 T _Z4OpenPKc10GDALAccess
> Whereas if I list the symbols of the jni lib i download from the imageio-ext
> project I do see it:
>                  U GDALOpen
>                  U GDALOpenShared
> 000000000000eb3c T Java_org_gdal_gdal_gdalJNI_Open
> 000000000000ea24 T Java_org_gdal_gdal_gdalJNI_OpenShared
> 000000000000e9b6 T _Z10OpenSharedPKc10GDALAccess
> 000000000000eac7 T _Z4OpenPKc10GDALAccess
>
> So perhaps I am building the jni lib improperly. Those SWIG suffixes make me
> think I probably am. Any guidance appreciated :)
> Thanks.
> -Justin
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT
> data
> generated by your applications, servers and devices whether physical,
> virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to