BUG: INCLUDE File Is Not Scanned CorrectlyLast reviewed: December 11, 1995Article ID: Q123172 |
The information in this article applies to:
SYMPTOMSWhen using a relative path reference, in the "INCLUDE" command or the metacommand "$INCLUDE", to include files into a FORTRAN source file, the correct dependencies may not be recognized.
CAUSEThe build engine in the Visual Workbench, provided with PowerStation, does not correctly parse the include string when relative paths are used.
RESOLUTIONUse the fully qualified paths instead.
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.
MORE INFORMATION
Sample CodeThe following code sample demonstrates the problem. Build the project; then make a change to one of the include files and select build again. The workbench will indicate that the .EXE file is up to date. To resolve the problem, specify the full paths for the include files ($INCLUDE 'c:\testing\inc1.inc' and INCLUDE 'c:\testing\inc2.inc'), save the sourcefile and scan all dependencies. Any change in the include files will properly cause the source file to be recompiled. Compile options needed: none File inc1.inc: print*, "Inside inc1.inc"File inc2.inc: print*, "Inside inc2.inc" PROGRAM test$INCLUDE '\testing\inc1.inc' INCLUDE '\testing\inc2.inc' PRINT*, 'in test' END |
Additional reference words: 1.00a 1.00 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |