I am making some tests with PSXE16.0 using SUBMODULES. My test job exhibits some strange behaviour:
1] On doing a successful build or clean then build if I do F5 to debug it says the exe is out of date and does a full build again. It will then debug.
2] On changing anything, e.g. the main program (there are only 3 source files ) is does a complete rebuild every time.
This type of behaviour I have experienced before when the project has circular dependencies. This project has three files, a module file with interfaces, a sub module file with only contained sub-routines and a simple main program. I did all the usual close VS and restarting, deleting the project and making a new one etc.
On opening the project in VS the first time and doing a build I get (one time only!):
C:\Users\...\fred_subs.f90 : warning: Module 'Debug\subroutine.mod' is created by both 'C:\Users\...\fred_subs.f90' and 'C:\Users\...\fred.f90'. 1>------ Build started: Project: SUBM_TEST2, Configuration: Debug Win32 ------ 1>Compiling with Intel(R) Visual Fortran Compiler 16.0 [IA-32]... 1>fred.f90 1>fred_subs.f90 1>SUBM_TEST.f90 1>Linking... 1>Embedding manifest... 1> 1>Build log written to "file://C:\Users\.....\Debug\BuildLog.htm" 1>SUBM_TEST2 - 0 error(s), 0 warning(s) ========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
Note the first line! I think this is the route cause but it makes no sense are the VS integration picking up “module subroutine” which is part of the interfaces for each subroutine and also the definition and believing there is a MODULE called SUBROUTINE? “Subroutine.mod” is not created by the way.
Does anyone know of any issues like this?