MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012232CMakeCMakepublic2011-05-28 15:262016-06-10 14:31
ReporterFelix Nawothnig 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformWin32OSOS Version
Product VersionCMake 2.8.4 
Target VersionFixed in Version 
Summary0012232: CMake possibly fails to launch devenv.com when disable8dot3 is set on NTFS
DescriptionCMake applies GetShortPathName() on the compiler path with the purpose to generate a space-free string - this doesn't work if the path to devenv.com a) contains a directory with spaces (which it usually does, due to the "Microsoft Visual Studio X" directory) and b) said directory was created (e.g. MSVC was installed) when disable8dot3 was set to 1.

The resulting error is rather cryptic - "Check for working C compiler" fails with the error message "%1 is not a valid Win32 application" (including the verbatim %1), as a result of CreateProcess() trying to launch the file "C:\Progra~2\Microsoft".

Steps To Reproduce
Additional InformationAs a workaround the user can give the MSVC directory a short-name, after which cmake works fine:

> fsutil.exe behavior set disable8dot3 0
> fsutil.exe file setshortname "Microsoft Visual Studio 9.0" msvc~90
> fsutil.exe behavior set disable8dot3 1
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-05-28 15:26Felix NawothnigNew Issue
2012-08-11 11:09David ColeStatusnew => backlog
2012-08-11 11:09David ColeNote Added: 0030262
2016-06-10 14:28Kitware RobotNote Added: 0041844
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030262)
David Cole   
2012-08-11 11:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041844)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.