[CMake] CMake 2.4.3, VTK 5.0.2, VS 2005 Express
James Bigler
bigler at cs.utah.edu
Fri Nov 10 09:01:24 EST 2006
David Cole wrote:
> Ah...
>
> Perhaps adding "/MANIFEST" to CMAKE_EXE_LINKER_FLAGS,
> CMAKE_MODULE_LINKER_FLAGS and CMAKE_SHARED_LINKER_FLAGS is what you
> need, then. I can't recall exactly why this is needed in some
> circumstances and not others, but I have had to add these manually in
> some projects using VS8 and CMake 2.4.3 -- I think it's a bug that's
> fixed in CVS CMake...
I haven't tried CMake CVS, but your suggestion seemed to work. This
didn't help the VS 8 project generator, though.
>> D:\rei\vtk-5.0.2\VS
> Certainly looks short enough to me.
>
> HTH,
> Dave
>
>
> On 11/9/06, James Bigler <bigler at cs.utah.edu> wrote:
>> David Cole wrote:
>> > Some of these try-compile tests end up failing if your path name is too
>> > long
>> > on Windows. Are you building under a super-long directory name under
>> > your My
>> > Documents folder, perhaps?
>> >
>> > You may start to run into trouble with path names as short as 100
>> > characters
>> > long or so, believe it or not because of the way some of the
>> relative paths
>> > are constructed for use by the CMake/Visual Studio combination...
>> Try using
>> > "C:\VTKbuild" or something similarly short as the root of your build
>> tree.
>>
>> I'll try this, but my build path seems short enough:
>>
>> D:\rei\vtk-5.0.2\VS
>>
>> I think the try compiles are failing, because the programs fail to run
>> properly due to some msvcr80.dll (manifests) issue. I can see in the
>> output that the files built fine, but the run result is a string of
>> garbled characters.
>>
>> James
>>
>> > HTH,
>> > David
>> >
>> > On 11/9/06, James Bigler <bigler at cs.utah.edu> wrote:
>> >>
>> >> I'm trying to build VTK 5.0.2 with Visual Studio 2005 Express Edition.
>> >> I need to build libraries in order to make some plugins for another
>> >> application. I'm also using CMake 2.4.3 on WinXP.
>> >>
>> >> I've been able to build other things with VS 2005 IDE. In fact, I can
>> >> build another open source package teem (http://teem.sourceforge.net)
>> >> with CMake using VS 2005 IDE and nmake (which needed a hack to include
>> >> Windows SDK includes).
>> >>
>> >> I tried following these instructions with no success.
>> >>
>> >>
>> >>
>> http://www.cmake.org/Wiki/CMake_Generator_Specific_Information#How_to_generate_NMake_Makefiles_using_Visual_C.2B.2B_Express_Edition_.28free_Visual_Studio_8.29
>>
>> >>
>> >>
>> >> If I use the Visual Studio 8 generator the configure fails when
>> checking
>> >> the endianness of the machine. This may be because of the msvcr80.dll
>> >> and manifest issue. I haven't been able to find much information
>> on the
>> >> mailing lists about this.
>> >>
>> >> The nmake generator completes, but complains about manifests. If I
>> >> restart the build it seems to get further.
>> >>
>> >> [ 1%] Building CXX object
>> >> Utilities/kwsys/CMakeFiles/vtksys.dir/CommandLineArgu
>> >> ments.obj
>> >> CommandLineArguments.cxx
>> >> Linking CXX shared library ..\..\bin\vtksys.dll
>> >> Creating library ..\..\bin\vtksys.lib and object
>> ..\..\bin\vtksys.exp
>> >>
>> >> ..\..\bin\vtksys.dll.manifest : general error c1010070: Failed to load
>> >> and parse the manifest. The system cannot find the file specified.
>> >> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> >> 8\VC\BIN\mt.EXE"' : return code '0x1f'
>> >> Stop.
>> >> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> >> 8\VC\BIN\nmake.exe"' : return code '0x2'
>> >> Stop.
>> >> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
>> >> 8\VC\BIN\nmake.exe"' : return code '0x2'
>> >> Stop.
>> >>
>> >> Perhaps there is a wrong dependency chain? It did seem to build
>> after I
>> >> restarted nmake 30 times or so.
>> >>
>> >> Thanks,
>> >> James
>> >> _______________________________________________
>> >> CMake mailing list
>> >> CMake at cmake.org
>> >> http://www.cmake.org/mailman/listinfo/cmake
>> >>
>> >
>>
More information about the CMake
mailing list