- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A future version will delete *__GENMOD.* from the intermediate directory on a clean.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
The thread hassome related issues:
http://software.intel.com/en-us/forums/showthread.php?t=64724
brian

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page