Re: [Nant-users] cl task and paths with white spaces

[Ian M. <ianm@ActiveState.com>]

Derek,

> I hope this hasn't been asked a thousands times - I'm new
> to NAnt.
No it hasn't otherwise it would have been fixed by now. This was a bug. 
Thanks for posting it. Everything else ( include dirs and such ) was 
quoted but not the source files.
I've committed a fix for this in cvs. It updates the cl, lib and link tasks.
you can sync the cvs tree or get the latest nightly to pick up this fix.

Ian



> I am attempting to use the "cl" task.  The path in which
> my source files reside has white spaces in it.  When NAnt
> turns the sources into arguments to cl, the arguments are
> not enclosed in quotes and cl barfs.
> 
> Here's the target:
> 
> 	<target name="release">
> 		<property name="build" value="Release"/>
> 		<cl outputdir="${build}" verbose="true" options='...'>
> 			<sources>
> 				<includes name="*.cpp"/>
> 			</sources>
> 		</cl>
> 	</target>
> 
> (the *.cpp files reside in "C:\My Stuff")
> 
> The build fails:
> 
> cl
> ...
>    /Fo"C:\My Stuff\Release/"
>    C:\My Stuff\Info.cpp
> 
> cl : Command line warning D4024 : unrecognized source file type 'C:\My',
> object file assumed
> cl : Command line warning D4027 : source file 'C:\My' ignored
> 
> 
> Since Nant invokes cl on my behalf, I don't know how to
> cause each source to be treated as an argument (ie., 
> surrounded by quotes).
> 
> thanks!
> Derek
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nant-users mailing list
> Nan...@li...
> https://lists.sourceforge.net/lists/listinfo/nant-users