Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

C++ projects fail to build if path contains a space
valeriec
#1 Posted : Thursday, December 3, 2015 11:43:51 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/3/2015(UTC)
Posts: 3
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
We have a very large solution in VS 2013, and a few of the projects are C++ projects. NCrunch has no problem building them, except if they are located in a folder that contains a space in the name. The error we were seeing was:

"cmd.exe exited with code 9009"

I was trying to look at the logging output and realized the path had a space - renamed the folder to remove the space, and all is well.
Remco
#2 Posted : Friday, December 4, 2015 1:37:42 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for sharing this issue. Can you confirm exactly which property in the build XML this applies to?

Edit: Sorry, just realised you were referring to the actual build location (not a build property in the XML file). Does this mean that the NCrunch workspace base path is causing the problem? http://www.ncrunch.net/documentation/reference_global-configuration_workspace-base-path
valeriec
#3 Posted : Friday, December 4, 2015 3:20:56 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/3/2015(UTC)
Posts: 3
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
The space was in the path to my source files. It looks like for C++ projects nCrunch copies the folder structure all the way up to 1-level below the drive letter. For example:

"C:\some words\dev\blah\blabiddy\solutionFolder"

In the nCrunch workspace I see the folder structure has been copied starting with the "some words" folder. I only see it being copied this far up the path for the C++ projects.
Remco
#4 Posted : Friday, December 4, 2015 10:13:06 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Gotcha - thanks. Do you have any record of which template the project files were created from? Changing the NCrunch workspace base path will let you work around this, but I think I can provide a better experience from the NCrunch side if I have a way to detect the project type.
valeriec
#5 Posted : Friday, December 4, 2015 10:22:06 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/3/2015(UTC)
Posts: 3
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
I'm not 100% sure - these projects have been around since before I started working here in 2010. But my guess is they were created from the Visual C++/CLR/Class Library template in Visual Studio (or whatever its equivalent was in VS 2010, we are using 2013/2015 now).
1 user thanked valeriec for this useful post.
Remco on 12/4/2015(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.035 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download