Re: [netcdfgroup] does anyone mind if the fortran 77 library always gets its own file, instead of being combined with the C library?

• To: netcdfgroup@xxxxxxxxxxxxxxxx
• Subject: Re: [netcdfgroup] does anyone mind if the fortran 77 library always gets its own file, instead of being combined with the C library?
• From: Magnus Hagdorn <Magnus.Hagdorn@xxxxxxxx>
• Date: Tue, 29 Mar 2011 09:28:18 +0100

Ed Hartnett wrote:

Howdy netCDFians!

In the old days the netCDF F77 library was built into the netCDF C
library. (This seemed natural, because it was really just a bunch of C
functions anyway.) Fortran programs using the F77 API, and C programs
linked with -lnetcdf.

This idea does not work with shared libraries, so when shared libraries
are built (now the default) a separate F77 library is built. Now C
library users still link with -lnetcdf, but F77 library users must use
-lnetcdff -lnetcdf. (Note the extra "f" at the end of the F77 library
name.)

Maintaining the ability to combine the C and F77 library is expensive in
terms of programmer time. Will anyone object if I remove this option?

Users will see no impact on their code. They will have to add
"-lnetcdff" to their Makefiles for F77 programs. (This is already true
for shared library builds.)

Any comment or feedback welcome...

Hi Ed,

Cheers
magnus

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

• Follow-Ups:
  • Re: [netcdfgroup] does anyone mind if the fortran 77 library always gets its own file, instead of being combined with the C library?
    • From: Ed Hartnett

• References:
  • [netcdfgroup] does anyone mind if the fortran 77 library always gets its own file, instead of being combined with the C library?
    • From: Ed Hartnett