On Mon, May 17, 2010 at 11:27 PM, Denis Barbier <bou...@gmail.com> wrote: > On 2010/5/17 Mathieu Malaterre wrote: >> On Mon, May 17, 2010 at 9:43 PM, Denis Barbier <bou...@gmail.com> wrote: > [...] >>> You may try instead >>> sed -e 's...@general;/usr/[^;]*\.so;@@g' VTKLibraryDepends.cmake >>> Is this file needed at all on Debian systems? >> >> Yes ! See for instance use-case: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579642 > > This is a different issue; it is caused by overlinking, it would not > hurt to have an empty VTKLibraryDepends.cmake
Yes it would, I believe you prepared the patch for VTK a while back. >> cmake does not use pkgconfig and such but instead read this kind of >> file to track dependant library (which is really only usefull for >> static lib...). > > Information about needed libraries are already embedded within ELF > shared objects. > BTW I just tried and have been able to build gdcm package after > echo > /usr/lib/vtk-5.4/VTKLibraryDepends.cmake I think Brad King rejected your patch because you were not propagating vtkCommon or vtksys as an automatic dep. So if you have an empty /usr/lib/vtk-5.4/VTKLibraryDepends.cmake, you should be able to produce a simple example that does: add_executable(bla bla.cxx) target_link_libraries(bla vtkFiltering) # cmake will pull vtkCommon/vtksys dep automatically. In this case you can produce a different behavior for an installed tree VTK vs a build tree VTK. HTH -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
