Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29250 Discussions

Compiled module files not deleted when the Solution is Cleaned

acar
Beginner
1,263 Views
I noticed yesterday for the first time that when I did a 'Clean Solution', the compiled module files were not deleted, i.e. they were still present in the /debug directory (I'm configured for DEBUG at present). I hadn't noticed this previously so I wonder if the changes I've made recently have caused this. This is of concern to me since it means that a 'rebuild' might not mean a rebuild in the sense that I understand it, i.e. if these files are found then presumably the compiler will not recompile them. I used to have such issues with CVF when I removed a routine from a solution but didn't delete the compiled version, any calls to that routine were accepted since the compiled routine was still available (erroneously) to the solution. In those days, if I recall correctly, a rebuild didn't pick this up so manual intervention was required to actually clean the solution. I guess the user is anticipating that the cleaning action is robust in that it leads, on rebuild, to a full recompilation and linking and without picking up debris from previous activity?
0 Kudos
7 Replies
Les_Neilson
Valued Contributor II
1,263 Views
Hi,
If you look at Project->Propertiesunder "General" you should see "Extensions to Delete on Clean" one of these should be *.mod (along with *.obj and others)
HTH

Les
0 Kudos
acar
Beginner
1,263 Views
Thanks Les. Actually, looking in more detail, the files are uncompiled module interface files generated by the compiler and with the extension f90. So, as you say, although *.mod is included in the Extensions to Delete on Clean, *.f90 is not. I guess I should add *.f90 to the list but wonder that might other unintended consiquences? ACAR.
0 Kudos
Steven_L_Intel1
Employee
1,263 Views
The __GENMOD.f90 files are there just for your reference - they are not used in the compilation process so they don't need to be cleaned. But I agree that these should be removed on a clean - I will suggest it to the developers.
0 Kudos
Les_Neilson
Valued Contributor II
1,263 Views
Hi
It's probably NOT a good idea to specify .f90 in the clean just in case you have or add any f90 source files of your own to the project. You don't want those deleted :-(
(has happened to me in the past!)

Les
0 Kudos
acar
Beginner
1,263 Views
Yes I agree. I've not added source files here but I don't like the idea of issuing a delete *.f90 even if its (supposedly) restricted to the /debug or /release directories.
0 Kudos
Steven_L_Intel1
Employee
1,263 Views
A future version will delete *__GENMOD.* from the intermediate directory on a clean.
0 Kudos
bmchenry
New Contributor II
1,263 Views
this thread reminded me of a 'cleaning' issue i asked about (and it was2! years ago!)
The thread hassome related issues:
http://software.intel.com/en-us/forums/showthread.php?t=64724

brian
0 Kudos
Reply