Re: Structure of large link libraries in f95
- From: robert.corbett@xxxxxxx
- Date: 30 Mar 2006 02:36:13 -0800
simon@xxxxxxxxxxxxxx wrote:
Perhaps the solution to this would be for compilers to be able to read
.mod files in archives.
You can put all the object code and corresponding .mod files into a
single '.a' file on unix now, the problem is that (as far as I know)
there aren't any compilers that will read the .mod files directly from
the archive - there would have to be a separate extraction step.
Sun f90/f95 reads .mod files from archives. The archive must be
named in the option argument following the option -M.
That does not solve the OP's problem. Currently, an entire
module must appear in a single source file. When that
source file is compiled, a single object file is produced.
That entire object file will be extracted if even a single
routine in the module is referenced. If a compiler
implemented compile-to-archive, it would produce
separate object files for each routine in the module, all
of which would appear in the archive.
Bob Corbett
.
- References:
- Structure of large link libraries in f95
- From: Charles Russell
- Re: Structure of large link libraries in f95
- From: robert . corbett
- Re: Structure of large link libraries in f95
- From: Charles Russell
- Re: Structure of large link libraries in f95
- From: robert . corbett
- Re: Structure of large link libraries in f95
- From: simon
- Structure of large link libraries in f95
- Prev by Date: Re: Structure of large link libraries in f95
- Next by Date: Re: status of quadruple precision arithmetic in g95 and gfortran?
- Previous by thread: Re: Structure of large link libraries in f95
- Next by thread: Re: Structure of large link libraries in f95
- Index(es):
Relevant Pages
|
|
