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

Build->Clean solution not always so "clean"

bmchenry
New Contributor II
1,416 Views
Note for those doing a "Rebuild All' and/or'Clean Solution'.
After scratching my head for a while wondering 'why am i getting these strange errors' when I used 'rebuild all' after executing a 'clean solution' command, I found that many files are not 'cleaned' out from the Debug and/or Release diectories.
And those remaining files may produce strange errors.
The project had been recomiling fine with interim recompilations and I wanted to cleanup everything and ran into the problem.
I suggest totruly 'clean' your Debug and/or Release directory before a Rebuild all command is executed I would recommend going to the debug and/or Release directories and deleting all files manually before the Rebuild all command.
Apparently when you rename/redefine/etc files while doing interim recompiles, it somehow ignores the old/unused files? and doesn't clean them out so when you try Clean Solution and then rebuild ALL, some of the old files may conflict with the new/clean rebuild.

Just a note. Don't know if this is the expected behavior.
I am using the latest (74, recently updated in last day) 11.0.3454.2003 with .NET 2003
0 Kudos
3 Replies
Jugoslav_Dujic
Valued Contributor II
1,416 Views
Quoting - bmchenry
Note for those doing a "Rebuild All' and/or'Clean Solution'.
Just a note. Don't know if this is the expected behavior.
I am using the latest (74, recently updated in last day) 11.0.3454.2003 with .NET 2003

Yes, this is the expected behavior.

I understand your frustration, but in my opinion it's much better this way, i.e. the IDE should only handle the items it knows about, for a couple of reasons:

* You may reconfigure your solutions so that the intermediate and output files go to a quite diverse family of directories, rather than just "Debug" or "Release" subdirectorise. You can't wipe out everything in sight.
* As a corrolary, user may keep its input or auxiliary files in those Debug or Release directories. You don't want them silently destroyed.
0 Kudos
bmchenry
New Contributor II
1,416 Views
I agree Jugoslav,
Don't want rebel robotics deleting stuff it knows nothing about!
I found the reason for my initial problems eith build 74 which i attributed to the'unclean' directory were really build interface block issues.
That now being solved the need to clean out the directory manually is not longer required.
Thanks!
brian
0 Kudos
Robinson__Donald
Beginner
1,416 Views
There is also the option "Extensions to Delete on Clean" (Project>Properties>General; MS Visual Studio 2005)to add deletion of file patterns that can crop of regularly, such as interfaces.

0 Kudos
Reply