<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-family:arial,sans-serif;font-size:13px">//Value Computed by CMake</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">ReadImageData_SOURCE_DIR:</span><span style="font-family:arial,sans-serif;font-size:13px">STATIC=C:/Users/Dan/Documents/</span><span style="font-family:arial,sans-serif;font-size:13px">Visual Studio 2013/Projects/VTK_test</span></blockquote>
<div><br></div><div>This should be set to the example source directory, which I would expect to be named ReadImageData. When building the example, there should be no need to edit any CMakeLists.txt files.</div><div><br>
</div>
<div>Once you set up an empty, clean build directory, you should open up cmake-gui. "Where is the source code:" should point to the ReadImageData example source code that you downloaded. "Where to build the binaries:" should point to the clean, empty directory you have made. Then set VTK_DIR to point to your VTK-6.1-install/lib/cmake/vtk-6.1 or build directory (whichever contains VTKConfig.cmake), where you have built VTK.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 5:02 PM, Dan <span dir="ltr"><<a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">I tried building the example ReadImageData (<a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/ReadImageData" target="_blank">http://www.vtk.org/Wiki/VTK/Examples/Cxx/IO/ReadImageData</a>) since I want to use vtkImageData in my own app. Using the CMakeLists.txt from the page gives me an include error<br>
<br><blockquote>Error 1 error C1083: Cannot open include file: 'vtkImageViewer2.h': No such file or directory C:\Users\Dan\Documents\Visual Studio 2013\Projects\VTK_test\ReadImageData.cpp 5 1 ReadImageData<br>
<br></blockquote>I have attached the CMakeCache.txt below. I notice it still says "/build" and not "/install" even though I changed it in the GUI / CMakeLists.txt.<br><br>Regards,<br>Dan<br><br><blockquote>
# This is the CMakeCache file.<br># For build in directory: c:/Users/Dan/Documents/Visual Studio 2013/Projects/VTK_test/build<br># It was generated by CMake: C:/Program Files (x86)/CMake/bin/cmake.exe<br># You can edit this file to change values found and used by cmake.<br>
# If you do not want to change any of the values, simply exit the editor.<br># If you do want to change a value, simply edit, save, and exit the editor.<br># The syntax for the file is as follows:<br># KEY:TYPE=VALUE<br># KEY is the name of a variable in the cache.<br>
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.<br># VALUE is the current value for the KEY.<br><br>########################<br># EXTERNAL cache entries<br>########################<br><br>//Semicolon separated list of supported configuration types, only<br>
// supports Debug, Release, MinSizeRel, and RelWithDebInfo, anything<br>// else will be ignored.<br>CMAKE_CONFIGURATION_TYPES:STRING=Debug;Release;MinSizeRel;RelWithDebInfo<br><br>//Flags used by the compiler during all build types.<br>
CMAKE_CXX_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3 /GR /EHsc<br><br>//Flags used by the compiler during debug builds.<br>CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1<br><br>//Flags used by the compiler during release builds for minimum<br>
// size.<br>CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG<br><br>//Flags used by the compiler during release builds.<br>CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG<br><br>//Flags used by the compiler during release builds with debug info.<br>
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG<br><br>//Libraries linked by default with all C++ applications.<br>CMAKE_CXX_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib<br>
<br>//Flags used by the compiler during all build types.<br>CMAKE_C_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3<br><br>//Flags used by the compiler during debug builds.<br>CMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1<br>
<br>//Flags used by the compiler during release builds for minimum<br>// size.<br>CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG<br><br>//Flags used by the compiler during release builds.<br>CMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG<br>
<br>//Flags used by the compiler during release builds with debug info.<br>CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG<br><br>//Libraries linked by default with all C applications.<br>CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib<br>
<br>//Flags used by the linker.<br>CMAKE_EXE_LINKER_FLAGS:STRING=' /machine:x64 '<br><br>//Flags used by the linker during debug builds.<br>CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL<br><br>//Flags used by the linker during release minsize builds.<br>
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO<br><br>//Flags used by the linker during release builds.<br>CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO<br><br>//Flags used by the linker during Release with Debug Info builds.<br>
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL<br><br>//Install path prefix, prepended onto install directories.<br>CMAKE_INSTALL_PREFIX:PATH=C:/Program Files/ReadImageData<br><br>//Path to a program.<br>
CMAKE_LINKER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/x86_amd64/link.exe<br><br>//Flags used by the linker during the creation of modules.<br>CMAKE_MODULE_LINKER_FLAGS:STRING=' /machine:x64 '<br>
<br>//Flags used by the linker during debug builds.<br>CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL<br><br>//Flags used by the linker during release minsize builds.<br>CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO<br>
<br>//Flags used by the linker during release builds.<br>CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO<br><br>//Flags used by the linker during Release with Debug Info builds.<br>CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL<br>
<br>//Value Computed by CMake<br>CMAKE_PROJECT_NAME:STATIC=ReadImageData<br><br>//RC compiler<br>CMAKE_RC_COMPILER:FILEPATH=rc<br><br>//Flags for Windows Resource Compiler.<br>CMAKE_RC_FLAGS:STRING=' '<br><br>//Flags used by the linker during the creation of dll's.<br>
CMAKE_SHARED_LINKER_FLAGS:STRING=' /machine:x64 '<br><br>//Flags used by the linker during debug builds.<br>CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL<br><br>//Flags used by the linker during release minsize builds.<br>
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO<br><br>//Flags used by the linker during release builds.<br>CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO<br><br>//Flags used by the linker during Release with Debug Info builds.<br>
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL<br><br>//If set, runtime paths are not added when installing shared libraries,<br>// but are added when building.<br>CMAKE_SKIP_INSTALL_RPATH:BOOL=OFF<br>
<br>//If set, runtime paths are not added when using shared libraries.<br>CMAKE_SKIP_RPATH:BOOL=OFF<br><br>//Flags used by the linker during the creation of static libraries.<br>CMAKE_STATIC_LINKER_FLAGS:STRING=<br><br>//Flags used by the linker during debug builds.<br>
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=<br><br>//Flags used by the linker during release minsize builds.<br>CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=<br><br>//Flags used by the linker during release builds.<br>CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=<br>
<br>//Flags used by the linker during Release with Debug Info builds.<br>CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=<br><br>//If true, cmake will use relative paths in makefiles and projects.<br>CMAKE_USE_RELATIVE_PATHS:BOOL=OFF<br>
<br>//If this value is on, makefiles will be generated without the<br>// .SILENT directive, and all commands will be echoed to the console<br>// during the make. This is useful for debugging only. With Visual<br>// Studio IDE projects all commands are done without /nologo.<br>
CMAKE_VERBOSE_MAKEFILE:BOOL=OFF<br><br>//Value Computed by CMake<br>ReadImageData_BINARY_DIR:STATIC=C:/Users/Dan/Documents/Visual Studio 2013/Projects/VTK_test/build<br><br>//Value Computed by CMake<br>ReadImageData_SOURCE_DIR:STATIC=C:/Users/Dan/Documents/Visual Studio 2013/Projects/VTK_test<br>
<br>//The directory containing a CMake configuration file for VTK.<br>VTK_DIR:PATH=C:/VTK-6.1.0/build<br><br><br>########################<br># INTERNAL cache entries<br>########################<br><br>//Stored GUID<br>ALL_BUILD_GUID_CMAKE:INTERNAL=3BBDABD8-5086-4206-839A-E664E7B5EF7A<br>
//This is the directory where this CMakeCache.txt was created<br>CMAKE_CACHEFILE_DIR:INTERNAL=c:/Users/Dan/Documents/Visual Studio 2013/Projects/VTK_test/build<br>//Major version of cmake used to create the current loaded cache<br>
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3<br>//Minor version of cmake used to create the current loaded cache<br>CMAKE_CACHE_MINOR_VERSION:INTERNAL=0<br>//Patch version of cmake used to create the current loaded cache<br>CMAKE_CACHE_PATCH_VERSION:INTERNAL=0<br>
//Path to CMake executable.<br>CMAKE_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/cmake.exe<br>//Path to cpack program executable.<br>CMAKE_CPACK_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/cpack.exe<br>//Path to ctest program executable.<br>
CMAKE_CTEST_COMMAND:INTERNAL=C:/Program Files (x86)/CMake/bin/ctest.exe<br>//ADVANCED property for variable: CMAKE_CXX_FLAGS<br>CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG<br>
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL<br>CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE<br>CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO<br>CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_CXX_STANDARD_LIBRARIES<br>CMAKE_CXX_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_C_FLAGS<br>CMAKE_C_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG<br>CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL<br>
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE<br>CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO<br>CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES<br>CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1<br>//Executable file format<br>CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown<br>//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS<br>
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG<br>CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL<br>
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE<br>CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO<br>
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>//Name of generator.<br>CMAKE_GENERATOR:INTERNAL=Visual Studio 12 2013 Win64<br>//Name of generator toolset.<br>CMAKE_GENERATOR_TOOLSET:INTERNAL=<br>//Start directory with the top level CMakeLists.txt file for this<br>
// project<br>CMAKE_HOME_DIRECTORY:INTERNAL=C:/Users/Dan/Documents/Visual Studio 2013/Projects/VTK_test<br>//ADVANCED property for variable: CMAKE_LINKER<br>CMAKE_LINKER-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS<br>
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG<br>CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL<br>
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE<br>CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO<br>
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>//number of local generators<br>CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_RC_COMPILER<br>CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1<br>
CMAKE_RC_COMPILER_WORKS:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_RC_FLAGS<br>CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1<br>//Path to CMake installation.<br>CMAKE_ROOT:INTERNAL=C:/Program Files (x86)/CMake/share/cmake-3.0<br>
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS<br>CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG<br>CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL<br>CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE<br>CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO<br>CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH<br>CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1<br>
//ADVANCED property for variable: CMAKE_SKIP_RPATH<br>CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS<br>CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG<br>
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL<br>CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE<br>
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO<br>CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1<br>//Suppress Warnings that are meant for the author of the CMakeLists.txt<br>
// files.<br>CMAKE_SUPPRESS_DEVELOPER_WARNINGS:INTERNAL=FALSE<br>//ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS<br>CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1<br>//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE<br>
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1<br>//Stored GUID<br>ReadImageData_GUID_CMAKE:INTERNAL=1A034F39-05B9-431A-9126-3953C0660729<br>//Stored GUID<br>SG_Filter_CMake Rules_GUID_CMAKE:INTERNAL=159E609E-BA6C-4D08-A708-93D06E02CB55<br>
//Stored GUID<br>SG_Filter_Header Files_GUID_CMAKE:INTERNAL=C25EDD65-569F-47DD-84C4-1A4DC95E848F<br>//Stored GUID<br>SG_Filter_Object Files_GUID_CMAKE:INTERNAL=49682549-146C-495A-A05E-4717E9235FE3<br>//Stored GUID<br>SG_Filter_Resources_GUID_CMAKE:INTERNAL=805E7B31-FCFB-4FEC-8C70-8462336B3109<br>
//Stored GUID<br>SG_Filter_Source Files_GUID_CMAKE:INTERNAL=618C9595-6DBD-4D3C-AAAE-B898B7AD7622<br>//Stored GUID<br>ZERO_CHECK_GUID_CMAKE:INTERNAL=CF1D2DF2-CBDF-4351-ABD8-055BE091763A<br></blockquote><br><br><br><div><hr>
Date: Tue, 1 Jul 2014 16:22:05 -0400<div><div class="h5"><br>Subject: Re: [vtkusers] CMake/Linking Issues VTK 6.1.0<br>From: <a href="mailto:christopher.mullins@kitware.com" target="_blank">christopher.mullins@kitware.com</a><br>
To: <a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a><br>CC: <a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a><br><br><div dir="ltr">Interesting. Are you able to build any of the VTK examples [1] against your current install? Also, have you tried with a clean build tree of your application? It sounds like something is getting cached when it shouldn't be.<div>
<br></div><div>It might help if I could have a look at your CMakeCache.txt, or if you could take a screenshot of your cmake-gui before the "configure" step.<br><div><div><br></div><div>[1] <a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx" target="_blank">http://www.vtk.org/Wiki/VTK/Examples/Cxx</a></div>
</div></div></div><div><br><br><div>On Tue, Jul 1, 2014 at 4:16 PM, Dan <span dir="ltr"><<a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a>></span> wrote:<br>
<blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Hmm, just tried removing it. It doesn't make a difference. If I type the correct install directory into the GUI it just resets when I press 'configure'. If I type it an they just click 'generate' it still gives the error about 'vtkalglib.lib'.<br>
<br>Dan<br><br><div><hr>Date: Tue, 1 Jul 2014 15:59:59 -0400<div><div><br>Subject: Re: [vtkusers] CMake/Linking Issues VTK 6.1.0<br>From: <a href="mailto:christopher.mullins@kitware.com" target="_blank">christopher.mullins@kitware.com</a><br>
To: <a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a><br>CC: <a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a><br><br><div dir="ltr"><blockquote style="border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span style="font-family:arial,sans-serif;font-size:13px">Also, even though I specified my VTK_DIR in the CMake it keeps showing the wrong directory in the CMake GUI and even if I change it, it swaps back when I click on configure.</span></blockquote>
<div><br></div><div>I suspect this is causing the problem. Could you take it out of the CMakeLists.txt file and just provide it at configure time via cmake-gui? </div></div><div><br><br><div>
On Tue, Jul 1, 2014 at 3:56 PM, Dan <span dir="ltr"><<a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Hi Christopher,<br><br>Yes I have seen and read that page. The problem I am having is not building VTK itself, rather, building my own application which uses VTK. I have cobbled together a CMake file from scouring the VTK documentation / Google. It reads<br>
<br><blockquote>cmake_minimum_required(VERSION 2.8.7)<br>project(Test)<br>set(VTK_DIR "C:/VTK-6.1.0/install")<br>find_package(VTK 6.1 REQUIRED NO_MODULE)<br>if(VTK_FOUND)<br> message("found VTK. Version:" ${VTK_VERSION}. VTK_DIR: ${VTK_DIR})<br>
endif()<br>include(${VTK_USE_FILE})<br>add_executable(Test test.cpp)<br>target_link_libraries(Test ${VTK_LIBRARIES})<br></blockquote><br>It configures fine and generates a Visual Studio solution I can open, but when I try and build this it throws a linker error saying<br>
<br><blockquote>"cannot open input file 'vtkalglib.lib'"<br><br></blockquote>Interesting to note is that in my install folder (specified while building VTK) there is a .lib called 'vtkalglib-6.1.lib' but no 'vtkalglib.lib'. Also, even though I specified my VTK_DIR in the CMake it keeps showing the wrong directory in the CMake GUI and even if I change it, it swaps back when I click on configure.<br>
<br>Regards,<br>Dan<br><div><br><br></div><div><div><hr>Date: Tue, 1 Jul 2014 15:43:36 -0400<br>Subject: Re: [vtkusers] CMake/Linking Issues VTK 6.1.0<br>From: <a href="mailto:christopher.mullins@kitware.com" target="_blank">christopher.mullins@kitware.com</a><br>
To: <a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a><br>CC: <a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a></div><div><div><br><br><div dir="ltr">Have you checked out the wiki page for configuring and building [1] ? It was written for VTK 6.1.0. <div>
<br></div><div>Could you post which step you're trying to accomplish, and the errors you receive? I think this will help us diagnose what's happening.<div>
<br></div><div><br></div><div>[1] <a href="http://www.vtk.org/Wiki/VTK/Configure_and_Build" target="_blank">http://www.vtk.org/Wiki/VTK/Configure_and_Build</a></div></div></div><div><br><br><div>On Tue, Jul 1, 2014 at 3:33 PM, Dan <span dir="ltr"><<a href="mailto:dbpvusrlist@hotmail.co.uk" target="_blank">dbpvusrlist@hotmail.co.uk</a>></span> wrote:<br>
<blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Hi All,<br><br>I have been using VTK (version 5) for some time. I downloaded and built the source as detailed on the website, and then I was able to link to the libraries and include the header files manually as I usually do for third party libraries. Everything worked fine.<br>
<br>I'm now on a new system so I downloaded, configured and built VTK 6.1.0. It built fine and I installed it to the specified directory. However, I then found it impossible to manually link my VS project to the libraries. To get around this I tried using CMake to generate a Visual Studio project but nothing I try seems to work. A number of permutations each seem to give different errors, either include errors or linking errors. Some won't even configure with CMake!<br>
<br>Could someone please explain, in clear steps how one goes about building and linking to VTK?<br><br>Thanks very much,<br>Dan<br><br>(I'm not a novice but after three days trying to sort this out I'm out of ideas!)<br>
<br> </div></div>
<br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/vtkusers" target="_blank">http://public.kitware.com/mailman/listinfo/vtkusers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Christopher Mullins<div>R&D Engineer</div><div>Kitware Inc.,</div><div><a>919.869.8871</a></div>
</div></div></div></div> </div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Christopher Mullins<div>R&D Engineer</div><div>Kitware Inc.,</div><div><a>919.869.8871</a></div>
</div></div></div></div> </div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Christopher Mullins<div>R&D Engineer</div><div>Kitware Inc.,</div><div><a href="tel:919.869.8871" value="+19198698871" target="_blank">919.869.8871</a></div>
</div></div></div></div> </div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Christopher Mullins<div>R&D Engineer</div><div>Kitware Inc.,</div><div>919.869.8871</div>
</div>