BUG: PWB May Record Incorrect Paths for Dependencies in Makefile

 Last reviewed: July 17, 1997
Article ID: Q67780
1.00 1.10 | 1.00 1.10 
MS-DOS     | OS/2
kbtool kbbuglist

The information in this article applies to:

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

SYMPTOMS

Creating a program list with dependencies in directories other than the project (makefile) directory may result in the Programmer's WorkBench (PWB) version 1.0 and 1.1 recording the wrong paths to these dependencies.

RESOLUTION

Changing the location of the project makefile or changing the names of the subdirectories will generate the correct paths for dependencies in the makefile.

STATUS

Microsoft has confirmed this to be a problem in PWB versions 1.0 and 1.1. We are researching this problem and will post new information here as it becomes available.

MORE INFORMATION

The following steps illustrate the problem:

  1. Create subdirectories named TEST and TESTA under the same directory, with sample files FILE1.C in TEST and FILE2.C in TESTA.

  2. Invoke PWB from the TESTA directory.

  3. Create a program list.

  4. Add FILE1.C and FILE2.C with full path.

  5. Save the list.

The resulting makefile will contain the line: 

   OBJS = file2.c file1.c
The correct line should read: 

   OBJS = file2.c ..\TEST\file1.c

Additional reference words: 1.00 1.10 buglist1.00 buglist1.10
KBCategory: kbtool kbbuglist
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.