PWB Does Not Automatically Update Include Dependencies

 Last reviewed: July 17, 1997
Article ID: Q84955
1.00 1.10 2.00 2.10.49 | 1.00 1.10 
MS-DOS                 | OS/2
kbtool

The information in this article applies to:

  • Microsoft Programmer's Workbench for MS-DOS, versions 1.0, 1.1, 2.0, and 2.1.49
  • Microsoft Programmer's Workbench for OS/2, versions 1.0 and 1.1

SUMMARY

The Programmer's WorkBench (PWB) versions 1.0, 1.1, and 2.0 do not automatically update the include dependencies if include statements are added to source code after a program list/project has been saved. The include dependencies are updated when the list is saved again. This is also documented on pages 47-48 of the "Microsoft C/C++ Environment and Tools" manual for version 7.0.

MORE INFORMATION

When a project is created, the include dependencies are added to the target dependency blocks. This is done by scanning the source code for 

#include statements. These statements can occur in source files (such
as .C files), header files (.H files), and resource scripts (.RC files).

If #include statements are subsequently added to files in the program list, they are not added to the makefile as dependencies until the program list is edited and saved. No actual changes to the list are required. Saving the list causes the include dependencies to be re-evaluated. To summarize, use the following procedure to update the include dependencies:

In PWB Versions 1.x

  1. Select Make from the main PWB menu.

  2. From the Make menu, choose Edit Program List.

  3. Choose Save List.

In PWB version 2.0

  1. Select Project from the main PWB menu.

  2. From the Project menu, choose Edit Project.

  3. Choose Save Project.

Additional reference words: kbinf 1.00 1.10 2.00 7.00 2.1.49 PWBIss
KBCategory: kbtool
KBSubcategory: PWBIss
Keywords : kb16bitonly

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