BUG: Resource Dependency Scans May Be Incomplete

 Last reviewed: July 22, 1997
Article ID: Q128834
The information in this article applies to:
  • Microsoft Visual C++ Cross-Development Edition for Macintosh, version 2.0

SYMPTOMS

File dependencies generated by include statements in .R files may not be added to a Macintosh project.

CAUSE

Projects that target both Macintosh and Win32 may include resource (.R) files that are used in building the Macintosh target but that are not part of the Win32 build process. Here are two scenarios that may cause dependencies generated by .R files to be ignored:

  • When a project is first created.
  • When Win32 is targeted and 'Update All Dependencies' is chosen.

In both these cases, the Win32 target tree is scanned to generate dependencies for the project. Because .R files are not part of the Win32 build process, a dependency on files included by .R files will not be updated correctly.

RESOLUTION

To update a dependency on files included in .R files, set the Target to Macintosh prior to choosing Update All Dependencies.

STATUS

Microsoft has confirmed this to be a bug in Visual C++ version 2.0 Cross Development Edition for Macintosh. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

In addition to the problems already mentioned, a dependency on a file may not be updated if the file contains //{{NO_DEPENDENCIES}} as the first line in the file. This preprocessor comment is frequently used in the RESOURCE.H file. It forces the development environment to ignore changes to the file.

Keywords : VCMac
Version : 2.0 2.1
Platform : MACINTOSH NT WINDOWS
Issue type : kbbug

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