Article ID: 150616
Article Last Modified on 12/8/2003
APPLIES TO
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 4.1 Subscription
- Microsoft Visual C++ 4.2 Enterprise Edition
- Microsoft Visual C++ 4.2 Professional Edition
This article was previously published under Q150616
SYMPTOMS
When you use the nmake utility to build a project containing a subproject
of type makefile that does not use nmake as its command, the subproject is
not built. However, the subproject can be built from Developer Studio.
RESOLUTION
There are two ways to resolve the problem:
- Build the project and sub-project separately. This requires either
typing in a batch file or makefile that calls nmake once for each
configuration.
-or-
- When you insert a project of type makefile, rather than changing the
Command line to execute something other than nmake, specify a makefile
which you create. Then create a makefile that executes the command you
would use instead of nmake.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes
available.
REFERENCES
For additional information, please see the following article in the
Microsoft Knowledge Base:
145936 How to Insert Existing Projects as Sub-Projects
Also see "Creating an External Project" from the Visual C++ online
documentation.
Additional query words: kbVC400bug 4.00 4.10 4.20 VWBIss
Keywords: kbide KB150616