Re: [nant-dev] UPDATE: BUG: Visual-Cpp tasks fail when path for response file contains a space.

2003-11-18 Thread James C. Papp
Yes, you're absolutely right.  The version of NAnt we are using for our builds 
is based off the 8.3 release.  When I found the error in the Visual-Cpp tasks, 
I first checked to see if it was already fixed in the nightly builds, then 
patch our version of the source.  Once that was fixed, we noticed the same 
problem with CSC, and just assumed it was a general problem without checking 
the nightly version again.Sorry about that!

BTW, thanks for adding the fix for the Visual-Cpp tasks.
James.

Quoting Gert Driesen [EMAIL PROTECTED]:

 James,
 
 I fixed the issues in the Visual Cpp tasks (should be available in the next
 nightly build), but I fixed this for the csc compiler before ...
 
 What version of NAnt are you using ?
 
 Gert
 
 - Original Message -
 From: James C. Papp [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, November 17, 2003 11:57 PM
 Subject: [nant-dev] UPDATE: BUG: Visual-Cpp tasks fail when path for
 response file contains a space.
 
 
  It seems that this a general problem with anything that creates a response
  file.  I'm seeing the same error the CSC compiler as well.
 
  James.
 
  Quoting James C. Papp [EMAIL PROTECTED]:
 
   BUG: Visual-Cpp tasks fail when path for response file contains a space.
  
   The code currently looks something like this:
  
   ...
 public override string ProgramArguments {
   get {
 ...
 if (Verbose) {
   return @ + _responseFileName;
 } else {
   return /nologo @ + _responseFileName;
 }
 ...
   }
 }
   ...
  
   To fix the bug it should be:
  
   ...
 public override string ProgramArguments {
   get {
 ...
 if (Verbose) {
   return @\ + _responseFileName + \;
 } else {
   return /nologo @\ + _responseFileName + \;
 }
 ...
   }
 }
   ...
  
   This bug is in ClTask.cs, LibTask.cs, and LinkTask.cs.
  
   For some of you, it may appear that the build works just fine even when
 the
   temporary response file contains spaces in its path.  This can happen if
 the
   path passed to CL is converted to the old DOS 8.3 short-form, which
 removes
   any spaces automatically.  In fact, this was exactly what was happening
 to
   me;
   I've only notice the problem when I disabled support for 8.3 filename
   creation
   on my NTFS volume.
  
   I verified that the bug still exists in the latest nightly build; it
 would be
   great if someone could add these small changes into CVS.
  
   Thanks!
   James.
  
 
 
 
 
  ---
  This SF. Net email is sponsored by: GoToMyPC
  GoToMyPC is the fast, easy and secure way to access your computer from
  any Web browser or wireless device. Click here to Try it Free!
  https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
  ___
  nant-developers mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/nant-developers
 
 
 
 




---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] UPDATE: BUG: Visual-Cpp tasks fail when path for response file contains a space.

2003-11-17 Thread James C. Papp
It seems that this a general problem with anything that creates a response 
file.  I'm seeing the same error the CSC compiler as well.

James.

Quoting James C. Papp [EMAIL PROTECTED]:

 BUG: Visual-Cpp tasks fail when path for response file contains a space.
 
 The code currently looks something like this:
 
 ...
   public override string ProgramArguments {
 get {
   ...
   if (Verbose) {
 return @ + _responseFileName;
   } else {
 return /nologo @ + _responseFileName;
   }
   ...
 }
   }
 ...
 
 To fix the bug it should be:
 
 ...
   public override string ProgramArguments {
 get {
   ...
   if (Verbose) {
 return @\ + _responseFileName + \;
   } else {
 return /nologo @\ + _responseFileName + \;
   }
   ...
 }
   }
 ...
 
 This bug is in ClTask.cs, LibTask.cs, and LinkTask.cs.
 
 For some of you, it may appear that the build works just fine even when the
 temporary response file contains spaces in its path.  This can happen if the
 path passed to CL is converted to the old DOS 8.3 short-form, which removes
 any spaces automatically.  In fact, this was exactly what was happening to
 me;
 I've only notice the problem when I disabled support for 8.3 filename
 creation
 on my NTFS volume.
 
 I verified that the bug still exists in the latest nightly build; it would be
 great if someone could add these small changes into CVS.
 
 Thanks!
 James.
 




---
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers