unusual INCLUDE hierarchy

[Robinson__Donald]

I'm having trouble getting Dev Studio to use the INCLUDE files I want. Here is a simplified example to show the problem.

I have source code and include files in two directories /d1 and /d2. There are 2 slightly different copies of an INCLUDE file 'parms.f77' in both directories. In this project, the version of 'parms.f77' in /d1 is never supposed to be used; even by source routines in /d1: the copy in /d2 is always used.

I've tried to modify settings under Tools | Options as well as the 'USE and INCLUDEPaths' settingsunder Project | Settings | Fortran | Preprocessor without any success. Although these settings are able to correctly point to /d2/parms.f77 when referenced bymost source files in the project, source files in /d1 always use /d1/parrms.f77. I've also tried dragging into the project the External include files, and then deleting them. Still no success.

For a variety or reasons - principally a shared code base -I can't just delete /d1/parms.f77 from the system permanently,although it would be OK if I could somehow automatically erase it each time I did a build. (My source control would still have a copy). My preferred solution would be to have the correct information in the DSP file

Is it possible to do what I want? Any advice would be very welcome.

[Steven_L_Intel1]

This is CVF, right? What version? My memory on this issue is a bit fuzzy, but I know there was a bug where the directory of the source was always used - the /assume:[no]source_include switch just determined where in the list it would go. I don't know if it ever got fixed in CVF.

[Robinson__Donald]

Hi Steve - This is CVF Standard 6.6c.

[Steven_L_Intel1]

Thought so. I don't know of a good solution for you.

[Robinson__Donald]

Thanks very much. Two possibilities come to mind: (1) do you know if there are any plans to keep producing CVF patches; (2) does the Intel product (which appears to bemuch more current!) get this right?

[Steven_L_Intel1]

There are no plans for future CVF updates.

This is fixed in the current Intel Visual Fortran (was fixed in late December.)

[sgongola]

Steve,

I think this is the problem I reported to CVF support in june, 2002:
#CVF18049: /assume:nosource_include does not seem to work correcly.

Unfortunately, it was not fixed with any of the CVF updates released since then and I have been working around it by ensuring that the needed include was always present in the same directory as the source file.

sol

[Steven_L_Intel1]

Yes, I remember that. As you note, it wasn't fixed for CVF.