On Mar 7, 2013, at 12:44 PM, John Peterson <jwpeter...@gmail.com> wrote:
> Am I actually getting "netCDF3" functionality (although built with netCDF
> 4.2.1.1 sources) in this case due to my lack of HDF5?
That's right. The source package included the latest version 3 API in
contrib/netcdf/v4/libsrc
and version 4 API in
contrib/netcdf/v4/libsrc4
The version 4 API requires HDF5, and the latest exodus requires version 4 for
full feature support.
When HDF5 is absent we fall back to building the libsrc version 3 only API, but
from the new 'v4' source tree (sorry for the confusion!!) and then tell Exodus
to turn off the new features, c.f. exodus.m4:
# no HDF5 &/or no NETCDF4
EXODUS_NOT_NETCDF4_FLAG=""
if (test "x$enablehdf5" = "xno" -o "x$netcdfversion" = "x3"); then
EXODUS_NOT_NETCDF4_FLAG="-DNOT_NETCDF4"
AC_MSG_RESULT([defining -DNOT_NETCDF4 for our Exodus build])
fi
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
