[vtkusers] Building 64bit vtk on Vista using Visual Studio 2008

[John Drescher]

On Sun, May 10, 2009 at 12:15 PM, John Drescher <drescherjm at gmail.com> wrote:
>> I just opened up cmake-gui and selected Visual Studio 9 WIN64 and then
>> opened the solution in VS2008 and compiled. It is building for x64
>> right now but did not finish yet.\
>>
> I did not say but I did do two Configures and a Generate in
> cmake-gui.. Still building. This is on a laptop with a mechanical disk
> so it will take some time...
>

Result, It built only 1/2 of the projects and does have WIN32 defined.

1>------ Build started: Project: vtksys, Configuration: Debug x64 ------
1>Generating vtksysProcessFwd9xEnc.c
2>------ Build started: Project: vtkRendering, Configuration: Debug x64 ------
2>Generating vtkShadowMapPassShader_vs.cxx, vtkShadowMapPassShader_vs.h
2>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.
2>Project : error PRJ0019: A tool returned an error code from
"Generating vtkShadowMapPassShader_vs.cxx,
vtkShadowMapPassShader_vs.h"
2>Build log was saved at
"file://c:\Programming\VC.90\vtk\Rendering\vtkRendering.dir\Debug\BuildLog.htm"
2>vtkRendering - 1 error(s), 0 warning(s)
1>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.
1>Project : error PRJ0019: A tool returned an error code from
"Generating vtksysProcessFwd9xEnc.c"
1>Build log was saved at
"file://c:\Programming\VC.90\vtk\Utilities\kwsys\vtksys.dir\Debug\BuildLog.htm"
1>vtksys - 1 error(s), 0 warning(s)
3>------ Build started: Project: ProcessShader, Configuration: Debug x64 ------
4>------ Build started: Project: vtkVolumeRendering, Configuration:
Debug x64 ------
4>Generating vtkVolumeTextureMapper3D_TwoDependentShadeFP.cxx,
vtkVolumeTextureMapper3D_TwoDependentShadeFP.h
3>Linking...

>From a quick google search this looks like a microsoft problem. I will
attempt to fix this later today..

John