FIX: "Failed to (or don't know how to) build" Warning

 Last reviewed: September 19, 1997
Article ID: Q140450

The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2

SYMPTOMS

When building an OLE Control project in Visual C++ versions 4.0, 4.1, or 4.2 that was created in version 2.2, you may receive the following warning: 

  Failed to (or don't know how to) build 'D:\test\Ocx22\$(OUTDIR)\OCX22.tlb
where OCX22.tlb is the type library for the OLE Control.

CAUSE

This error occurs if the type library does not already exist or under the following circumstances:

  • The Visual C++ 2.2 project has not been built as a Visual C++ 2.2 project before it is converted to Visual C++ 4.0, 4.1, or 4.2 and then Built under Visual C++ 4.0, 4.1, or 4.2.

    -or-

  • The .tlb file is deleted and rebuilt. Note that deleting the .tlb file occurs when you delete the obj32 build directory.

In either of these cases, if you choose Rebuild All, the error does not appear; nor does it appear in subsequent builds unless the type library is deleted.

RESOLUTION

This warning can be safely ignored. The OLE Control should compile and run without problems.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ version 5.0. 

Keywords          : NmakeIss vcbuglist400 vcfixlist500 kbprg
Version           : 4.0 4.1 4.2
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

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