[CMake] How to create a 64-bit Windows build of cmake?

John R. Cary cary at txcorp.com
Tue Aug 2 08:50:40 EDT 2011


Thanks for your response.  This will definitely decrease my headpain.

It turns out that I need vtk-5.0.0, but right now I am not sure
that I need the wrapping code.  Am checking on this.

Would it make sense to just not call vtkLoadCMakeExtensions.cmake?

Thx....John Cary

On 8/2/11 5:00 AM, David Cole wrote:
> On Tue, Aug 2, 2011 at 7:00 AM, David Cole<david.cole at kitware.com>  wrote:
>> On Mon, Aug 1, 2011 at 8:34 PM, John R. Cary<cary at txcorp.com>  wrote:
>>> I believe I have followed what I have found on the web for
>>> building a Win64 version of CMake.  I have downloaded the
>>> win32 version and used it to configure the cmake source.
>>> I used the Visual Studio 9 2008 Win64 generator.
>>>
>>> However, when I then use that cmake to configure vtk (an
>>> old version, 5.0.0) I get the much discussed error,
>>>
>>> -- Loading VTK CMake commands
>>> CMake Error at CMake/vtkLoadCMakeExtensions.cmake:7 (LOAD_COMMAND):
>>>   load_command Attempt to load the library
>>>   C:/winsame/cary/builds-vs9/composerall/vtk-5.0.0i/ser/CMake/cmVTK_WRAP_TCL2.dll
>>>   failed.  Additional error info is:
>>>
>>>   The application has failed to start because its side-by-side configuration
>>>   is incorrect.  Please see the application event log or use the command-line
>>>   sxstrace.exe tool for more detail.
>>>
>>> Call Stack (most recent call first):
>>>   CMake/vtkLoadCMakeExtensions.cmake:27 (VTK_LOAD_SINGLE_CMAKE_EXTENSION)
>>>   CMakeLists.txt:632 (VTK_LOAD_CMAKE_EXTENSIONS)
>>>
>>>
>>> CMake Error at CMake/vtkLoadCMakeExtensions.cmake:11 (MESSAGE):
>>>   Loading VTK command VTK_WRAP_TCL2 - failed
>>> Call Stack (most recent call first):
>>>   CMake/vtkLoadCMakeExtensions.cmake:27 (VTK_LOAD_SINGLE_CMAKE_EXTENSION)
>>>   CMakeLists.txt:632 (VTK_LOAD_CMAKE_EXTENSIONS)
>>>
>>> Using sxstrace shows
>>>
>>> INFO: Parsing Manifest File
>>> C:\winsame\cary\builds-vs9\composerall\vtk-5.0.0i\ser\CMake\cmVTK_WRAP_TCL2.dll.
>>>     INFO: Manifest Definition Identity is (null).
>>>     INFO: Reference:
>>> Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
>>> INFO: Resolving reference
>>> Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
>>>     INFO: Resolving reference for ProcessorArchitecture amd64.
>>>
>>> which seems to indicate that even though I built cmake with the VS9-Win64
>>> generator, cmake somehow created the dll as win32?  Even though cmake
>>> says,
>>>
>>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
>>> Studio
>>> 9.0/VC/bin/amd64/cl.exe
>>>
>>>
>>> showing that it found the 64-bit compiler?
>>>
>>> Any hints on what to do next?
>>>
>>> Thx...John Cary
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the CMake FAQ at:
>>> http://www.cmake.org/Wiki/CMake_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.cmake.org/mailman/listinfo/cmake
>>>
>> This is a problem with VTK 5.0, not a problem with CMake...
>>
>> Since VTK 5.0, the "loaded custom CMake commands" have been eliminated
>> from VTK for just this reason. Can you use VTK 5.2, 5.4 or 6.5
>> instead...? (I'm not 100% sure exactly when that problem was fixed,
>> but a more recent VTK should fix this issue.)
>>
> make that "5.2, 5.4 or **5.6**"...
>



More information about the CMake mailing list