[Insight-developers] Unable to build on VS 10 Express

[Brad King]

On 03/25/2011 06:04 PM, Bill Lorensen wrote:
> You need the HEAD of cmake. The fixes are to cmake.

More specifically, the bug is in VS itself in that it cannot handle
relative paths if the current working directory plus the relative
path exceeds something like 250-ish characters.  The "fix" in CMake
is to workaround the VS bug by using full paths.

This same problem could have been hit with older ITK too if one used
a source and build tree with a long enough path.  Modular ITK ends up
with longer paths than monolithic ITK did because the directory structure
is so hierarchical now.

-Brad K

> On Fri, Mar 25, 2011 at 3:41 PM, Bradley Lowekamp
> <blowekamp at mail.nih.gov <mailto:blowekamp at mail.nih.gov>> wrote:
> 
> 
>     So in the latest version these errors went away:
>>
>>     5>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itkv3p_netlib-4.0.lib'
>>     3>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itkv3p_netlib-4.0.lib'
>>     2>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itkv3p_netlib-4.0.lib'
>>     7>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itktestlib-4.0.lib'
>>     4>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itkv3p_netlib-4.0.lib'
>>     6>LINK : fatal error LNK1104: cannot open file
>>     '..\..\..\..\..\..\..\..\lib\Debug\itktestlib-4.0.lib'
> 
>     But the GDCM errors are still there. However, I can disable the GDCM
>     IO module, even though I still get the error when trying to build
>     GDCM, ITK doesn't need it. So I can proceed with my SimpleITK
>     development.