PRB: Special Characters in Path Cause NMake Error U1007

Last reviewed: July 25, 1997
Article ID: Q121018
The information in this article applies to:
  • The Visual Workbench included with: - Microsoft Visual C++, 32-bit Edition, versions 2.0, 2.1, 4.0, 5.0

SYMPTOMS

Building a project that uses one of the special characters shown below works correctly in the Visual Workbench. But an attempt to build the same project from a command session fails, returning this error:

   test.mak(98) : fatal error U1007: double quotation mark not
   allowed in name
   Stop.

CAUSE

This is limitation of the NMAKE utility included with the products listed above. The following legitimate characters cause this problem:

   $, %, @, #, !, ^, (, ), {, }, [, ], -, and the space character.

When one of them is used in a path specification, Visual C++ puts quotation marks around the file specification in several places within the makefile. NMAKE cannot process files specified in this way.

WORKAROUND

To work around this problem:

  • Avoid using any of these special characters.

          -or-
    
  • Modify the makefile to remove the quotation marks and use the project as an external makefile when using the Visual C++ Workbench to launch the build.

          -or-
    
  • Always use the Visual C++ Workbench to build the project.


Additional query words: quotes
Keywords : NmakeIss VwbIss
Version : 2.0 2.1 4.0 5.0
Platform : NT WINDOWS
Issue type : kbprb
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.