Hello, On ketvirtadienis 17 Rugsėjis 2009 13:39:46 Mathieu Malaterre wrote: > On Thu, Sep 17, 2009 at 12:33 PM, Mathieu Malaterre > > <mathieu.malate...@gmail.com> wrote: > >> echo JAVA_AWT_LIBRARY:FILEPATH=/usr/lib/jvm/default- > >> java/jre/lib/$(DEB_HOST_ARCH_CPU)/libjawt.so >> Build/CMakeCache.txt > > As a side note here is the output of what is happening without those > two lines and using the old FindJNI.cmake: > > https://buildd.debian.org/~luk/status/package.php?p=gdcm
That's not true. Those failures are an example of cmake "leaking" link interface libraries from vtk (with the help of vtk cmake hackery of course). I grep'ed gcdm sources a bit and I'm 100% sure vtkgdcmJava did not request to be linked with libjawt.so, it probably does not need jawt at all. That jawt link dependency came from libvtk5-dev (/usr/lib/vtk-5.2/VTKLibraryDepends.cmake). So here you also have an explanation why it searches for a weird path on armel and where it came from... We faced this in KDE and rather successfully solved the issue. cmake 2.6 has proper means to fight this "linking the whole world together" problem with its LINK_INTERFACE_LIBRARIES property and support for IMPORTED targets. So it is time for vtk to properly use those. -- Modestas Vainius <modes...@vainius.eu>
signature.asc
Description: This is a digitally signed message part.
