To reflect the official release of the NetCDF library I've changed
Rules.make to use nf-config instead of nc-config. If you don't intend to
update to the latest NetCDF version the compilation of GETM will fail
and you'll manually have to change nf-config back to nc-config (2
places).
http://www.unidata.ucar.edu/netcdf/release-notes-4.2.html
http://www.unidata.ucar.edu/downloads/netcdf/
Karsten
thanks for this information. We had also problems with netcdf4 and my
Postdoc (Santiago Moreira) identified this issue too and changed it in
our local copy.
We are currently working to connect our SALMO lake model to FABM, more
will hopefully come at the Leipzig workshop.
Many many thanks for maintaining GOTM!!
Thomas Petzoldt
--
Dr. Thomas Petzoldt
Technische Universitaet Dresden
Faculty of Forest, Geo and Hydro Sciences
Institute of Hydrobiology
01062 Dresden, Germany
Tel.: +49 (351) 463-34954
Fax: +49 (351) 463-37108
E-Mail: thomas....@tu-dresden.de
http://tu-dresden.de/Members/thomas.petzoldt
> To reflect the official release of the NetCDF library I've changed
> Rules.make to use nf-config instead of nc-config.
Thanks for keeping GETM updated.
> If you don't intend to
> update to the latest NetCDF version the compilation of GETM will fail
> and you'll manually have to change nf-config back to nc-config (2
> places).
>
The other possibility is:
do *not* export NETCDF_VERSION=NETCDF4
but export NETCDFINC, NETCDFLIBDIR and if needed NETCDFLIBNAME. The
latter might be "-lnetcdf -lnetcdff" to also include -lnetcdff.
BTW:
Maybe we should change
ifeq(NETCDF_VERSION,NETCDF4)
<up2date settings>
else
<use of NETCDFINC etc.>
endif
to
ifdef NETCDF_NONDEFAULT
<use of NETCDFINC etc.>
else
<up2date settings>
endif
(or something similar)?
Knut