FIX: Internal Make Facility Ignores Response (@) File

ID: Q128555

The information in this article applies to:

The development environment, included with: Microsoft Visual C++ for Windows, versions 1.0, 1.5, 1.51, 1.52

SYMPTOMS

A response (@) file added to the Compiler Custom Options is ignored by the development environment's internal make facility.

NOTE: To enter Compiler Custom Options, choose Project from the Options menu, and then select Custom Options under Compiler.

If, however, the project makefile is compiled using the NMAKE.EXE utility or if the makefile is used as an external makefile, the response file is parsed and used.

RESOLUTION

If a response (@) file is required, use the makefile as an external makefile to force usage of the external NMAKE.EXE facility, or compile from the command line by using the NMAKE.EXE program.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Visual C++, 32-bit edition, version 2.0.

MORE INFORMATION

A similar problem occurs when you add a response file to the Miscellaneous Linker Project Options. After adding the response file, the following link error is reported when building in IDE:

   Fatal Error L1021: cannot nest response files
   Link returned error code 2.

If a customized response file is needed for the linker, use the makefile as an external makefile in the development environment, or use the NMAKE.EXE utility.

Additional reference words: 1.00 1.50 VWB workbench IDE KBCategory: kbtool kbfixlist kbbuglist KBSubcategory: VWBIss

Keywords          : kbenv kb16bitonly kbide kbVC kbVC100bug kbVC150bug kbVC151bug kbVC152bug kbVC200fix kbGrpDSTools kbbuglist kbfixlist
Version           : 1.00 1.50 1.51 1.52
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

Last Reviewed: October 3, 1998