BUG: NMAKE Build Fails When Intermediate Dir Starts with ..\

 Last reviewed: May 12, 1997
Article ID: Q168420
The information in this article applies to:
  • The development environment included with: - Microsoft Visual C++, 32-bit Editions, version 5.0

SYMPTOMS

If your intermediate directory starts with ..\ and you export a makefile for the project, the makefile may not be written correctly. The result is that some or all files in the project may not compile.

RESOLUTION

  1. Change the intermediate directory to start with .\..\ instead of ..\.

  2. Export a new makefile for the project.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a default Appwizard application.

  2. Select Project:Settings:General.

  3. Change the intermediate directory for the debug build to ..\debug.

  4. Run "Export Makefile" from the project menu.

  5. Open a Command Shell and run vcvars32.bat from the <msdevpath>\bin directory.

  6. Build the exported makefile using nmake /a /f <makefile>. You get the following error:

    LINK : fatal error LNK1104: cannot open file ".\..\Debug\Appwz50.obj" NMAKE : fatal error U1077: 'link.exe' : return code '0xa'

  7. Now change the intermediate directory for the debug build to .\..\debug.

  8. Repeat steps 4 – 6 and not that the project builds successfully.

Keywords : kbtool vcbuglist500 VWBIss kbbuglist
Version : 5.0
Platform : NT WINDOWS
Issue type : kbbug

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: May 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.