BUG: Visual C++ Doesn't Generate Dependencies for .RSC FilesLast reviewed: July 22, 1997Article ID: Q135287 |
The information in this article applies to:
SYMPTOMSIf a .RSC file, which is an output file of a resource compiler, is included in a .R file, which is a Macintosh resource file, using either of the following statements, the Visual Workbench will not generate dependencies for it:
// resource.r #include "mrc\types.r" #include "mrc\balloons.r" include "wlm.rsc"; include "commdlg.rsc"; #include "ftab.r"then, when generating the dependencies for this file, the Visual Workbench will not include WLM.RSC or COMMDLG.RSC in the dependencies list. If any of these .RSC files or the .RC/.R file used to generate the .RSC file changes, the .RSC file will not be rebuilt. Dependencies are correctly generated for files included with #include, such as, MRC\TYPES.R, MRC\BALLOONS.R, and FTAB.R.
CAUSEDependencies are not generated for resources included with the INCLUDE statement because while it is legal to include *.RSC using the include <filename> syntax, the Visual C++ build system cannot handle this type of .RSC build.
WORKAROUNDUse one of the following workarounds:
STATUSMicrosoft 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. |
Keywords : VCMac VWBIss
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |