Compilation order (USE assocs)
- From: Antoon <antoon.Koster@xxxxxxxxxxx>
- Date: Mon, 22 Sep 2008 23:57:13 -0700 (PDT)
Hi,
Any idea how to force the compilation order of the F90 files ? My
problem is this ...
All my F90 routines are (one-to-one) embedded in module procedures, in
order to create explicit interfaces for checking the subroutine calls
(very useful F90 feature indeed). For this purpose for each subroutine
call the corresponding USE assocation is added. What you expect from
your IDE that the F90 files are compiled in the right order, what
means that before compiling the module itself first all the modules in
the USE assocations are checked and compiled if needed. Sounds
reasonable.
But for my IDE, Vis. Studio 2005 this is unf not the case. In VS2005-
speak when I do a Rebuild (Clean + Build) all F90 files in that
'project' are compiled in one single sweep, but it looks as if the USE
dependendies in the F90 files are completely ignored. On compiling a
F90 file, now I get compile-time error messages that the files in the
USE assocations can't be found. When I manually compile the missing
modules first, then it does work, so nothing wrong with the software
or settings (module paths) I guess. The full name of my Fortran
compiler is Intel(R) Fortran Compiler 10.1.011 [IA-32].
Any idea to force the correct compilation order here ?
Thanks !
Antoon
in my IDE (Vis. Studio 2005) for
.
- Follow-Ups:
- Re: Compilation order (USE assocs)
- From: Jugoslav Dujic
- Re: Compilation order (USE assocs)
- From: JayBee
- Re: Compilation order (USE assocs)
- Prev by Date: Re: Passing module procedures to external procedures -- type issues
- Next by Date: Re: Compilation order (USE assocs)
- Previous by thread: Scope of implicit none
- Next by thread: Re: Compilation order (USE assocs)
- Index(es):
Relevant Pages
|