From: William S F. <ws...@fu...> - 2015-11-25 20:05:12
|
On 5 November 2015 at 16:45, <seb...@ne...> wrote: > Hello, > > We're currently developing a java application that needs the gdal library. > This library use swig for java bindings. > > We're facing a cross platform problem, I think that I misunderstood > something... We are developing our application on a windows platform and > deploy it on a linux platform. The gdal library is installed on window and > linux. It works like a charm on windows as we use the swig jar delivered in > the installer. But when we deploy our application on linux with this swig > jar, it doesn't work... We have to switch on the linux version of the swig > binding jar to make this work. > > I suppose that the gdal library is not compiled with the same options on > windows and on linux, so the swig jar is not the same and cause our > problem... > > Questions are : > - Is there any chance for this to work (i.e. having a single cross > platform jar file)? In the Java world, having 2 different jars is not > coherent and the toolset that we use is not designed to handle this. > SWIG should produce identical code when generated on all platforms. There is nothing in the Java layer that is platform specific so you can use just one jar file on all platforms. There is a very small amount of platform/compiler specific code within C macros in the generated code. - Can we compile the swig jar binding file to ignore non used C++ methods? > Use %ignore. William |