I have a problem in generating fortran 90 project using modules. It looks like a timing problem between a file creation and it's effective creation on the disk. This problem happens in Windows (XP3 in my case) not in Linux.
I use MinGW tdm last distribution (as you have in C::B 10.05) except than I use gfortran 4.4.0 not 4.4.1 because on some projects I have some problems with this last version.
See this test case in Test_f90_modules.7z.
I have a main program in aa.f. This program uses two modules. Module cc which is in mod_cc.f and module bb which is in mod_bb.f.
Module bb itself uses module cc. So the first thing to do is to set correctly build priorities to force the right order of compilation.
So I set priority 0 to mod_cc.f, priority 25 to mod_bb.f and default priority 50 to aa.f. (Right clic on each .f file in Management window, Properties..., Build, and setting the priority weight to the correct value).
Like that, when mod_cc.f is compiled, it creates a mod_cc.o in /obj and cc.mod directly the main folder.
Same thing for mod_bb.f. But, cc.mod must exist at compile time.
Then when aa.f is compiled, cc.mod and bb.mod must exist at compile time.
On Linux, as I said, no problem. Build process is correct.
On Windows, it's different.
If I build the project (click on main task bar build button), mod_cc.f is compiled but when mod_bb.f is compiled I obtain an error message sayind that cc.mod is not here. But If I look in my folder, I can see it : it has been created. If I again build the project (here cc.mod already exists), mod_bb.f is correctly compiled and bb.mod created, but when compiling aa.f, I obtain an error message saying that bb.mod is not here. Nevertheless, I build again and that time all is OK. So, for this project, I need to click 3 times on the main Build button (or Ctrl+F9).
Now, if I try to build manually the project, starting from a clean folder, no .exe, no .o and no .mod, by :
1) right click on mod_cc.f and click on Build file
2) right click on mod_bb.f and click on build file
3) Click on the main build button.
Like this, everything is OK.
Builds logs in Builds_logs.7z
So, if doing manually the total build works, but the global automatic chaining build does not work. It looks like there is a timing problem. I think, but I am not totally sure of this, that there is a problem with the cache system on Windows. When chaining automatically, mod_cc.f is compiled creating effectively mod_cc.o and cc.mod, but cc.mod may be is still in the cache and not still physically on the disk when mod_bb.f is compiled, so generating the error. Next time, it's OK, because cc.mod is already there, but in fact, it's the previous compiled version which is used. It could be a problem if I modify something in the module between the 2 builds.
An other problem, related with this, is that when you Clean (or Rebuild) the project, the executable and .o files are first deleted, but it's not true for .mod files. You have to delete them manually. I tried to add an rm *.mod in pre-build step, but it is not a solution because .mod files are deleted even if nothing has changed in the modules.
And finally, I think I have quite a similar problem when building CodeBlocks itself on Windows from svn files (never happen on Linux). I have often, but not systematically, an error when I build the workspace (and sometimes rebuild) because some files as sdk.h or sdk_precomp.h (and sometimes others) are declared as missing. But I can see them in my folders. I just need to build again the workspace, and that time, the previous declared missing file is found. May be a similar problem with cache disk on Windows.
So if effectively it's the same problem it's more a CodeBlocks problem on Windows than a gfortran one.
gd_on
[attachment deleted by admin]
