fpp behavior

[netphilou31]

Hi,

I don't unsderstand the following fpp strange behavior:

With CVF 6.6 a compilation directive such as:

#include "V:Sourcesconst.h"

associated with fpp:"-m" works correctly but the same declaration with IVF leads to the following error :

#error: can't find include file: V:Sourcesconst.h

If I change the declatation to :

#include "..Sourcesconst.h"

The compilation is successful. How can I use absolute paths with the fpp in IVF ?

regards,

[Steven_L_Intel1]

I can't reproduce the problem. Are you sure that the absolute path is correct? I can't think of how fpp would do anything special for file paths.

[netphilou31]

Thanks Steve for your answer.

Unfortunately, I'm sure that the path is correct (if I right-click on the filename from the source editor and I select "open V:Sourcesconst.h" the file is found and opened correctly !). You should note that the fpp version with CVF 6.6 behaves normally (with the same source file). I have only noticed this problem with the fpp version delivered with IVF 9.0 (which uses differents options, may be one could solve the problem but I don't know which of them ?). The last thing that you need to know is that the drive V: is a substituted drive; but if I replace it with the original path, the same problem arises.

Regards,

[Steven_L_Intel1]

The fpp processors in CVF and IVF are different. Which specific version of IVF do you have? 9.1.025 is current (though 9.1.027 will be out in the next couple of days.)

I can see one other report of this problem, but the customer did not send us a test case. I suggest that you submit an issue to Intel Premier Support and attach a test case. Add a note for the Intel support engineer to also see Q379355.

[jimdempseyatthecove]

My problem with fpp is different but my solution may be the same.

I use fpp not only for my Fortran projects but also for script files that are used to control input parameters to the application (simulator). Back when IVF changed from V8.n to V9.0 something changed in FPP. My application would compile properly but the script files would not be parsed correctly by FPP..

The solution was to use the older FPP on the script files. You could probably use CPP or the FPP from CVF if you must.

The other option to consider is to create a path relative temp folder for the include files. Then make a "project" file that freshens the files in the path relative temp folder from the files on the mapped drive. Essentially the build operation is a COPY command.

The other option might be to add "V:Sources" to the include path

Jim Dempsey

[Steven_L_Intel1]

I did some more tests. I can reproduce the problem with 9.0.030 but not with 9.1.027 (out soon). Wait for that and try again.

[netphilou31]

Thanks to all,

I think that it is a problem with my version of IVF (9.0.025). I will test it with the version 9.1.027 when available. Can this version (9.1.027) run within VisualStudio .NET 2003 or it requires VS .NET 2005 ?

Again Thanks.

[Steven_L_Intel1]

VS.NET 2003 will be fine. The release is now likely to be 9.1.028.

Before installing 9.1, you must uninstall the "Intel Fortran Integration into Microsoft Visual Studio" from 9.0. You can also remove the other 9.0 components but that is optional. (If you don't, both versions will be on your system.)