* need to put *smod files on -I path?
@ 2017-03-10 14:22 Anton Shterenlikht
2017-03-10 18:19 ` Paul Richard Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Anton Shterenlikht @ 2017-03-10 14:22 UTC (permalink / raw)
To: fortran
I have a library with a number of modules and submodules.
There is a "top level" module file that uses all other modules.
When I compile a program which call routines from this library,
it seems I need to add only this "top level" *mod file
to -I include path. It seems access to *smod files is not
required on compiling such program. Have I got this right?
Anton
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: need to put *smod files on -I path?
2017-03-10 14:22 need to put *smod files on -I path? Anton Shterenlikht
@ 2017-03-10 18:19 ` Paul Richard Thomas
2017-03-10 18:22 ` Anton Shterenlikht
0 siblings, 1 reply; 3+ messages in thread
From: Paul Richard Thomas @ 2017-03-10 18:19 UTC (permalink / raw)
To: mexas; +Cc: fortran
Hi Anton,
Module and submodule files share the code for input and output and so
the path is also shared.
To your question, the straight answer is 'yes'.
Regards
Paul
On 10 March 2017 at 14:22, Anton Shterenlikht <mexas@bris.ac.uk> wrote:
> I have a library with a number of modules and submodules.
> There is a "top level" module file that uses all other modules.
> When I compile a program which call routines from this library,
> it seems I need to add only this "top level" *mod file
> to -I include path. It seems access to *smod files is not
> required on compiling such program. Have I got this right?
>
> Anton
--
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: need to put *smod files on -I path?
2017-03-10 18:19 ` Paul Richard Thomas
@ 2017-03-10 18:22 ` Anton Shterenlikht
0 siblings, 0 replies; 3+ messages in thread
From: Anton Shterenlikht @ 2017-03-10 18:22 UTC (permalink / raw)
To: mexas, paul.richard.thomas; +Cc: fortran
From paul.richard.thomas@gmail.com Fri Mar 10 18:20:25 2017
>
>Hi Anton,
>
>Module and submodule files share the code for input and output and so
>the path is also shared.
>
>To your question, the straight answer is 'yes'.
>
>Regards
>
>Paul
Paul, thank you
Anton
>
>On 10 March 2017 at 14:22, Anton Shterenlikht <mexas@bris.ac.uk> wrote:
>> I have a library with a number of modules and submodules.
>> There is a "top level" module file that uses all other modules.
>> When I compile a program which call routines from this library,
>> it seems I need to add only this "top level" *mod file
>> to -I include path. It seems access to *smod files is not
>> required on compiling such program. Have I got this right?
>>
>> Anton
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-10 18:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-10 14:22 need to put *smod files on -I path? Anton Shterenlikht
2017-03-10 18:19 ` Paul Richard Thomas
2017-03-10 18:22 ` Anton Shterenlikht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).