Hi Andre,<br><br>thank you for your help. I tried what you told me, too. But guess what - it doesn't work. Always the same, CMake links the weong libraries. I'm going slightly mad. Can please post your whole CMakeLists.txt, so I can compare the whole stuff to my own one?<br>
<br>With kind regards,<br>Michael<br><br><br><br><div class="gmail_quote">2010/7/21 André Prins <span dir="ltr"><<a href="mailto:a.h.prins@gmail.com">a.h.prins@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Michael,<br>
<br>
What Dave probably meant with was to explicitly specify a VTK_DIR<br>
variable to the find_package command. E.g. something like this:<br>
<br>
set( VTK_DIR "c:\work\libs\vtk_bin_5.6.0_x64" )<br>
find_package( VTK REQUIRED )<br>
include( ${VTK_USE_FILE} )<br>
<br>
Alternatively, you could specify a hint to find_package. E.g. in my<br>
projects...,<br>
<br>
find_package( VTK REQUIRED HINTS $ENV{VTKDIR} )<br>
include( ${VTK_USE_FILE} )<br>
<br>
I usually have severaly "batch-scripts or profiles" with my various<br>
development-environments... E.g. a 32-bit Vtk Release Static and a<br>
64-bit Vtk Debug Release, etc. This way I can use a single<br>
CMakeLists.txt.<br>
<br>
Regards,<br>
Andre<br>
<div><div></div><br></div></blockquote></div><br>