vc90.pdb location

[strohhaecker]

The location where vc90.pdb is created, seems to be fixed when using the 2011.0.104 release of the visual fortran compiler (visual studio 2008).

To reproduce this, create a new console project ("Main Program Code" for a quick setup), compiling this with default settings (debug) will place vc90.pdb in the directory where the project file (vfproj) resides.

Now changing in the project settings anything related to vc90.pdb does not work, for example renaming the Properties->Fortran->Output Files->"Program Database File Name" entry to test.pdb is completely ignored, so is changing its path ($(IntDir) or anything that modifies the immediate directory path).

This is a problem when building multi-project solutions on multicore systems (when visual studio is enabled to compile several projects at once, which is the default) because depending on the location of the project file they may use the same vc90.pdb file, causing build errors.

I haven't found anything mentioned about this in the changelogs or release notes, is this an intentional change?

Thank you.

[strohhaecker]

This is still existent in the exact same flavor in the 2011.1.127 update.

It effectively renders multi-project solutions (where the project files are in the same directory) unusable, blocking the upgrade to the 12.0 releases since it was working correctly before.

[Steven_L_Intel1]

Would you please attach the .vfproj file and buildlog.htm from your build? I'll take a look.

[strohhaecker]

As stated in the first posting, this issue can be reproduced by creating a new project and only changing one of the parameters that has influence on the location or naming of vc90.pdb.

Anyways, I've attached project files and buildlogs of working (v11 Intel compiler) and nonworking (v12) setups, one part using unmodified project settings and one has the intermediate path changed which should have an effect on the placement of vc90.pdb.

Thank you.

[strohhaecker]

This issue is present in exactly the same manner in the 2011.2.154 release. Thus it still blocks parallel building solutions that contain projects in the same directory.

[Steven_L_Intel1 · Accepted solution]

This was escalated to development as issue DPD200168013.

[strohhaecker]

Thank you. Just let me know if there are further questions.

[Steven_L_Intel1]

I was able to reproduce it easily enough. It seems that the /Fd option is simply ignored.

[strohhaecker]

This is working correctly in Update4 (2011) now, thank you.