[netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

[Pedro_Vicente1]

Hi Ward

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

The way I make Visual Studio be aware of libraries/headers is by means of Windows environment variables
for example

$HEADER_HDF5
Is defined for me as
T:\hdf5\hdf5\src
and
$LIB_HDF5
as
T:\hdf5\hdf5\proj\hdf5\Debug\hdf5d.lib

1) Is it possible to do this with the supplied CMake projects, point to environment variables instead of an install path ?

My HDF5 header/libs are always "development" locations, that I use for debugging, not pre built binary distributions.

2) I did try a pre built binary distribution for this case, the latest HDF5 built with CMake from here, this one

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

Windows (64-bit)
  Compilers:
    CMake VS 2010 C, C++, IVF 12

3) Following the instructions (this is for RC3) in "COMPILE_CMake.txt"

"
The CMake build system discourages 'in-source' builds. Instead, a
build directory is created and used to contain the output of the build
process. From the command line, this may be achieved as follows:

developer@dummy-machine:/netcdf$ mkdir build_dir
developer@dummy-machine:/netcdf$ cd build_dir
developer@dummy-machine:/netcdf/build_dir$ cmake ..
"

I did just that with these arguments , -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10
is the location of the pre-built binaries I downloaded from the HDF site, that contains some CMake information

W:\netcdf-4.3.0-rc3\build_dir>cmake . -DCMAKE_INSTALL_PREFIX=W:\netcdf_install -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10

I get these messages

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
  include could not find load file:

    HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
  CMakeLists.txt:75 (INCLUDE)

-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib, T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib, T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version "1.2.7")
-- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
CMake Error at CMakeLists.txt:417 (MESSAGE):
  DAP Support specified, CURL libraries are not found.

-- Configuring incomplete, errors occurred!

Thanks

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header and library files. The netCDF build will use the zlib library included with the hdf5 binary distribution. If you do not have this, or if it is installed elsewhere, you can specify multiple search locations thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website, http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new location. Please note that these pre-built libraries (both 32 & 64-bit) are built and tested on 64-bit Windows 7 using Visual Studio 10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release candidate, or the final 4.3.0 release (depending on the number and severity of bugs reported). As always, we welcome any bug reports and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

[Ward_Fisher]

Good morning Pedro,

Hi Ward

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

The way I make Visual Studio be aware of libraries/headers is by means of Windows environment variables
for example

$HEADER_HDF5
Is defined for me as
T:\hdf5\hdf5\src
and
$LIB_HDF5
as
T:\hdf5\hdf5\proj\hdf5\Debug\hdf5d.lib

1) Is it possible to do this with the supplied CMake projects, point to environment variables instead of an install path ?

My HDF5 header/libs are always "development" locations, that I use for debugging, not pre built binary distributions.

I will take a look to see how CMake handles Windows environmental variables; an impromptu test shows that (in the MSYS shell, at least) CMake does not automatically pick up environmental variables. I was able to specify the libraries/header locations manually on the command line, however:

$ cmake .. -DZLIB_LIBRARY=/c/share/x64/shared/lib/zlib.lib \
    -DCURL_LIBRARY=/c/share/x64/shared/lib/libcurl_imp.lib \
    -DHDF5_HL_LIB=/c/share/x64/shared/lib/hdf5_hldll.lib \
    -DHDF5_LIB=/c/share/x64/shared/lib/hdf5dll.lib \
    -DHDF5_INCLUDE_DIR=/c/share/x64/shared/include/ \
    -DCURL_INCLUDE_DIR=/c/share/x64/shared/include/ \
    -G"Visual Studio 10 Win64"

The same arguments should work from a default Windows command.exe shell, using standard Windows path syntax.

2) I did try a pre built binary distribution for this case, the latest HDF5 built with CMake from here, this one

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

Windows (64-bit)
Compilers:
   CMake VS 2010 C, C++, IVF 12

<.....>

Since you are using the 64-bit libraries, I think you need to specify the 64-bit Visual Studio generator via the '-G' flag, e.g. -G"Visual Studio 10 Win64". When I specify this flag, the fist few lines appear as follows:

-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10 Win64
-- Check for working C compiler using: Visual Studio 10 Win64 -- works
-- Detecting C compiler ABI info

I suspect it is not finding the hdf5 and curl libraries because it is looking for 32-bit versions of the libraries, not 64. This is something that should be clarified in the documentation; thanks for pointing this out! I'll also add a section on manually specifying dependencies instead of letting CMake determine them automatically.

Thanks, have a great day,

-Ward

···

On 3/18/13 4:16 AM, Pedro Vicente wrote:

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:

   HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib, T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib, T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version "1.2.7")
-- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
CMake Error at CMakeLists.txt:417 (MESSAGE):
DAP Support specified, CURL libraries are not found.

-- Configuring incomplete, errors occurred!

Thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header and library files. The netCDF build will use the zlib library included with the hdf5 binary distribution. If you do not have this, or if it is installed elsewhere, you can specify multiple search locations thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website, http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new location. Please note that these pre-built libraries (both 32 & 64-bit) are built and tested on 64-bit Windows 7 using Visual Studio 10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release candidate, or the final 4.3.0 release (depending on the number and severity of bugs reported). As always, we welcome any bug reports and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

[pedro.vicente]

Hi Ward

Here are some suggestions that hopefully will help you to build a more robust CMake build

I am sending this as well to the HDF list, since there are often CMake posts on it

I will take a look to see how CMake handles Windows environmental variables;

The environmental variables issue is not a show stopper, I can use just a regular path

an impromptu test shows that (in the MSYS shell, at least)

A suggestion is to make the Windows CMake build on the Windows shell.
Many Unix tools that may be assumed existent are just not existent on the Windows shell.

I think this is the cause of these errors:

Since I don't have curl installed, I tried

cmake .. -DCMAKE_INSTALL_PREFIX=W:\netcdf_install -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10 -D"ENABLE_DAP=OFF"

Output is

CMake Error: Parse error in cache file W:/netcdf-4.3.0-rc3_2/build_dir/CMakeCache.txt. Offending entry: for command: UNAME-NOTFOUND -s-CreateProcessError: The system cannot find th
e file specified.
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

Both of these are Unix .

Why the need for a Pkg-Config dependency on a CMake builld ?
If not needed, these should be taken off

Then

HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
  CMakeLists.txt:75 (INCLUDE)

How can I specify "HDF5_ROOT_DIR" ?

Shouldn't the -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10 be the same ?

Then, finally

- CMake Summary:

-- Build Type: DEBUG
-- Building Shared Libraries: ON
-- Building netCDF-4: ON
-- Building DAP Support: OFF
-- Building Utilities: ON
-- CMake Prefix Path: T:\hdf5_install_1.8.10
-- Using pnetcdf: OFF,
-- Using Parallel IO: OFF
-- Linking against: T:/hdf5_install_1.8.10/lib/hdf5dll.lib;T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib;T:/hdf5_install_1.8.10/lib/zlib.lib

-- Configuring incomplete, errors occurred!

I did try to install a Pkg-Config port for Win32, I'll send the results in a separate email

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: "HDF Users Discussion List" <hdf-forum@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>
Sent: Monday, March 18, 2013 8:47 AM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Good morning Pedro,

On 3/18/13 4:16 AM, Pedro Vicente wrote:

Hi Ward

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

The way I make Visual Studio be aware of libraries/headers is by means of Windows environment variables
for example

$HEADER_HDF5
Is defined for me as
T:\hdf5\hdf5\src
and
$LIB_HDF5
as
T:\hdf5\hdf5\proj\hdf5\Debug\hdf5d.lib

1) Is it possible to do this with the supplied CMake projects, point to environment variables instead of an install path ?

My HDF5 header/libs are always "development" locations, that I use for debugging, not pre built binary distributions.

I will take a look to see how CMake handles Windows environmental variables; an impromptu test shows that (in the MSYS shell, at least) CMake does not automatically pick up environmental variables. I was able to specify the libraries/header locations manually on the command line, however:

$ cmake .. -DZLIB_LIBRARY=/c/share/x64/shared/lib/zlib.lib \
   -DCURL_LIBRARY=/c/share/x64/shared/lib/libcurl_imp.lib \
   -DHDF5_HL_LIB=/c/share/x64/shared/lib/hdf5_hldll.lib \
   -DHDF5_LIB=/c/share/x64/shared/lib/hdf5dll.lib \
   -DHDF5_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -DCURL_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -G"Visual Studio 10 Win64"

The same arguments should work from a default Windows command.exe shell, using standard Windows path syntax.

2) I did try a pre built binary distribution for this case, the latest HDF5 built with CMake from here, this one

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

Windows (64-bit)
Compilers:
   CMake VS 2010 C, C++, IVF 12

<.....>

Since you are using the 64-bit libraries, I think you need to specify the 64-bit Visual Studio generator via the '-G' flag, e.g. -G"Visual Studio 10 Win64". When I specify this flag, the fist few lines appear as follows:

-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10 Win64
-- Check for working C compiler using: Visual Studio 10 Win64 -- works
-- Detecting C compiler ABI info

I suspect it is not finding the hdf5 and curl libraries because it is looking for 32-bit versions of the libraries, not 64. This is something that should be clarified in the documentation; thanks for pointing this out! I'll also add a section on manually specifying dependencies instead of letting CMake determine them automatically.

Thanks, have a great day,

-Ward

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:

   HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib, T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib, T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version "1.2.7")
-- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
CMake Error at CMakeLists.txt:417 (MESSAGE):
DAP Support specified, CURL libraries are not found.

-- Configuring incomplete, errors occurred!

Thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header and library files. The netCDF build will use the zlib library included with the hdf5 binary distribution. If you do not have this, or if it is installed elsewhere, you can specify multiple search locations thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website, http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new location. Please note that these pre-built libraries (both 32 & 64-bit) are built and tested on 64-bit Windows 7 using Visual Studio 10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release candidate, or the final 4.3.0 release (depending on the number and severity of bugs reported). As always, we welcome any bug reports and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

[Pedro_Vicente1]

I noticed that this file FindHDF5.cmake

CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:
HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

is the same as the one on the HDF5 supplied binary , that I got from here

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

This is line 83 of FindHDF5.cmake:83

actually line 83 of the netCDF version, it is 85 on the HDF5 version

INCLUDE (${HDF5_ROOT_DIR}/hdf5-config.cmake)

However , this message

CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:

just means that the file cannot be found

Can someone from the HDF-Group provide some guidance on these errors?

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Pedro Vicente" <pedro.vicente@space-research.org>
To: "HDF Users Discussion List" <hdf-forum@hdfgroup.org>
Cc: "HDF Users Discussion List" <hdf-forum@hdfgroup.org>;
<netcdfgroup@unidata.ucar.edu>
Sent: Monday, March 18, 2013 1:36 PM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release
Candidateavailable --- CMake build in Windows

Hi Ward

Here are some suggestions that hopefully will help you to build a more
robust CMake build

I am sending this as well to the HDF list, since there are often CMake
posts on it

I will take a look to see how CMake handles Windows environmental
variables;

The environmental variables issue is not a show stopper, I can use just a
regular path

an impromptu test shows that (in the MSYS shell, at least)

A suggestion is to make the Windows CMake build on the Windows shell.
Many Unix tools that may be assumed existent are just not existent on the
Windows shell.

I think this is the cause of these errors:

Since I don't have curl installed, I tried

cmake
.. -DCMAKE_INSTALL_PREFIX=W:\netcdf_install -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10
-D"ENABLE_DAP=OFF"

Output is

CMake Error: Parse error in cache file
W:/netcdf-4.3.0-rc3_2/build_dir/CMakeCache.txt. Offending entry: for
command: UNAME-NOTFOUND -s-CreateProcessError: The system cannot find th
e file specified.
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

Both of these are Unix .

Why the need for a Pkg-Config dependency on a CMake builld ?
If not needed, these should be taken off

Then

HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

How can I specify "HDF5_ROOT_DIR" ?

Shouldn't the -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10 be the same ?

Then, finally

- CMake Summary:

-- Build Type: DEBUG
-- Building Shared Libraries: ON
-- Building netCDF-4: ON
-- Building DAP Support: OFF
-- Building Utilities: ON
-- CMake Prefix Path: T:\hdf5_install_1.8.10
-- Using pnetcdf: OFF,
-- Using Parallel IO: OFF
-- Linking against:
T:/hdf5_install_1.8.10/lib/hdf5dll.lib;T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib;T:/hdf5_install_1.8.10/lib/zlib.lib

-- Configuring incomplete, errors occurred!

I did try to install a Pkg-Config port for Win32, I'll send the results
in a separate email

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: "HDF Users Discussion List" <hdf-forum@hdfgroup.org>;
<netcdfgroup@unidata.ucar.edu>
Sent: Monday, March 18, 2013 8:47 AM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidate
available --- CMake build in Windows

Good morning Pedro,

On 3/18/13 4:16 AM, Pedro Vicente wrote:

Hi Ward

If your hdf5 libraries are installed in W:\hdf5_install, for example,
you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

The way I make Visual Studio be aware of libraries/headers is by means
of Windows environment variables
for example

$HEADER_HDF5
Is defined for me as
T:\hdf5\hdf5\src
and
$LIB_HDF5
as
T:\hdf5\hdf5\proj\hdf5\Debug\hdf5d.lib

1) Is it possible to do this with the supplied CMake projects, point to
environment variables instead of an install path ?

My HDF5 header/libs are always "development" locations, that I use for
debugging, not pre built binary distributions.

I will take a look to see how CMake handles Windows environmental
variables; an impromptu test shows that (in the MSYS shell, at least)
CMake does not automatically pick up environmental variables. I was able
to specify the libraries/header locations manually on the command line,
however:

$ cmake .. -DZLIB_LIBRARY=/c/share/x64/shared/lib/zlib.lib \
   -DCURL_LIBRARY=/c/share/x64/shared/lib/libcurl_imp.lib \
   -DHDF5_HL_LIB=/c/share/x64/shared/lib/hdf5_hldll.lib \
   -DHDF5_LIB=/c/share/x64/shared/lib/hdf5dll.lib \
   -DHDF5_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -DCURL_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -G"Visual Studio 10 Win64"

The same arguments should work from a default Windows command.exe shell,
using standard Windows path syntax.

2) I did try a pre built binary distribution for this case, the latest
HDF5 built with CMake from here, this one

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

Windows (64-bit)
Compilers:
   CMake VS 2010 C, C++, IVF 12

<.....>

Since you are using the 64-bit libraries, I think you need to specify the
64-bit Visual Studio generator via the '-G' flag, e.g. -G"Visual Studio
10 Win64". When I specify this flag, the fist few lines appear as
follows:

-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10 Win64
-- Check for working C compiler using: Visual Studio 10 Win64 -- works
-- Detecting C compiler ABI info

I suspect it is not finding the hdf5 and curl libraries because it is
looking for 32-bit versions of the libraries, not 64. This is something
that should be clarified in the documentation; thanks for pointing this
out! I'll also add a section on manually specifying dependencies instead
of letting CMake determine them automatically.

Thanks, have a great day,

-Ward

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:

   HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib,
T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib,
T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version
"1.2.7")
-- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
CMake Error at CMakeLists.txt:417 (MESSAGE):
DAP Support specified, CURL libraries are not found.

-- Configuring incomplete, errors occurred!

Thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher"
<wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example,
you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header
and library files. The netCDF build will use the zlib library included
with the hdf5 binary distribution. If you do not have this, or if it
is installed elsewhere, you can specify multiple search locations
thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib
locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher"
<wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C
libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website,
http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this
new location. Please note that these pre-built libraries (both 32 &
64-bit) are built and tested on 64-bit Windows 7 using Visual Studio
10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release
candidate, or the final 4.3.0 release (depending on the number and
severity of bugs reported). As always, we welcome any bug reports
and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

[Pedro_Vicente1]

Thanks, Ward

If not, you can set -DHDF5_ROOT_DIR to the folder containing this file.

yes, the fatal error was the missing HDF5_ROOT_DIR, that I set up with

cmake .. -D"CMAKE_INSTALL_PREFIX=W:\netcdf_install" -D"ENABLE_DAP=OFF" -D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5" -D"CMAKE_PREFIX_PATH=T:\
hdf5_install_1.8.10"

Output is

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib, T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib, T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version "1.2.7")
-- Looking for math.h

etc

but still an error of a missing file:

-- CMake Summary:

-- Build Type: DEBUG
-- Building Shared Libraries: ON
-- Building netCDF-4: ON
-- Building DAP Support: OFF
-- Building Utilities: ON
-- CMake Prefix Path: T:\hdf5_install_1.8.10
-- Using pnetcdf: OFF,
-- Using Parallel IO: OFF
-- Linking against: T:/hdf5_install_1.8.10/lib/hdf5dll.lib;T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib;T:/hdf5_install_1.8.10/lib/zlib.lib

-- Configuring done
CMake Error at ncgen/CMakeLists.txt:11 (ADD_EXECUTABLE):
  Cannot find source file:

    XGetopt.c

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Monday, March 18, 2013 4:17 PM
Subject: Re: [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidate available --- CMake build in Windows

Good afternoon Pedro,
On 3/18/13 2:36 PM, Pedro Vicente wrote:

Hi Ward

Here are some suggestions that hopefully will help you to build a more robust CMake build

I am sending this as well to the HDF list, since there are often CMake posts on it

I will take a look to see how CMake handles Windows environmental variables;

The environmental variables issue is not a show stopper, I can use just a regular path

an impromptu test shows that (in the MSYS shell, at least)

A suggestion is to make the Windows CMake build on the Windows shell.
Many Unix tools that may be assumed existent are just not existent on the Windows shell.

I think this is the cause of these errors:

Since I don't have curl installed, I tried

cmake .. -DCMAKE_INSTALL_PREFIX=W:\netcdf_install -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10 -D"ENABLE_DAP=OFF"

Output is

CMake Error: Parse error in cache file W:/netcdf-4.3.0-rc3_2/build_dir/CMakeCache.txt. Offending entry: for command: UNAME-NOTFOUND -s-CreateProcessError: The system cannot find th
e file specified.

I have not encountered the "Parse Error in cache file" error before, but the fix I find suggested in the CMake documentation is to delete the 'CMakeCache.txt' file and re-run CMake from scratch.

-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

Both of these are Unix .

Why the need for a Pkg-Config dependency on a CMake builld ?

Pkg-Config is available for Windows as well; it was initially carried over as part of the conversion from autotools based builds. The failure to find pkg-config.exe on Windows is not a fatal error; the build should continue. I believe the original idea was to have the cmake-based build use pkg-config (when available) to generate the appropriate files to make netcdf more visible to other projects via pkg-config. This is likely unnecessary; I will evaluate if we still need it, and what it would take to complete that functionality.

If not needed, these should be taken off

Then

HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

How can I specify "HDF5_ROOT_DIR" ?

Shouldn't the -DCMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10 be the same ?

On my system, HDF5_ROOT_DIR is set to C:\share\w32\shared\share\cmake\hdf5. The hdf5-related .cmake files are contained within this directory. These files were installed by the HDF5 install executable. Is hdf5-config.cmake present in your T:\hdf5_install_1.8.10 folder? If not, you can set -DHDF5_ROOT_DIR to the folder containing this file. If it is, I'm not certain why it would not have been found by cmake, but I will poke around and see if I can recreate the error.

Then, finally

- CMake Summary:

-- Build Type: DEBUG
-- Building Shared Libraries: ON
-- Building netCDF-4: ON
-- Building DAP Support: OFF
-- Building Utilities: ON
-- CMake Prefix Path: T:\hdf5_install_1.8.10
-- Using pnetcdf: OFF,
-- Using Parallel IO: OFF
-- Linking against: T:/hdf5_install_1.8.10/lib/hdf5dll.lib;T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib;T:/hdf5_install_1.8.10/lib/zlib.lib

-- Configuring incomplete, errors occurred!

I did try to install a Pkg-Config port for Win32, I'll send the results in a separate email

The presence or absence of pkg-config shouldn't be a fatal error; you might try deleting your CMakeCache.txt file and try the process again. Actually, the fatal error is refering to the failure to find the hdf5-config.cmake file, not the lack of pkg-config, so never mind about that.

Thanks, have a great evening!

-Ward

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: "HDF Users Discussion List" <hdf-forum@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>
Sent: Monday, March 18, 2013 8:47 AM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Good morning Pedro,

On 3/18/13 4:16 AM, Pedro Vicente wrote:

Hi Ward

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

The way I make Visual Studio be aware of libraries/headers is by means of Windows environment variables
for example

$HEADER_HDF5
Is defined for me as
T:\hdf5\hdf5\src
and
$LIB_HDF5
as
T:\hdf5\hdf5\proj\hdf5\Debug\hdf5d.lib

1) Is it possible to do this with the supplied CMake projects, point to environment variables instead of an install path ?

My HDF5 header/libs are always "development" locations, that I use for debugging, not pre built binary distributions.

I will take a look to see how CMake handles Windows environmental variables; an impromptu test shows that (in the MSYS shell, at least) CMake does not automatically pick up environmental variables. I was able to specify the libraries/header locations manually on the command line, however:

$ cmake .. -DZLIB_LIBRARY=/c/share/x64/shared/lib/zlib.lib \
   -DCURL_LIBRARY=/c/share/x64/shared/lib/libcurl_imp.lib \
   -DHDF5_HL_LIB=/c/share/x64/shared/lib/hdf5_hldll.lib \
   -DHDF5_LIB=/c/share/x64/shared/lib/hdf5dll.lib \
   -DHDF5_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -DCURL_INCLUDE_DIR=/c/share/x64/shared/include/ \
   -G"Visual Studio 10 Win64"

The same arguments should work from a default Windows command.exe shell, using standard Windows path syntax.

2) I did try a pre built binary distribution for this case, the latest HDF5 built with CMake from here, this one

http://www.hdfgroup.org/HDF5/release/obtain5.html#bin

Windows (64-bit)
Compilers:
   CMake VS 2010 C, C++, IVF 12

<.....>

Since you are using the 64-bit libraries, I think you need to specify the 64-bit Visual Studio generator via the '-G' flag, e.g. -G"Visual Studio 10 Win64". When I specify this flag, the fist few lines appear as follows:

-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10 Win64
-- Check for working C compiler using: Visual Studio 10 Win64 -- works
-- Detecting C compiler ABI info

I suspect it is not finding the hdf5 and curl libraries because it is looking for 32-bit versions of the libraries, not 64. This is something that should be clarified in the documentation; thanks for pointing this out! I'll also add a section on manually specifying dependencies instead of letting CMake determine them automatically.

Thanks, have a great day,

-Ward

-- Building for: Visual Studio 10
-- The C compiler identification is MSVC 16.0.40219.1
-- Check for working C compiler using: Visual Studio 10
-- Check for working C compiler using: Visual Studio 10 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at cmake/modules/windows/FindHDF5.cmake:83 (INCLUDE):
include could not find load file:

   HDF5_ROOT_DIR-NOTFOUND/hdf5-config.cmake
Call Stack (most recent call first):
CMakeLists.txt:75 (INCLUDE)

-- T:/hdf5_install_1.8.10/lib/hdf5dll.lib, T:/hdf5_install_1.8.10/lib/hdf5_hldll.lib, T:/hdf5_install_1.8.10/include
-- Found ZLIB: T:/hdf5_install_1.8.10/lib/zlib.lib (found version "1.2.7")
-- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR)
CMake Error at CMakeLists.txt:417 (MESSAGE):
DAP Support specified, CURL libraries are not found.

-- Configuring incomplete, errors occurred!

Thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header and library files. The netCDF build will use the zlib library included with the hdf5 binary distribution. If you do not have this, or if it is installed elsewhere, you can specify multiple search locations thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website, http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new location. Please note that these pre-built libraries (both 32 & 64-bit) are built and tested on 64-bit Windows 7 using Visual Studio 10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release candidate, or the final 4.3.0 release (depending on the number and severity of bugs reported). As always, we welcome any bug reports and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

[Pedro_Vicente1]

Hi Ward

I was able to built netCDF using the latest HDF5 binaries with Cmake info that I got from here

http://www.hdfgroup.org/HDF5/release/obtain5.html

using these 2 options

-D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10"
-D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5"

my next step is

1) Build using the same source distribution of HDF5, instead of the pre-compiled binaries
2) Build using a HDF5 version without Cmake information

Is it possible to to this?
I noticed that the source HDF5 files do not include this folder, that is available only in the binaries T:\hdf5_install_1.8.10\cmake\hdf5

Ideally what woulde be needed is a way for the Cmake system to find the HDF5 header files location and the name of the library hdf5.lib... that's all Visual Studio needs...
something like

-D"MY_HDF5_HEADER_FOLDER=<etc>
-D"MY_HDF5_LIBRARY_FILE=<etc>

thanks

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

Hi Pedro,

If your hdf5 libraries are installed in W:\hdf5_install, for example, you would specify the following argument:

-DCMAKE_PREFIX_PATH=W:\hdf5_install

CMake would then check this location first when looking for any header and library files. The netCDF build will use the zlib library included with the hdf5 binary distribution. If you do not have this, or if it is installed elsewhere, you can specify multiple search locations thusly:

-DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".

I hope this helps!

-Ward

On 3/14/13 7:04 PM, Pedro Vicente wrote:

Hi Ward

I tried to build in Windows with CMake, using

cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install

I get these messages

-- Building for: Visual Studio 10
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
-- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
CMake Error at CMakeLists.txt:403 (MESSAGE):
HDF5 Support specified, cannot find ZLib.

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
HDF5_INCLUDE_DIR
  used as include directory in directory W:/netcdf_svn

-- Configuring incomplete, errors occurred!

How can I make the supplied CMake projects to detect my HDF5 and zlib locations?

Thanks

Pedro

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: <netcdfgroup@unidata.ucar.edu>
Sent: Tuesday, February 26, 2013 5:04 PM
Subject: [netcdfgroup] netCDF 4.3 Release Candidate available

Good afternoon all,

We are officially announcing the availability of the netCDF-C libraries version 4.3.0, release candidate 2.

Documentation and source downloads are available at:

http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp

Pre-built Windows binaries are available at:

http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html

The previous Windows-specific website, http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new location. Please note that these pre-built libraries (both 32 & 64-bit) are built and tested on 64-bit Windows 7 using Visual Studio 10.

Highlights of the 4.3 release include:

o Many bug fixes.
o Improved DAP support.
o Improved parallel-netcdf support.
o Improved Windows support.
o Integration of CMake, allow for Visual-Studio based builds.

This release candidate is the precursor to either a new release candidate, or the final 4.3.0 release (depending on the number and severity of bugs reported). As always, we welcome any bug reports and/or feedback!

Have a great evening,

-Ward
Ward Fisher
wfisher@unidata.ucar.edu

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

[byrn]

CMake provides two ways to find libraries:
1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})
    where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to
hdf5library}/cmake/hdf5"

2. Non-cmake built HDF5 - use FIND_PACKAGE (HDF5)
    where ENV{HDF5_ROOT}="{path to hdf5library}"

Allen

···

On Friday, March 29, 2013 10:32:04 AM Pedro Vicente wrote:

Hi Ward

I was able to built netCDF using the latest HDF5 binaries with Cmake info
that I got from here

http://www.hdfgroup.org/HDF5/release/obtain5.html

using these 2 options

-D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10"
-D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5"

my next step is

1) Build using the same source distribution of HDF5, instead of the
pre-compiled binaries
2) Build using a HDF5 version without Cmake information

Is it possible to to this?
I noticed that the source HDF5 files do not include this folder, that is
available only in the binaries T:\hdf5_install_1.8.10\cmake\hdf5

Ideally what woulde be needed is a way for the Cmake system to find the HDF5
header files location and the name of the library hdf5.lib... that's all
Visual Studio needs...
something like

-D"MY_HDF5_HEADER_FOLDER=<etc>
-D"MY_HDF5_LIBRARY_FILE=<etc>

thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message -----
From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake
build in Windows

> Hi Pedro,
>
> If your hdf5 libraries are installed in W:\hdf5_install, for example, you
> would specify the following argument:
>
> -DCMAKE_PREFIX_PATH=W:\hdf5_install
>
> CMake would then check this location first when looking for any header and
> library files. The netCDF build will use the zlib library included with
> the hdf5 binary distribution. If you do not have this, or if it is
> installed elsewhere, you can specify multiple search locations thusly:
>
> -DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".
>
> I hope this helps!
>
> -Ward
>
> On 3/14/13 7:04 PM, Pedro Vicente wrote:
>> Hi Ward
>>
>> I tried to build in Windows with CMake, using
>>
>>
>> cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install
>>
>> I get these messages
>>
>>
>> -- Building for: Visual Studio 10
>> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
>> -- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
>> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
>>
>> CMake Error at CMakeLists.txt:403 (MESSAGE):
>> HDF5 Support specified, cannot find ZLib.
>>
>> CMake Error: The following variables are used in this project, but they
>> are set to NOTFOUND.
>> Please set them or make sure they are set and tested correctly in the
>> CMake files:
>> HDF5_INCLUDE_DIR
>>
>> used as include directory in directory W:/netcdf_svn
>> used as include directory in directory W:/netcdf_svn
>> used as include directory in directory W:/netcdf_svn
>> used as include directory in directory W:/netcdf_svn
>>
>> -- Configuring incomplete, errors occurred!
>>
>>
>> How can I make the supplied CMake projects to detect my HDF5 and zlib
>> locations?
>>
>> Thanks
>>
>> Pedro
>>
>>
>> ------
>> Pedro Vicente, Earth System Science
>> University of California, Irvine
>> http://www.ess.uci.edu/
>>
>>
>> ----- Original Message ----- From: "Ward Fisher"
>> <wfisher@unidata.ucar.edu>
>> To: <netcdfgroup@unidata.ucar.edu>
>> Sent: Tuesday, February 26, 2013 5:04 PM
>> Subject: [netcdfgroup] netCDF 4.3 Release Candidate available
>>
>>> Good afternoon all,
>>>
>>> We are officially announcing the availability of the netCDF-C libraries
>>> version 4.3.0, release candidate 2.
>>>
>>> Documentation and source downloads are available at:
>>>
>>> http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp
>>>
>>> Pre-built Windows binaries are available at:
>>>
>>> http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html
>>>
>>> The previous Windows-specific website,
>>> http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this new
>>> location. Please note that these pre-built libraries (both 32 & 64-bit)
>>> are built and tested on 64-bit Windows 7 using Visual Studio 10.
>>>
>>> Highlights of the 4.3 release include:
>>>
>>> o Many bug fixes.
>>> o Improved DAP support.
>>> o Improved parallel-netcdf support.
>>> o Improved Windows support.
>>> o Integration of CMake, allow for Visual-Studio based builds.
>>>
>>> This release candidate is the precursor to either a new release
>>> candidate, or the final 4.3.0 release (depending on the number and
>>> severity of bugs reported). As always, we welcome any bug reports
>>> and/or feedback!
>>>
>>> Have a great evening,
>>>
>>> -Ward
>>> Ward Fisher
>>> wfisher@unidata.ucar.edu
>>>
>>> _______________________________________________
>>> netcdfgroup mailing list
>>> netcdfgroup@unidata.ucar.edu
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>
> _______________________________________________
> netcdfgroup mailing list
> netcdfgroup@unidata.ucar.edu
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

[Pedro_Vicente1]

CMake provides two ways to find libraries:
1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})
   where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to
hdf5library}/cmake/hdf5"

2. Non-cmake built HDF5 - use FIND_PACKAGE (HDF5)
   where ENV{HDF5_ROOT}="{path to hdf5library}"

thank you for the reply, but this is not clear to me...

what does this mean ? Do I have to edit and change any file ?

I just want a command line example that allows me, in a Windows shell, to do 2 things:

1) build HDF5 from source using Cmake

I tried using, per the instructions supplied , with my actual zlib header and lib file

cmake .. -D"ZLIB_INCLUDE_DIR:PATH=T:\zlib-1.2.3" -D"ZLIB_LIBRARY:FILEPATH=T:\zlib-1.2.3\projects\visualc6\Win32_LIB_Debug\zlibd.lib"

but I got the compiler errors in the previous email due to the generated Visual Studio projects cannot find the zlib header...
sure, I can edit the Visual Studio project, and add the header location, which I did, but I would like to know if I missed something on the command above, so that I won't have to do that edit next time,
or is this a HDF5 Cmake project build bug ?

2) build netCDF using the HDF5 *source* build (the above) ; using the HDF5 *binary* build, it's possible with

cmake .. -D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5" -D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10"

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Allen D Byrne" <byrn@hdfgroup.org>
To: <hdf-forum@hdfgroup.org>
Cc: <help@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>; "Ward Fisher" <wfisher@unidata.ucar.edu>
Sent: Friday, March 29, 2013 11:49 AM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

CMake provides two ways to find libraries:
1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})
   where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to
hdf5library}/cmake/hdf5"

2. Non-cmake built HDF5 - use FIND_PACKAGE (HDF5)
   where ENV{HDF5_ROOT}="{path to hdf5library}"

Allen

On Friday, March 29, 2013 10:32:04 AM Pedro Vicente wrote:

Hi Ward

I was able to built netCDF using the latest HDF5 binaries with Cmake info
that I got from here

http://www.hdfgroup.org/HDF5/release/obtain5.html

using these 2 options

-D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10"
-D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5"

my next step is

1) Build using the same source distribution of HDF5, instead of the
pre-compiled binaries
2) Build using a HDF5 version without Cmake information

Is it possible to to this?
I noticed that the source HDF5 files do not include this folder, that is
available only in the binaries T:\hdf5_install_1.8.10\cmake\hdf5

Ideally what woulde be needed is a way for the Cmake system to find the HDF5
header files location and the name of the library hdf5.lib... that's all
Visual Studio needs...
something like

-D"MY_HDF5_HEADER_FOLDER=<etc>
-D"MY_HDF5_LIBRARY_FILE=<etc>

thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message -----
From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake
build in Windows

> Hi Pedro,
>
> If your hdf5 libraries are installed in W:\hdf5_install, for example, > you
> would specify the following argument:
>
> -DCMAKE_PREFIX_PATH=W:\hdf5_install
>
> CMake would then check this location first when looking for any header > and
> library files. The netCDF build will use the zlib library included > with
> the hdf5 binary distribution. If you do not have this, or if it is
> installed elsewhere, you can specify multiple search locations thusly:
>
> -DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".
>
> I hope this helps!
>
> -Ward
>
> On 3/14/13 7:04 PM, Pedro Vicente wrote:
>> Hi Ward
>>
>> I tried to build in Windows with CMake, using
>>
>> cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install
>>
>> I get these messages
>>
>> -- Building for: Visual Studio 10
>> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
>> -- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
>> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
>>
>> CMake Error at CMakeLists.txt:403 (MESSAGE):
>> HDF5 Support specified, cannot find ZLib.
>>
>> CMake Error: The following variables are used in this project, but >> they
>> are set to NOTFOUND.
>> Please set them or make sure they are set and tested correctly in the
>> CMake files:
>> HDF5_INCLUDE_DIR
>>
>> used as include directory in directory W:/netcdf_svn
>>
>> -- Configuring incomplete, errors occurred!
>>
>> How can I make the supplied CMake projects to detect my HDF5 and zlib
>> locations?
>>
>> Thanks
>>
>> Pedro
>>
>> ------
>> Pedro Vicente, Earth System Science
>> University of California, Irvine
>> http://www.ess.uci.edu/
>>
>> ----- Original Message ----- From: "Ward Fisher"
>> <wfisher@unidata.ucar.edu>
>> To: <netcdfgroup@unidata.ucar.edu>
>> Sent: Tuesday, February 26, 2013 5:04 PM
>> Subject: [netcdfgroup] netCDF 4.3 Release Candidate available
>>
>>> Good afternoon all,
>>>
>>> We are officially announcing the availability of the netCDF-C >>> libraries
>>> version 4.3.0, release candidate 2.
>>>
>>> Documentation and source downloads are available at:
>>>
>>> http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp
>>>
>>> Pre-built Windows binaries are available at:
>>>
>>> http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html
>>>
>>> The previous Windows-specific website,
>>> http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this >>> new
>>> location. Please note that these pre-built libraries (both 32 & >>> 64-bit)
>>> are built and tested on 64-bit Windows 7 using Visual Studio 10.
>>>
>>> Highlights of the 4.3 release include:
>>>
>>> o Many bug fixes.
>>> o Improved DAP support.
>>> o Improved parallel-netcdf support.
>>> o Improved Windows support.
>>> o Integration of CMake, allow for Visual-Studio based builds.
>>>
>>> This release candidate is the precursor to either a new release
>>> candidate, or the final 4.3.0 release (depending on the number and
>>> severity of bugs reported). As always, we welcome any bug reports
>>> and/or feedback!
>>>
>>> Have a great evening,
>>>
>>> -Ward
>>> Ward Fisher
>>> wfisher@unidata.ucar.edu
>>>
>>> _______________________________________________
>>> netcdfgroup mailing list
>>> netcdfgroup@unidata.ucar.edu
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>
> _______________________________________________
> netcdfgroup mailing list
> netcdfgroup@unidata.ucar.edu
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

[Pedro_Vicente1]

Hi Allen, Ward

CMake provides two ways to find libraries:
1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})
   where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to
hdf5library}/cmake/hdf5"

Is it possible just to use the command line to build netCDF using the *source* HDF5 Cmake distribution ?

I was able to build netCDF only with the precompiled HDF5 Cmake made *binaries* , with these 2 options

-D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10" -D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5"

Now I am trying the new HDF5 release with CMake, replacing the above with

"T:\hdf5-1.8.11-pre1"

but I get this error

CMake Error at CMakeLists.txt:391 (MESSAGE):
  netCDF-4 support specified, but hdf5 libraries not found.
-- Configuring incomplete, errors occurred!

Unlike the HDF5 1.8.10 binaries, the source of hdf5-1.8.11-pre1 the does not include a "cmake/hdf5" folder

Also, the hdf5-1.8.11-pre1 Cmake build is missing the Dimension Scales API, a must have for netCDF

Thanks

Pedro

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message ----- From: "Allen D Byrne" <byrn@hdfgroup.org>
To: <hdf-forum@hdfgroup.org>
Cc: "Pedro Vicente" <pvicente@uci.edu>; "Ward Fisher" <wfisher@unidata.ucar.edu>; <help@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 29, 2013 11:49 AM
Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake build in Windows

CMake provides two ways to find libraries:
1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})
   where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to
hdf5library}/cmake/hdf5"

2. Non-cmake built HDF5 - use FIND_PACKAGE (HDF5)
   where ENV{HDF5_ROOT}="{path to hdf5library}"

Allen

On Friday, March 29, 2013 10:32:04 AM Pedro Vicente wrote:

Hi Ward

I was able to built netCDF using the latest HDF5 binaries with Cmake info
that I got from here

http://www.hdfgroup.org/HDF5/release/obtain5.html

using these 2 options

-D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10"
-D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5"

my next step is

1) Build using the same source distribution of HDF5, instead of the
pre-compiled binaries
2) Build using a HDF5 version without Cmake information

Is it possible to to this?
I noticed that the source HDF5 files do not include this folder, that is
available only in the binaries T:\hdf5_install_1.8.10\cmake\hdf5

Ideally what woulde be needed is a way for the Cmake system to find the HDF5
header files location and the name of the library hdf5.lib... that's all
Visual Studio needs...
something like

-D"MY_HDF5_HEADER_FOLDER=<etc>
-D"MY_HDF5_LIBRARY_FILE=<etc>

thanks

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message -----
From: "Ward Fisher" <wfisher@unidata.ucar.edu>
To: "Pedro Vicente" <pvicente@uci.edu>
Cc: <netcdfgroup@unidata.ucar.edu>
Sent: Friday, March 15, 2013 8:36 AM
Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available --- CMake
build in Windows

> Hi Pedro,
>
> If your hdf5 libraries are installed in W:\hdf5_install, for example, > you
> would specify the following argument:
>
> -DCMAKE_PREFIX_PATH=W:\hdf5_install
>
> CMake would then check this location first when looking for any header > and
> library files. The netCDF build will use the zlib library included > with
> the hdf5 binary distribution. If you do not have this, or if it is
> installed elsewhere, you can specify multiple search locations thusly:
>
> -DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".
>
> I hope this helps!
>
> -Ward
>
> On 3/14/13 7:04 PM, Pedro Vicente wrote:
>> Hi Ward
>>
>> I tried to build in Windows with CMake, using
>>
>> cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install
>>
>> I get these messages
>>
>> -- Building for: Visual Studio 10
>> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
>> -- HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
>> -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)
>>
>> CMake Error at CMakeLists.txt:403 (MESSAGE):
>> HDF5 Support specified, cannot find ZLib.
>>
>> CMake Error: The following variables are used in this project, but >> they
>> are set to NOTFOUND.
>> Please set them or make sure they are set and tested correctly in the
>> CMake files:
>> HDF5_INCLUDE_DIR
>>
>> used as include directory in directory W:/netcdf_svn
>>
>> -- Configuring incomplete, errors occurred!
>>
>> How can I make the supplied CMake projects to detect my HDF5 and zlib
>> locations?
>>
>> Thanks
>>
>> Pedro
>>
>> ------
>> Pedro Vicente, Earth System Science
>> University of California, Irvine
>> http://www.ess.uci.edu/
>>
>> ----- Original Message ----- From: "Ward Fisher"
>> <wfisher@unidata.ucar.edu>
>> To: <netcdfgroup@unidata.ucar.edu>
>> Sent: Tuesday, February 26, 2013 5:04 PM
>> Subject: [netcdfgroup] netCDF 4.3 Release Candidate available
>>
>>> Good afternoon all,
>>>
>>> We are officially announcing the availability of the netCDF-C >>> libraries
>>> version 4.3.0, release candidate 2.
>>>
>>> Documentation and source downloads are available at:
>>>
>>> http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp
>>>
>>> Pre-built Windows binaries are available at:
>>>
>>> http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html
>>>
>>> The previous Windows-specific website,
>>> http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to this >>> new
>>> location. Please note that these pre-built libraries (both 32 & >>> 64-bit)
>>> are built and tested on 64-bit Windows 7 using Visual Studio 10.
>>>
>>> Highlights of the 4.3 release include:
>>>
>>> o Many bug fixes.
>>> o Improved DAP support.
>>> o Improved parallel-netcdf support.
>>> o Improved Windows support.
>>> o Integration of CMake, allow for Visual-Studio based builds.
>>>
>>> This release candidate is the precursor to either a new release
>>> candidate, or the final 4.3.0 release (depending on the number and
>>> severity of bugs reported). As always, we welcome any bug reports
>>> and/or feedback!
>>>
>>> Have a great evening,
>>>
>>> -Ward
>>> Ward Fisher
>>> wfisher@unidata.ucar.edu
>>>
>>> _______________________________________________
>>> netcdfgroup mailing list
>>> netcdfgroup@unidata.ucar.edu
>>> For list information or to unsubscribe, visit:
>>> http://www.unidata.ucar.edu/mailing_lists/
>
> _______________________________________________
> netcdfgroup mailing list
> netcdfgroup@unidata.ucar.edu
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@hdfgroup.org
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

[Pedro_Vicente1]

I was able to build netCDF with CMake using

cmake -D"HDF5_INCLUDE_DIR=T:\hdf5-1.8.11-pre1\src" -D"HDF5_LIB=T:\hdf5-1.8.11-pre1\build\bin\Debug\libhdf5_D.lib" -D"HDF5_HL_LIB=T:\hdf5-1.8.11-pre1\build\bin\Debug\libhdf5_hl_D.lib" -D"ZLIB_INCLUDE_DIR:PATH=T:\zlib-1.2.5" -D"ZLIB_LIBRARY:FILEPATH=T:\zlib-1.2.5\build\bin\Debug\libzlib_D.lib" -D"SZIP_INCLUDE_DIR:PATH=T:\szip-2.1\src" -D"SZIP_LIBRARY:FILEPATH=T:\szip-2.1\build\bin\Debug\libszip_D.lib" -D"ENABLE_DAP=ON" -D"BUILD_SHARED_LIBS=OFF" -D"ENABLE_DLL=OFF" -D"CURL_LIBRARY=W:\curl-7.29.0\builds\libcurl-vc10-x86-debug-static-ipv6-sspi-spnego-winssl\lib\libcurl_a_debug.lib" -D"CURL_INCLUDE_DIR=W:\curl-7.29.0\builds\libcurl-vc10-x86-debug-static-ipv6-sspi-spnego-winssl\include"…I found the needed options in the fileCMakeLists.txt MESSAGE(STATUS "Found HDF5: ${HDF5_LIB}") MESSAGE(STATUS "Found HDF5_HL: ${HDF5_HL_LIB}") MESSAGE(STATUS "Found HDF5 Includes: ${HDF5_INCLUDE_DIR}")This should be explained in COMPILE_CMake.txtAlso, I got 2 compiling errors due to missing HDF5 header files15>…\…\h5_test\tst_h_vars2.c(13): fatal error C1083: Cannot open includefile: 'H5DSpublic.h': No such file or directorythis seems to be because this file is not located in theHDF5_INCLUDE_DIRI specified ,so I had to put it there to avoid the error------Pedro Vicente, Earth System ScienceUniversity of California, Irvinehttp://www.ess.uci.edu/----- Original Message -----From: "Pedro Vicente" <pvicente@uci.edu>To: "Allen D Byrne" <byrn@hdfgroup.org>; <hdf-forum@hdfgroup.org>Cc: <help@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>Sent: Thursday, April 18, 2013 8:47 PM!
re1 the doesnot include a "cmake/hdf5" folder>> Also, the hdf5-1.8.11-
pre1 Cmake build is missing the Dimension ScalesAPI, a must have for netCDF>> Thanks>> Pedro>>> ------> Pedro Vicente, Earth System Science> University of California, Irvine> http://www.ess.uci.edu/>>> ----- Original Message -----> From: "Allen D Byrne" <byrn@hdfgroup.org>> To: <hdf-forum@hdfgroup.org>> Cc: "Pedro Vicente" <pvicente@uci.edu>; "Ward Fisher"<wfisher@unidata.ucar.edu>; <help@hdfgroup.org>;<netcdfgroup@unidata.ucar.edu>> Sent: Friday, March 29, 2013 11:49 AM> Subject: Re: [Hdf-forum] [netcdfgroup] netCDF 4.3 Release Candidateavailable — CMake build in Windows>>>> CMake provides two ways to find libraries:>> 1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})>> where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to>> hdf5library}/cmake/hdf5">>>> 2. Non-cmake built HDF5 - use FIND_PACKAGE (HDF5)>> where ENV{HDF5_ROOT}="{path to hdf5library}">>>> Allen>>>> On Friday, March 29, 2013 10:32:04 AM Pedro Vicente wrote:>>> Hi Ward!
>>>>>> I was able to built netCDF using the latest HDF5 binaries with Cmakeinfo>>> that I got from here>>>>>> http://www.hdfgroup.org/HDF5/release/obtain5.html>>>>>>>>> using these 2 options>>>>>> -D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10">>> -D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5">>>>>> my next step is>>>>>> 1) Build using the same source distribution of HDF5, instead of the>>> pre-compiled binaries>>> 2) Build using a HDF5 version without Cmake information>>>>>> Is it possible to to this?>>> I noticed that the source HDF5 files do not include this folder, that is>>> available only in the binaries T:\hdf5_install_1.8.10\cmake\hdf5>>>>>> Ideally what woulde be needed is a way for the Cmake system to find theHDF5>>> header files location and the name of the library hdf5.lib… that'sall>>> Visual Studio needs…>>> something like>>>>>> -D"MY_HDF5_HEADER_FOLDER=<etc>>>> -D"MY_HDF5_LIBRARY_FILE=<etc>>>>>>> thanks>>>>>>>>> ------>>> Pedro Vicente, Earth System !
>>> University of California, Irvine>>> http://www.ess.uci.edu/
> >> I tried to build in Windows with CMake, using>>> >>>>> >>>>> >> cmake -DCMAKE_INSTALL_PREFIX=W:\netcdf_install>>> >>>>> >> I get these messages>>> >>>>> >>>>> >> – Building for: Visual Studio 10>>> >> – Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)>>> >> – HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND>>> >> – Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)>>> >>>>> >> CMake Error at CMakeLists.txt:403 (MESSAGE):>>> >> HDF5 Support specified, cannot find ZLib.>>> >>>>> >> CMake Error: The following variables are used in this project, butthey>>> >> are set to NOTFOUND.>>> >> Please set them or make sure they are set and tested correctly in the>>> >> CMake files:>>> >> HDF5_INCLUDE_DIR>>> >>>>> >> used as include directory in directory W:/netcdf_svn>>> >> used as include directory in directory W:/netcdf_svn>>> >> used as include directory in directory W:/netcdf_svn>>> >> used as include directory in directory W:!
/netcdf_svn>>> >>>>> >> – Configuring incomplete, errors occurred!>>>
>>>>> >>>>> >> How can I make the supplied CMake projects to detect my HDF5 and zlib>>> >> locations?>>> >>>>> >> Thanks>>> >>>>> >> Pedro>>> >>>>> >>>>> >> ------>>> >> Pedro Vicente, Earth System Science>>> >> University of California, Irvine>>> >> http://www.ess.uci.edu/>>> >>>>> >>>>> >> ----- Original Message ----- From: "Ward Fisher">>> >> <wfisher@unidata.ucar.edu>>>> >> To: <netcdfgroup@unidata.ucar.edu>>>> >> Sent: Tuesday, February 26, 2013 5:04 PM>>> >> Subject: [netcdfgroup] netCDF 4.3 Release Candidate available>>> >>>>> >>> Good afternoon all,>>> >>>>>> >>> We are officially announcing the availability of the netCDF-Clibraries>>> >>> version 4.3.0, release candidate 2.>>> >>>>>> >>> Documentation and source downloads are available at:>>> >>>>>> >>> http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc/index.jsp>>> >>>>>> >>> Pre-built Windows binaries are available at:>>> >>>>>> >>> http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html>>> >>>>>> >>>!
  The previous Windows-specific website,>>> >>> http://www.unidata.ucar.edu/netcdf/win_netcdf/ will redirect to thisnew>>> >>> location. Please note that these pre-built libraries (both 32 &64-bit)>>> >>> are built and tested on 64-bit Windows 7 using Visual Studio 10.>>> >>>>>> >>> Highlights of the 4.3 release include:>>> >>>>>> >>> o Many bug fixes.>>> >>> o Improved DAP support.>>> >>> o Improved parallel-netcdf support.>>> >>> o Improved Windows support.>>> >>> o Integration of CMake, allow for Visual-Studio based builds.>>> >>>>>> >>> This release candidate is the precursor to either a new release>>> >>> candidate, or the final 4.3.0 release (depending on the number and>>> >>> severity of bugs reported). As always, we welcome any bug reports>>> >>> and/or feedback!>>> >>>>>> >>> Have a great evening,>>> >>>>>> >>> -Ward>>> >>> Ward Fisher>>> >>> wfisher@unidata.ucar.edu>>> >>>>>> >>> _______________________________________________>>> >>> netcdfgroup mailing list>>> >!
>> netcdfgroup@unidata.ucar.edu>>> >>> For list information or to unsu
bscribe, visit:>>> >>> http://www.unidata.ucar.edu/mailing_lists/>>> >>>> > _______________________________________________>>> > netcdfgroup mailing list>>> > netcdfgroup@unidata.ucar.edu>>> > For list information or to unsubscribe, visit:>>> > http://www.unidata.ucar.edu/mailing_lists/>>>>>> _______________________________________________>>> Hdf-forum is for HDF software users discussion.>>> Hdf-forum@hdfgroup.org>>> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org>>>>>> _______________________________________________> netcdfgroup mailing list> netcdfgroup@unidata.ucar.edu> For list information or to unsubscribe, visit:http://www.unidata.ucar.edu/mailing_lists/>

···

Subject: Re: [netcdfgroup] [Hdf-forum] netCDF 4.3 ReleaseCandidateavailable --- CMake build in Windows> Hi Allen, Ward>>>> CMake provides two ways to find libraries:>> 1. CMake built HDF5 - use FIND_PACKAGE (HDF5 NAMES ${HDF5_PACKAGE_NAME})>> where HDF5_PACKAGE_NAME:STRING="hdf5" and ENV{HDF5_DIR}="{path to>> hdf5library}/cmake/hdf5">>> Is it possible just to use the command line to build netCDF using the*source* HDF5 Cmake distribution ?>> I was able to build netCDF only with the precompiled HDF5 Cmake made*binaries* , with these 2 options>> -D"CMAKE_PREFIX_PATH=T:\hdf5_install_1.8.10" -D"HDF5_ROOT_DIR=T:\hdf5_install_1.8.10\cmake\hdf5">> Now I am trying the new HDF5 release with CMake, replacing the above with>> "T:\hdf5-1.8.11-pre1">> but I get this error>> CMake Error at CMakeLists.txt:391 (MESSAGE):> netCDF-4 support specified, but hdf5 libraries not found.> -- Configuring incomplete, errors occurred!>> Unlike the HDF5 1.8.10 binaries, the source of hdf5-1.8.11-p!

----- Original Message ----->>> From: "Ward Fisher" <wfisher@unidata.ucar.edu>>>> To: "Pedro Vicente" <pvicente@uci.edu>>>> Cc: <netcdfgroup@unidata.ucar.edu>>>> Sent: Friday, March 15, 2013 8:36 AM>>> Subject: Re: [netcdfgroup] netCDF 4.3 Release Candidate available ---CMake>>> build in Windows>>>>>> > Hi Pedro,>>> >>>> > If your hdf5 libraries are installed in W:\hdf5_install, for example,you>>> > would specify the following argument:>>> >>>> > -DCMAKE_PREFIX_PATH=W:\hdf5_install>>> >>>> > CMake would then check this location first when looking for any headerand>>> > library files. The netCDF build will use the zlib library includedwith>>> > the hdf5 binary distribution. If you do not have this, or if it is>>> > installed elsewhere, you can specify multiple search locations thusly:>>> >>>> > -DCMAKE_PREFIX_PATH="W:\hdf5_install;W:\zlib_install".>>> >>>> > I hope this helps!>>> >>>> > -Ward>>> >>>> > On 3/14/13 7:04 PM, Pedro Vicente wrote:>>> >> Hi Ward>>> >>>>!

[Pedro_Vicente1]

not sure what happened to my last email , here's hopefully a readable one

I was able to build netCDF with CMake using

cmake -D"HDF5_INCLUDE_DIR=T:\hdf5-1.8.11-pre1\src" -D"HDF5_LIB=T:\hdf5-1.8.11-pre1\build\bin\Debug\libhdf5_D.lib"
-D"HDF5_HL_LIB=T:\hdf5-1.8.11-pre1\build\bin\Debug\libhdf5_hl_D.lib" -D"ZLIB_INCLUDE_DIR:PATH=T:\zlib-1.2.5"
-D"ZLIB_LIBRARY:FILEPATH=T:\zlib-1.2.5\build\bin\Debug\libzlib_D.lib" -D"SZIP_INCLUDE_DIR:PATH=T:\szip-2.1\src"
-D"SZIP_LIBRARY:FILEPATH=T:\szip-2.1\build\bin\Debug\libszip_D.lib" -D"ENABLE_DAP=ON"
  -D"BUILD_SHARED_LIBS=OFF" -D"ENABLE_DLL=OFF" -D"CURL_LIBRARY=W:\curl-7.29.0\builds\libcurl-vc10-x86-debug-static-ipv6-sspi-spnego-winssl\lib\libcurl_a_debug.lib"
-D"CURL_INCLUDE_DIR=W:\curl-7.29.0\builds\libcurl-vc10-x86-debug-static-ipv6-sspi-spnego-winssl\include"..

I found the needed options in the file

CMakeLists.txt

MESSAGE(STATUS "Found HDF5: ${HDF5_LIB}")
MESSAGE(STATUS "Found HDF5_HL: ${HDF5_HL_LIB}")
MESSAGE(STATUS "Found HDF5 Includes: ${HDF5_INCLUDE_DIR}")

This should be explained in

COMPILE_CMake.txt

Also, I got 2 compiling errors due to missing HDF5 header files15>..\..\h5_test\tst_h_vars2.c(13): fatal error C1083: Cannot open includefile: 'H5DSpublic.h': No such file or directory

this seems to be because this file is not located in the

HDF5_INCLUDE_DIR

I specified ,so I had to put it there to avoid the error

Phew ....

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

----- Original Message -----
From: "Pedro Vicente" <pvicente@uci.edu>
To: "Allen D Byrne" <byrn@hdfgroup.org>; <hdf-forum@hdfgroup.org>
Cc: <help@hdfgroup.org>; <netcdfgroup@unidata.ucar.edu>
Sent: Friday, April 19, 2013 1:50 AM
Subject: Re: [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable--- CMake build in Windows

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

[John_Biddiscombe]

Hello

I saw this thread and am in need of cmakeified netCDF for a project, so I tried downloading and building the tarball on win8/vs2012 - naturally, it failed.

Is it not safe to assume that anyone building netCDF for themselves using cmake has also already built hdf5 themselves using cmake first. If so, then it is not necessary to

INCLUDE (${CMAKE_SOURCE_DIR}/cmake/modules/windows/FindHDF5.cmake)

But rather just use

find_package(HDF5 NO_MODULE)

and then all the checks for includes/libs and all the other stuff I had to remove just go away. Just link to hdf5 or hdf5_hl as the targets are imported for you.

With a few tweaks and removing all the unnecessary checks, all builds fine. Is there a repo to which I can submit a patch?

I tried running the tests and got quite a few fails.

Should I try to find what's wrong with them, or are they 'known' to fail on windows.

JB

Test project C:/cmakebuild/netcdf-4.3

        Start 1: ncdump_ctest

  1/106 Test #1: ncdump_ctest ..................... Passed 0.02 sec

        Start 2: ncdump_ctest64

  2/106 Test #2: ncdump_ctest64 ................... Passed 0.02 sec

        Start 3: ncdump_tst_utf8

  3/106 Test #3: ncdump_tst_utf8 .................. Passed 0.02 sec

        Start 4: ncdump_tst_create_files

  4/106 Test #4: ncdump_tst_create_files ..........***Failed 0.02 sec

        Start 5: ncdump_tst_group_data

  5/106 Test #5: ncdump_tst_group_data ............***Failed 0.02 sec

        Start 6: ncdump_tst_enum_data

  6/106 Test #6: ncdump_tst_enum_data .............***Failed 0.03 sec

        Start 7: ncdump_tst_opaque_data

  7/106 Test #7: ncdump_tst_opaque_data ...........***Failed 0.02 sec

        Start 8: ncdump_tst_string_data

  8/106 Test #8: ncdump_tst_string_data ...........***Failed 0.02 sec

        Start 9: ncdump_tst_vlen_data

  9/106 Test #9: ncdump_tst_vlen_data .............***Failed 0.02 sec

        Start 10: ncdump_tst_comp

10/106 Test #10: ncdump_tst_comp ..................***Failed 0.02 sec

        Start 11: ncdump_tst_comp2

11/106 Test #11: ncdump_tst_comp2 .................***Failed 0.04 sec

        Start 12: ncdump_tst_nans

12/106 Test #12: ncdump_tst_nans .................. Passed 0.02 sec

        Start 13: ncdump_tst_unicode

13/106 Test #13: ncdump_tst_unicode ...............***Failed 0.02 sec

        Start 14: nctest

14/106 Test #14: nctest ...........................***Failed 0.60 sec

        Start 15: tst_rename

15/106 Test #15: tst_rename ....................... Passed 0.01 sec

        Start 16: nc_test_t_nc

16/106 Test #16: nc_test_t_nc ..................... Passed 0.01 sec

        Start 17: nc_test_tst_small

17/106 Test #17: nc_test_tst_small ................***Failed 0.24 sec

        Start 18: nc_test_tst_misc

18/106 Test #18: nc_test_tst_misc ................. Passed 0.03 sec

        Start 19: nc_test_tst_norm

19/106 Test #19: nc_test_tst_norm ................. Passed 0.01 sec

        Start 20: nc_test_tst_names

20/106 Test #20: nc_test_tst_names ................***Failed 0.03 sec

        Start 21: nc_test_tst_nofill

21/106 Test #21: nc_test_tst_nofill ............... Passed 0.31 sec

        Start 22: nc_test_tst_nofill2

22/106 Test #22: nc_test_tst_nofill2 .............. Passed 0.08 sec

        Start 23: nc_test_tst_nofill3

23/106 Test #23: nc_test_tst_nofill3 .............. Passed 0.03 sec

        Start 24: nc_test_tst_atts

24/106 Test #24: nc_test_tst_atts .................***Failed 0.02 sec

        Start 25: nc_test

25/106 Test #25: nc_test ..........................***Failed 2.57 sec

        Start 26: nc_test4_tst_dims

26/106 Test #26: nc_test4_tst_dims ................***Failed 0.02 sec

        Start 27: nc_test4_tst_dims2

27/106 Test #27: nc_test4_tst_dims2 ...............***Failed 0.02 sec

        Start 28: nc_test4_tst_dims3

28/106 Test #28: nc_test4_tst_dims3 ...............***Failed 0.02 sec

        Start 29: nc_test4_tst_files

29/106 Test #29: nc_test4_tst_files ...............***Failed 0.03 sec

        Start 30: nc_test4_tst_files4

30/106 Test #30: nc_test4_tst_files4 ..............***Failed 0.02 sec

        Start 31: nc_test4_tst_vars

31/106 Test #31: nc_test4_tst_vars ................***Failed 0.02 sec

        Start 32: nc_test4_tst_varms

32/106 Test #32: nc_test4_tst_varms ...............***Failed 0.02 sec

        Start 33: nc_test4_tst_unlim_vars

33/106 Test #33: nc_test4_tst_unlim_vars ..........***Failed 0.02 sec

        Start 34: nc_test4_tst_converts

34/106 Test #34: nc_test4_tst_converts ............***Failed 0.02 sec

        Start 35: nc_test4_tst_converts2

35/106 Test #35: nc_test4_tst_converts2 ...........***Failed 0.02 sec

        Start 36: nc_test4_tst_grps

36/106 Test #36: nc_test4_tst_grps ................***Failed 0.05 sec

        Start 37: nc_test4_tst_grps2

37/106 Test #37: nc_test4_tst_grps2 ...............***Failed 0.02 sec

        Start 38: nc_test4_tst_compounds

38/106 Test #38: nc_test4_tst_compounds ...........***Failed 0.02 sec

        Start 39: nc_test4_tst_compounds2

39/106 Test #39: nc_test4_tst_compounds2 .......... Passed 0.03 sec

        Start 40: nc_test4_tst_compounds3

40/106 Test #40: nc_test4_tst_compounds3 ..........***Failed 0.02 sec

        Start 41: nc_test4_tst_opaques

41/106 Test #41: nc_test4_tst_opaques .............***Failed 0.02 sec

        Start 42: nc_test4_tst_strings

42/106 Test #42: nc_test4_tst_strings .............***Failed 0.03 sec

        Start 43: nc_test4_tst_strings2

43/106 Test #43: nc_test4_tst_strings2 ............ Passed 0.02 sec

        Start 44: nc_test4_tst_interops

44/106 Test #44: nc_test4_tst_interops ............***Failed 0.02 sec

        Start 45: nc_test4_tst_interops4

45/106 Test #45: nc_test4_tst_interops4 ...........***Failed 0.02 sec

        Start 46: nc_test4_tst_interops6

46/106 Test #46: nc_test4_tst_interops6 ...........***Failed 0.02 sec

        Start 47: nc_test4_tst_enums

47/106 Test #47: nc_test4_tst_enums ...............***Failed 0.03 sec

        Start 48: nc_test4_tst_coords

48/106 Test #48: nc_test4_tst_coords ..............***Failed 0.02 sec

        Start 49: nc_test4_tst_coords2

49/106 Test #49: nc_test4_tst_coords2 .............***Failed 0.02 sec

        Start 50: nc_test4_tst_coords3

50/106 Test #50: nc_test4_tst_coords3 .............***Failed 0.02 sec

        Start 51: nc_test4_tst_vars3

51/106 Test #51: nc_test4_tst_vars3 ...............***Failed 0.02 sec

        Start 52: nc_test4_tst_vars4

52/106 Test #52: nc_test4_tst_vars4 ...............***Failed 0.04 sec

        Start 53: nc_test4_tst_chunks

53/106 Test #53: nc_test4_tst_chunks ..............***Failed 0.02 sec

        Start 54: nc_test4_tst_chunks2

54/106 Test #54: nc_test4_tst_chunks2 .............***Failed 0.02 sec

        Start 55: nc_test4_tst_utf8

55/106 Test #55: nc_test4_tst_utf8 ................***Failed 0.02 sec

        Start 56: nc_test4_tst_fills

56/106 Test #56: nc_test4_tst_fills ...............***Failed 0.02 sec

        Start 57: nc_test4_tst_fills2

57/106 Test #57: nc_test4_tst_fills2 ..............***Failed 0.02 sec

        Start 58: nc_test4_tst_fillbug

58/106 Test #58: nc_test4_tst_fillbug .............***Failed 0.02 sec

        Start 59: nc_test4_tst_xplatform

59/106 Test #59: nc_test4_tst_xplatform ...........***Failed 0.02 sec

        Start 60: nc_test4_tst_xplatform2

60/106 Test #60: nc_test4_tst_xplatform2 .......... Passed 0.03 sec

        Start 61: nc_test4_tst_h_atts2

61/106 Test #61: nc_test4_tst_h_atts2 ............. Passed 0.01 sec

        Start 62: nc_test4_tst_endian_fill

62/106 Test #62: nc_test4_tst_endian_fill .........***Failed 0.02 sec

        Start 63: nc_test4_tst_atts

63/106 Test #63: nc_test4_tst_atts ................***Failed 0.03 sec

        Start 64: nc_test4_t_type

64/106 Test #64: nc_test4_t_type .................. Passed 0.01 sec

        Start 65: nc_test4_cdm_sea_soundings

65/106 Test #65: nc_test4_cdm_sea_soundings .......***Failed 0.02 sec

        Start 66: nc_test4_tst_vl

66/106 Test #66: nc_test4_tst_vl ..................***Failed 0.02 sec

        Start 67: nc_test4_tst_atts1

67/106 Test #67: nc_test4_tst_atts1 ...............***Failed 0.04 sec

        Start 68: nc_test4_tst_atts2

68/106 Test #68: nc_test4_tst_atts2 ............... Passed 0.05 sec

        Start 69: nc_test4_tst_vars2

69/106 Test #69: nc_test4_tst_vars2 ...............***Failed 0.03 sec

        Start 70: nc_test4_tst_files5

70/106 Test #70: nc_test4_tst_files5 .............. Passed 0.02 sec

        Start 71: nc_test4_tst_files6

71/106 Test #71: nc_test4_tst_files6 ..............***Failed 0.02 sec

        Start 72: nc_test4_tst_sync

72/106 Test #72: nc_test4_tst_sync ................***Failed 0.02 sec

        Start 73: nc_test4_tst_h_strbug

73/106 Test #73: nc_test4_tst_h_strbug ............***Failed 0.05 sec

        Start 74: nc_test4_tst_h_refs

74/106 Test #74: nc_test4_tst_h_refs ..............***Failed 0.02 sec

        Start 75: tst_h_files

75/106 Test #75: tst_h_files ...................... Passed 0.03 sec

        Start 76: tst_h_files2

76/106 Test #76: tst_h_files2 ..................... Passed 0.01 sec

        Start 77: tst_h_files4

77/106 Test #77: tst_h_files4 ..................... Passed 0.02 sec

        Start 78: tst_h_atts

78/106 Test #78: tst_h_atts .......................***Failed 0.05 sec

        Start 79: tst_h_atts3

79/106 Test #79: tst_h_atts3 ...................... Passed 0.00 sec

        Start 80: tst_h_atts4

80/106 Test #80: tst_h_atts4 ...................... Passed 0.00 sec

        Start 81: tst_h_vars

81/106 Test #81: tst_h_vars .......................***Failed 0.03 sec

        Start 82: tst_h_vars2

82/106 Test #82: tst_h_vars2 ......................***Failed 0.02 sec

        Start 83: tst_h_vars3

83/106 Test #83: tst_h_vars3 ...................... Passed 0.02 sec

        Start 84: tst_h_grps

84/106 Test #84: tst_h_grps ....................... Passed 0.03 sec

        Start 85: tst_h_compounds

85/106 Test #85: tst_h_compounds .................. Passed 0.09 sec

        Start 86: tst_h_compounds2

86/106 Test #86: tst_h_compounds2 ................. Passed 0.02 sec

        Start 87: tst_h_wrt_cmp

87/106 Test #87: tst_h_wrt_cmp .................... Passed 0.02 sec

        Start 88: tst_h_rd_cmp

88/106 Test #88: tst_h_rd_cmp ..................... Passed 0.01 sec

        Start 89: tst_h_vl

89/106 Test #89: tst_h_vl ......................... Passed 0.02 sec

        Start 90: tst_h_opaques

90/106 Test #90: tst_h_opaques .................... Passed 0.01 sec

        Start 91: tst_h_strings

91/106 Test #91: tst_h_strings .................... Passed 0.03 sec

        Start 92: tst_h_strings1

92/106 Test #92: tst_h_strings1 ................... Passed 0.02 sec

        Start 93: tst_h_strings2

93/106 Test #93: tst_h_strings2 ................... Passed 0.02 sec

        Start 94: tst_h_ints

94/106 Test #94: tst_h_ints ....................... Passed 0.01 sec

        Start 95: tst_h_dimscales

95/106 Test #95: tst_h_dimscales ..................***Failed 0.02 sec

        Start 96: tst_h_dimscales1

96/106 Test #96: tst_h_dimscales1 .................***Failed 0.02 sec

        Start 97: tst_h_dimscales2

97/106 Test #97: tst_h_dimscales2 .................***Failed 0.04 sec

        Start 98: tst_h_dimscales3

98/106 Test #98: tst_h_dimscales3 .................***Failed 0.02 sec

        Start 99: tst_h_enums

99/106 Test #99: tst_h_enums ...................... Passed 0.02 sec

        Start 100: tst_h_dimscales4

100/106 Test #100: tst_h_dimscales4 .................***Failed 0.02 sec

        Start 101: C_tests_simple_xy_wr

101/106 Test #101: C_tests_simple_xy_wr ............. Passed 0.01 sec

        Start 102: C_tests_simple_xy_rd

102/106 Test #102: C_tests_simple_xy_rd ............. Passed 0.01 sec

        Start 103: C_tests_sfc_pres_temp_wr

103/106 Test #103: C_tests_sfc_pres_temp_wr ......... Passed 0.01 sec

        Start 104: C_tests_sfc_pres_temp_rd

104/106 Test #104: C_tests_sfc_pres_temp_rd ......... Passed 0.01 sec

        Start 105: C_tests_pres_temp_4D_wr

105/106 Test #105: C_tests_pres_temp_4D_wr .......... Passed 0.01 sec

        Start 106: C_tests_pres_temp_4D_rd

106/106 Test #106: C_tests_pres_temp_4D_rd .......... Passed 0.01 sec

40% tests passed, 64 tests failed out of 106

Total Test time (real) = 6.96 sec

The following tests FAILED:

          4 - ncdump_tst_create_files (Failed)

          5 - ncdump_tst_group_data (Failed)

          6 - ncdump_tst_enum_data (Failed)

          7 - ncdump_tst_opaque_data (Failed)

          8 - ncdump_tst_string_data (Failed)

          9 - ncdump_tst_vlen_data (Failed)

         10 - ncdump_tst_comp (Failed)

         11 - ncdump_tst_comp2 (Failed)

         13 - ncdump_tst_unicode (Failed)

         14 - nctest (Failed)

         17 - nc_test_tst_small (Failed)

         20 - nc_test_tst_names (Failed)

         24 - nc_test_tst_atts (Failed)

         25 - nc_test (Failed)

         26 - nc_test4_tst_dims (Failed)

         27 - nc_test4_tst_dims2 (Failed)

         28 - nc_test4_tst_dims3 (Failed)

         29 - nc_test4_tst_files (Failed)

         30 - nc_test4_tst_files4 (Failed)

         31 - nc_test4_tst_vars (Failed)

         32 - nc_test4_tst_varms (Failed)

         33 - nc_test4_tst_unlim_vars (Failed)

         34 - nc_test4_tst_converts (Failed)

         35 - nc_test4_tst_converts2 (Failed)

         36 - nc_test4_tst_grps (Failed)

         37 - nc_test4_tst_grps2 (Failed)

         38 - nc_test4_tst_compounds (Failed)

         40 - nc_test4_tst_compounds3 (Failed)

         41 - nc_test4_tst_opaques (Failed)

         42 - nc_test4_tst_strings (Failed)

         44 - nc_test4_tst_interops (Failed)

         45 - nc_test4_tst_interops4 (Failed)

         46 - nc_test4_tst_interops6 (Failed)

         47 - nc_test4_tst_enums (Failed)

         48 - nc_test4_tst_coords (Failed)

         49 - nc_test4_tst_coords2 (Failed)

         50 - nc_test4_tst_coords3 (Failed)

         51 - nc_test4_tst_vars3 (Failed)

         52 - nc_test4_tst_vars4 (Failed)

         53 - nc_test4_tst_chunks (Failed)

         54 - nc_test4_tst_chunks2 (Failed)

         55 - nc_test4_tst_utf8 (Failed)

         56 - nc_test4_tst_fills (Failed)

         57 - nc_test4_tst_fills2 (Failed)

         58 - nc_test4_tst_fillbug (Failed)

         59 - nc_test4_tst_xplatform (Failed)

         62 - nc_test4_tst_endian_fill (Failed)

         63 - nc_test4_tst_atts (Failed)

         65 - nc_test4_cdm_sea_soundings (Failed)

         66 - nc_test4_tst_vl (Failed)

         67 - nc_test4_tst_atts1 (Failed)

         69 - nc_test4_tst_vars2 (Failed)

         71 - nc_test4_tst_files6 (Failed)

         72 - nc_test4_tst_sync (Failed)

         73 - nc_test4_tst_h_strbug (Failed)

         74 - nc_test4_tst_h_refs (Failed)

         78 - tst_h_atts (Failed)

         81 - tst_h_vars (Failed)

         82 - tst_h_vars2 (Failed)

         95 - tst_h_dimscales (Failed)

         96 - tst_h_dimscales1 (Failed)

         97 - tst_h_dimscales2 (Failed)

         98 - tst_h_dimscales3 (Failed)

        100 - tst_h_dimscales4 (Failed)

Errors while running CTest

[John_Biddiscombe]

Just a follow up, it turns out my code was linking to debug libraries for hdf, but release for hdf5_hl, I hadn't removed all the necessary hdf5 link crud, once that was fixed, tests are almost complete. Just 3 fails, which I'll look at later.

JB

c:\cmakebuild\netcdf-4.3>"c:\Program Files\cmake-2.8.10.1-win32-x86\bin\ctest.exe" -C Debug

Test project C:/cmakebuild/netcdf-4.3

        Start 1: ncdump_ctest

  1/106 Test #1: ncdump_ctest ..................... Passed 0.18 sec

        Start 2: ncdump_ctest64

  2/106 Test #2: ncdump_ctest64 ................... Passed 0.02 sec

        Start 3: ncdump_tst_utf8

  3/106 Test #3: ncdump_tst_utf8 .................. Passed 0.02 sec

        Start 4: ncdump_tst_create_files

  4/106 Test #4: ncdump_tst_create_files .......... Passed 0.03 sec

        Start 5: ncdump_tst_group_data

  5/106 Test #5: ncdump_tst_group_data ............ Passed 0.11 sec

        Start 6: ncdump_tst_enum_data

  6/106 Test #6: ncdump_tst_enum_data ............. Passed 0.04 sec

        Start 7: ncdump_tst_opaque_data

  7/106 Test #7: ncdump_tst_opaque_data ........... Passed 0.03 sec

        Start 8: ncdump_tst_string_data

  8/106 Test #8: ncdump_tst_string_data ........... Passed 0.03 sec

        Start 9: ncdump_tst_vlen_data

  9/106 Test #9: ncdump_tst_vlen_data ............. Passed 0.04 sec

        Start 10: ncdump_tst_comp

10/106 Test #10: ncdump_tst_comp .................. Passed 0.08 sec

        Start 11: ncdump_tst_comp2

11/106 Test #11: ncdump_tst_comp2 ................. Passed 0.04 sec

        Start 12: ncdump_tst_nans

12/106 Test #12: ncdump_tst_nans .................. Passed 0.02 sec

        Start 13: ncdump_tst_unicode

13/106 Test #13: ncdump_tst_unicode ............... Passed 0.03 sec

        Start 14: nctest

14/106 Test #14: nctest ........................... Passed 1.70 sec

        Start 15: tst_rename

15/106 Test #15: tst_rename ....................... Passed 0.03 sec

        Start 16: nc_test_t_nc

16/106 Test #16: nc_test_t_nc ..................... Passed 0.03 sec

        Start 17: nc_test_tst_small

17/106 Test #17: nc_test_tst_small ................ Passed 2.03 sec

        Start 18: nc_test_tst_misc

18/106 Test #18: nc_test_tst_misc ................. Passed 0.06 sec

        Start 19: nc_test_tst_norm

19/106 Test #19: nc_test_tst_norm ................. Passed 0.02 sec

        Start 20: nc_test_tst_names

20/106 Test #20: nc_test_tst_names ................ Passed 0.16 sec

        Start 21: nc_test_tst_nofill

21/106 Test #21: nc_test_tst_nofill ............... Passed 0.24 sec

        Start 22: nc_test_tst_nofill2

22/106 Test #22: nc_test_tst_nofill2 .............. Passed 0.09 sec

        Start 23: nc_test_tst_nofill3

23/106 Test #23: nc_test_tst_nofill3 .............. Passed 0.07 sec

        Start 24: nc_test_tst_atts

24/106 Test #24: nc_test_tst_atts ................. Passed 0.04 sec

        Start 25: nc_test

25/106 Test #25: nc_test .......................... Passed 43.26 sec

        Start 26: nc_test4_tst_dims

26/106 Test #26: nc_test4_tst_dims ................ Passed 0.20 sec

        Start 27: nc_test4_tst_dims2

27/106 Test #27: nc_test4_tst_dims2 ............... Passed 4.89 sec

        Start 28: nc_test4_tst_dims3

28/106 Test #28: nc_test4_tst_dims3 ............... Passed 0.25 sec

        Start 29: nc_test4_tst_files

29/106 Test #29: nc_test4_tst_files ............... Passed 0.44 sec

        Start 30: nc_test4_tst_files4

30/106 Test #30: nc_test4_tst_files4 .............. Passed 0.06 sec

        Start 31: nc_test4_tst_vars

31/106 Test #31: nc_test4_tst_vars ................***Failed 45.60 sec

        Start 32: nc_test4_tst_varms

32/106 Test #32: nc_test4_tst_varms ............... Passed 0.05 sec

        Start 33: nc_test4_tst_unlim_vars

33/106 Test #33: nc_test4_tst_unlim_vars .......... Passed 0.07 sec

        Start 34: nc_test4_tst_converts

34/106 Test #34: nc_test4_tst_converts ............ Passed 0.05 sec

        Start 35: nc_test4_tst_converts2

35/106 Test #35: nc_test4_tst_converts2 ...........***Failed 1.39 sec

        Start 36: nc_test4_tst_grps

36/106 Test #36: nc_test4_tst_grps ................ Passed 0.21 sec

        Start 37: nc_test4_tst_grps2

37/106 Test #37: nc_test4_tst_grps2 ............... Passed 0.14 sec

        Start 38: nc_test4_tst_compounds

38/106 Test #38: nc_test4_tst_compounds ........... Passed 0.12 sec

        Start 39: nc_test4_tst_compounds2

39/106 Test #39: nc_test4_tst_compounds2 .......... Passed 0.04 sec

        Start 40: nc_test4_tst_compounds3

40/106 Test #40: nc_test4_tst_compounds3 .......... Passed 0.04 sec

        Start 41: nc_test4_tst_opaques

41/106 Test #41: nc_test4_tst_opaques ............. Passed 0.05 sec

        Start 42: nc_test4_tst_strings

42/106 Test #42: nc_test4_tst_strings ............. Passed 0.16 sec

        Start 43: nc_test4_tst_strings2

43/106 Test #43: nc_test4_tst_strings2 ............ Passed 0.03 sec

        Start 44: nc_test4_tst_interops

44/106 Test #44: nc_test4_tst_interops ............ Passed 0.09 sec

        Start 45: nc_test4_tst_interops4

45/106 Test #45: nc_test4_tst_interops4 ........... Passed 0.40 sec

        Start 46: nc_test4_tst_interops6

46/106 Test #46: nc_test4_tst_interops6 ........... Passed 0.06 sec

        Start 47: nc_test4_tst_enums

47/106 Test #47: nc_test4_tst_enums ............... Passed 0.07 sec

        Start 48: nc_test4_tst_coords

48/106 Test #48: nc_test4_tst_coords .............. Passed 0.33 sec

        Start 49: nc_test4_tst_coords2

49/106 Test #49: nc_test4_tst_coords2 ............. Passed 0.16 sec

        Start 50: nc_test4_tst_coords3

50/106 Test #50: nc_test4_tst_coords3 ............. Passed 0.23 sec

        Start 51: nc_test4_tst_vars3

51/106 Test #51: nc_test4_tst_vars3 ............... Passed 1.25 sec

        Start 52: nc_test4_tst_vars4

52/106 Test #52: nc_test4_tst_vars4 ............... Passed 0.03 sec

        Start 53: nc_test4_tst_chunks

53/106 Test #53: nc_test4_tst_chunks .............. Passed 0.41 sec

        Start 54: nc_test4_tst_chunks2

54/106 Test #54: nc_test4_tst_chunks2 ............. Passed 1.37 sec

        Start 55: nc_test4_tst_utf8

55/106 Test #55: nc_test4_tst_utf8 ................ Passed 0.05 sec

        Start 56: nc_test4_tst_fills

56/106 Test #56: nc_test4_tst_fills ............... Passed 0.14 sec

        Start 57: nc_test4_tst_fills2

57/106 Test #57: nc_test4_tst_fills2 .............. Passed 0.07 sec

        Start 58: nc_test4_tst_fillbug

58/106 Test #58: nc_test4_tst_fillbug ............. Passed 0.04 sec

        Start 59: nc_test4_tst_xplatform

59/106 Test #59: nc_test4_tst_xplatform ........... Passed 0.04 sec

        Start 60: nc_test4_tst_xplatform2

60/106 Test #60: nc_test4_tst_xplatform2 .......... Passed 0.04 sec

        Start 61: nc_test4_tst_h_atts2

61/106 Test #61: nc_test4_tst_h_atts2 ............. Passed 0.02 sec

        Start 62: nc_test4_tst_endian_fill

62/106 Test #62: nc_test4_tst_endian_fill ......... Passed 0.04 sec

        Start 63: nc_test4_tst_atts

63/106 Test #63: nc_test4_tst_atts ................ Passed 0.05 sec

        Start 64: nc_test4_t_type

64/106 Test #64: nc_test4_t_type .................. Passed 0.02 sec

        Start 65: nc_test4_cdm_sea_soundings

65/106 Test #65: nc_test4_cdm_sea_soundings ....... Passed 0.03 sec

        Start 66: nc_test4_tst_vl

66/106 Test #66: nc_test4_tst_vl .................. Passed 0.06 sec

        Start 67: nc_test4_tst_atts1

67/106 Test #67: nc_test4_tst_atts1 ............... Passed 0.17 sec

        Start 68: nc_test4_tst_atts2

68/106 Test #68: nc_test4_tst_atts2 ............... Passed 0.06 sec

        Start 69: nc_test4_tst_vars2

69/106 Test #69: nc_test4_tst_vars2 ............... Passed 0.35 sec

        Start 70: nc_test4_tst_files5

70/106 Test #70: nc_test4_tst_files5 .............. Passed 0.03 sec

        Start 71: nc_test4_tst_files6

71/106 Test #71: nc_test4_tst_files6 .............. Passed 0.03 sec

        Start 72: nc_test4_tst_sync

72/106 Test #72: nc_test4_tst_sync ................ Passed 0.09 sec

        Start 73: nc_test4_tst_h_strbug

73/106 Test #73: nc_test4_tst_h_strbug ............ Passed 0.10 sec

        Start 74: nc_test4_tst_h_refs

74/106 Test #74: nc_test4_tst_h_refs .............. Passed 13.39 sec

        Start 75: tst_h_files

75/106 Test #75: tst_h_files ...................... Passed 1.56 sec

        Start 76: tst_h_files2

76/106 Test #76: tst_h_files2 ..................... Passed 0.32 sec

        Start 77: tst_h_files4

77/106 Test #77: tst_h_files4 ..................... Passed 0.11 sec

        Start 78: tst_h_atts

78/106 Test #78: tst_h_atts ....................... Passed 2.72 sec

        Start 79: tst_h_atts3

79/106 Test #79: tst_h_atts3 ...................... Passed 0.09 sec

        Start 80: tst_h_atts4

80/106 Test #80: tst_h_atts4 ...................... Passed 0.08 sec

        Start 81: tst_h_vars

81/106 Test #81: tst_h_vars .......................***Failed 2.33 sec

        Start 82: tst_h_vars2

82/106 Test #82: tst_h_vars2 ...................... Passed 2.96 sec

        Start 83: tst_h_vars3

83/106 Test #83: tst_h_vars3 ...................... Passed 0.26 sec

        Start 84: tst_h_grps

84/106 Test #84: tst_h_grps ....................... Passed 0.16 sec

        Start 85: tst_h_compounds

85/106 Test #85: tst_h_compounds .................. Passed 0.27 sec

        Start 86: tst_h_compounds2

86/106 Test #86: tst_h_compounds2 ................. Passed 0.05 sec

        Start 87: tst_h_wrt_cmp

87/106 Test #87: tst_h_wrt_cmp .................... Passed 0.05 sec

        Start 88: tst_h_rd_cmp

88/106 Test #88: tst_h_rd_cmp ..................... Passed 0.19 sec

        Start 89: tst_h_vl

89/106 Test #89: tst_h_vl ......................... Passed 0.19 sec

        Start 90: tst_h_opaques

90/106 Test #90: tst_h_opaques .................... Passed 0.06 sec

        Start 91: tst_h_strings

91/106 Test #91: tst_h_strings .................... Passed 0.10 sec

        Start 92: tst_h_strings1

92/106 Test #92: tst_h_strings1 ................... Passed 0.16 sec

        Start 93: tst_h_strings2

93/106 Test #93: tst_h_strings2 ................... Passed 0.08 sec

        Start 94: tst_h_ints

94/106 Test #94: tst_h_ints ....................... Passed 0.10 sec

        Start 95: tst_h_dimscales

95/106 Test #95: tst_h_dimscales .................. Passed 0.74 sec

        Start 96: tst_h_dimscales1

96/106 Test #96: tst_h_dimscales1 ................. Passed 0.09 sec

        Start 97: tst_h_dimscales2

97/106 Test #97: tst_h_dimscales2 ................. Passed 0.19 sec

        Start 98: tst_h_dimscales3

98/106 Test #98: tst_h_dimscales3 ................. Passed 0.06 sec

        Start 99: tst_h_enums

99/106 Test #99: tst_h_enums ...................... Passed 0.09 sec

        Start 100: tst_h_dimscales4

100/106 Test #100: tst_h_dimscales4 ................. Passed 0.14 sec

        Start 101: C_tests_simple_xy_wr

101/106 Test #101: C_tests_simple_xy_wr ............. Passed 0.17 sec

        Start 102: C_tests_simple_xy_rd

102/106 Test #102: C_tests_simple_xy_rd ............. Passed 0.07 sec

        Start 103: C_tests_sfc_pres_temp_wr

103/106 Test #103: C_tests_sfc_pres_temp_wr ......... Passed 0.04 sec

        Start 104: C_tests_sfc_pres_temp_rd

104/106 Test #104: C_tests_sfc_pres_temp_rd ......... Passed 0.08 sec

        Start 105: C_tests_pres_temp_4D_wr

105/106 Test #105: C_tests_pres_temp_4D_wr .......... Passed 0.07 sec

        Start 106: C_tests_pres_temp_4D_rd

106/106 Test #106: C_tests_pres_temp_4D_rd .......... Passed 0.07 sec

97% tests passed, 3 tests failed out of 106

Total Test time (real) = 136.75 sec

The following tests FAILED:

         31 - nc_test4_tst_vars (Failed)

         35 - nc_test4_tst_converts2 (Failed)

         81 - tst_h_vars (Failed)

Errors while running CTest

[Pedro_Vicente1]

Hi Ward

I tried the same command as John did.

I am using

1) hdf5-1.8.11-pre1 built with CMake
2) netCDF from the svn repo

Here's the output, 2 tests fail

W:\netcdf_svn\build>ctest -C Debug
Test project W:/netcdf_svn/build
        Start 1: ncdump_ctest
  1/108 Test #1: ncdump_ctest ..................... Passed 0.02 sec
        Start 2: ncdump_ctest64
  2/108 Test #2: ncdump_ctest64 ................... Passed 0.02 sec
        Start 3: ncdump_tst_utf8
  3/108 Test #3: ncdump_tst_utf8 .................. Passed 0.02 sec
        Start 4: ncdump_tst_create_files
  4/108 Test #4: ncdump_tst_create_files .......... Passed 0.05 sec
        Start 5: ncdump_tst_group_data
  5/108 Test #5: ncdump_tst_group_data ............ Passed 0.06 sec
        Start 6: ncdump_tst_enum_data
  6/108 Test #6: ncdump_tst_enum_data ............. Passed 0.03 sec
        Start 7: ncdump_tst_opaque_data
  7/108 Test #7: ncdump_tst_opaque_data ........... Passed 0.03 sec
        Start 8: ncdump_tst_string_data
  8/108 Test #8: ncdump_tst_string_data ........... Passed 0.05 sec
        Start 9: ncdump_tst_vlen_data
  9/108 Test #9: ncdump_tst_vlen_data ............. Passed 0.03 sec
        Start 10: ncdump_tst_comp
10/108 Test #10: ncdump_tst_comp .................. Passed 0.06 sec
        Start 11: ncdump_tst_comp2
11/108 Test #11: ncdump_tst_comp2 ................. Passed 0.03 sec
        Start 12: ncdump_tst_nans
12/108 Test #12: ncdump_tst_nans .................. Passed 0.02 sec
        Start 13: ncdump_tst_unicode
13/108 Test #13: ncdump_tst_unicode ............... Passed 0.03 sec
        Start 14: nctest
14/108 Test #14: nctest ........................... Passed 1.53 sec
        Start 15: tst_rename
15/108 Test #15: tst_rename ....................... Passed 0.02 sec
        Start 16: nc_test_t_nc
16/108 Test #16: nc_test_t_nc ..................... Passed 0.02 sec
        Start 17: nc_test_tst_small
17/108 Test #17: nc_test_tst_small ................ Passed 1.45 sec
        Start 18: nc_test_tst_misc
18/108 Test #18: nc_test_tst_misc ................. Passed 0.03 sec
        Start 19: nc_test_tst_norm
19/108 Test #19: nc_test_tst_norm ................. Passed 0.02 sec
        Start 20: nc_test_tst_names
20/108 Test #20: nc_test_tst_names ................ Passed 0.16 sec
        Start 21: nc_test_tst_nofill
21/108 Test #21: nc_test_tst_nofill ............... Passed 0.33 sec
        Start 22: nc_test_tst_nofill2
22/108 Test #22: nc_test_tst_nofill2 .............. Passed 0.08 sec
        Start 23: nc_test_tst_nofill3
23/108 Test #23: nc_test_tst_nofill3 .............. Passed 0.03 sec
        Start 24: nc_test_tst_atts
24/108 Test #24: nc_test_tst_atts ................. Passed 0.05 sec
        Start 25: nc_test
25/108 Test #25: nc_test .......................... Passed 62.01 sec
        Start 26: nc_test4_tst_dims
26/108 Test #26: nc_test4_tst_dims ................ Passed 0.11 sec
        Start 27: nc_test4_tst_dims2
27/108 Test #27: nc_test4_tst_dims2 ............... Passed 3.73 sec
        Start 28: nc_test4_tst_dims3
28/108 Test #28: nc_test4_tst_dims3 ............... Passed 0.12 sec
        Start 29: nc_test4_tst_files
29/108 Test #29: nc_test4_tst_files ............... Passed 0.62 sec
        Start 30: nc_test4_tst_files4
30/108 Test #30: nc_test4_tst_files4 .............. Passed 0.06 sec
        Start 31: nc_test4_tst_vars
31/108 Test #31: nc_test4_tst_vars ................***Failed 29.42 sec
        Start 32: nc_test4_tst_varms
32/108 Test #32: nc_test4_tst_varms ............... Passed 0.06 sec
        Start 33: nc_test4_tst_unlim_vars
33/108 Test #33: nc_test4_tst_unlim_vars .......... Passed 0.05 sec
        Start 34: nc_test4_tst_converts
34/108 Test #34: nc_test4_tst_converts ............ Passed 0.06 sec
        Start 35: nc_test4_tst_converts2
35/108 Test #35: nc_test4_tst_converts2 ........... Passed 0.08 sec
        Start 36: nc_test4_tst_grps
36/108 Test #36: nc_test4_tst_grps ................ Passed 0.19 sec
        Start 37: nc_test4_tst_grps2
37/108 Test #37: nc_test4_tst_grps2 ............... Passed 0.14 sec
        Start 38: nc_test4_tst_compounds
38/108 Test #38: nc_test4_tst_compounds ........... Passed 0.17 sec
        Start 39: nc_test4_tst_compounds2
39/108 Test #39: nc_test4_tst_compounds2 .......... Passed 0.03 sec
        Start 40: nc_test4_tst_compounds3
40/108 Test #40: nc_test4_tst_compounds3 .......... Passed 0.05 sec
        Start 41: nc_test4_tst_opaques
41/108 Test #41: nc_test4_tst_opaques ............. Passed 0.06 sec
        Start 42: nc_test4_tst_strings
42/108 Test #42: nc_test4_tst_strings ............. Passed 0.19 sec
        Start 43: nc_test4_tst_strings2
43/108 Test #43: nc_test4_tst_strings2 ............ Passed 0.03 sec
        Start 44: nc_test4_tst_interops
44/108 Test #44: nc_test4_tst_interops ............ Passed 0.05 sec
        Start 45: nc_test4_tst_interops4
45/108 Test #45: nc_test4_tst_interops4 ........... Passed 0.30 sec
        Start 46: nc_test4_tst_interops6
46/108 Test #46: nc_test4_tst_interops6 ........... Passed 0.03 sec
        Start 47: nc_test4_tst_enums
47/108 Test #47: nc_test4_tst_enums ............... Passed 0.03 sec
        Start 48: nc_test4_tst_coords
48/108 Test #48: nc_test4_tst_coords .............. Passed 0.11 sec
        Start 49: nc_test4_tst_coords2
49/108 Test #49: nc_test4_tst_coords2 ............. Passed 0.03 sec
        Start 50: nc_test4_tst_coords3
50/108 Test #50: nc_test4_tst_coords3 ............. Passed 0.06 sec
        Start 51: nc_test4_tst_vars3
51/108 Test #51: nc_test4_tst_vars3 ............... Passed 1.36 sec
        Start 52: nc_test4_tst_vars4
52/108 Test #52: nc_test4_tst_vars4 ............... Passed 0.03 sec
        Start 53: nc_test4_tst_chunks
53/108 Test #53: nc_test4_tst_chunks .............. Passed 0.11 sec
        Start 54: nc_test4_tst_chunks2
54/108 Test #54: nc_test4_tst_chunks2 ............. Passed 8.89 sec
        Start 55: nc_test4_tst_utf8
55/108 Test #55: nc_test4_tst_utf8 ................ Passed 0.05 sec
        Start 56: nc_test4_tst_fills
56/108 Test #56: nc_test4_tst_fills ............... Passed 0.06 sec
        Start 57: nc_test4_tst_fills2
57/108 Test #57: nc_test4_tst_fills2 .............. Passed 0.05 sec
        Start 58: nc_test4_tst_fillbug
58/108 Test #58: nc_test4_tst_fillbug ............. Passed 0.03 sec
        Start 59: nc_test4_tst_xplatform
59/108 Test #59: nc_test4_tst_xplatform ........... Passed 0.03 sec
        Start 60: nc_test4_tst_xplatform2
60/108 Test #60: nc_test4_tst_xplatform2 .......... Passed 0.03 sec
        Start 61: nc_test4_tst_h_atts2
61/108 Test #61: nc_test4_tst_h_atts2 ............. Passed 0.00 sec
        Start 62: nc_test4_tst_endian_fill
62/108 Test #62: nc_test4_tst_endian_fill ......... Passed 0.05 sec
        Start 63: nc_test4_tst_atts
63/108 Test #63: nc_test4_tst_atts ................ Passed 0.03 sec
        Start 64: nc_test4_t_type
64/108 Test #64: nc_test4_t_type .................. Passed 0.02 sec
        Start 65: nc_test4_cdm_sea_soundings
65/108 Test #65: nc_test4_cdm_sea_soundings ....... Passed 0.02 sec
        Start 66: nc_test4_tst_vl
66/108 Test #66: nc_test4_tst_vl .................. Passed 0.06 sec
        Start 67: nc_test4_tst_atts1
67/108 Test #67: nc_test4_tst_atts1 ............... Passed 0.12 sec
        Start 68: nc_test4_tst_atts2
68/108 Test #68: nc_test4_tst_atts2 ............... Passed 0.06 sec
        Start 69: nc_test4_tst_vars2
69/108 Test #69: nc_test4_tst_vars2 ............... Passed 0.25 sec
        Start 70: nc_test4_tst_files5
70/108 Test #70: nc_test4_tst_files5 .............. Passed 0.03 sec
        Start 71: nc_test4_tst_files6
71/108 Test #71: nc_test4_tst_files6 .............. Passed 0.03 sec
        Start 72: nc_test4_tst_sync
72/108 Test #72: nc_test4_tst_sync ................ Passed 0.03 sec
        Start 73: nc_test4_tst_h_strbug
73/108 Test #73: nc_test4_tst_h_strbug ............ Passed 0.05 sec
        Start 74: nc_test4_tst_h_refs
74/108 Test #74: nc_test4_tst_h_refs ..............***Failed 0.87 sec
        Start 75: tst_h_files
75/108 Test #75: tst_h_files ...................... Passed 0.03 sec
        Start 76: tst_h_files2
76/108 Test #76: tst_h_files2 ..................... Passed 0.02 sec
        Start 77: tst_h_files4
77/108 Test #77: tst_h_files4 ..................... Passed 0.03 sec
        Start 78: tst_h_atts
78/108 Test #78: tst_h_atts ....................... Passed 0.06 sec
        Start 79: tst_h_atts3
79/108 Test #79: tst_h_atts3 ...................... Passed 0.02 sec
        Start 80: tst_h_atts4
80/108 Test #80: tst_h_atts4 ...................... Passed 0.02 sec
        Start 81: tst_h_vars
81/108 Test #81: tst_h_vars ....................... Passed 0.03 sec
        Start 82: tst_h_vars2
82/108 Test #82: tst_h_vars2 ...................... Passed 2.31 sec
        Start 83: tst_h_vars3
83/108 Test #83: tst_h_vars3 ...................... Passed 0.03 sec
        Start 84: tst_h_grps
84/108 Test #84: tst_h_grps ....................... Passed 0.03 sec
        Start 85: tst_h_compounds
85/108 Test #85: tst_h_compounds .................. Passed 0.08 sec
        Start 86: tst_h_compounds2
86/108 Test #86: tst_h_compounds2 ................. Passed 0.03 sec
        Start 87: tst_h_wrt_cmp
87/108 Test #87: tst_h_wrt_cmp .................... Passed 0.02 sec
        Start 88: tst_h_rd_cmp
88/108 Test #88: tst_h_rd_cmp ..................... Passed 0.02 sec
        Start 89: tst_h_vl
89/108 Test #89: tst_h_vl ......................... Passed 0.03 sec
        Start 90: tst_h_opaques
90/108 Test #90: tst_h_opaques .................... Passed 0.02 sec
        Start 91: tst_h_strings
91/108 Test #91: tst_h_strings .................... Passed 0.05 sec
        Start 92: tst_h_strings1
92/108 Test #92: tst_h_strings1 ................... Passed 0.03 sec
        Start 93: tst_h_strings2
93/108 Test #93: tst_h_strings2 ................... Passed 0.03 sec
        Start 94: tst_h_ints
94/108 Test #94: tst_h_ints ....................... Passed 0.02 sec
        Start 95: tst_h_dimscales
95/108 Test #95: tst_h_dimscales .................. Passed 0.27 sec
        Start 96: tst_h_dimscales1
96/108 Test #96: tst_h_dimscales1 ................. Passed 0.02 sec
        Start 97: tst_h_dimscales2
97/108 Test #97: tst_h_dimscales2 ................. Passed 0.06 sec
        Start 98: tst_h_dimscales3
98/108 Test #98: tst_h_dimscales3 ................. Passed 0.02 sec
        Start 99: tst_h_enums
99/108 Test #99: tst_h_enums ...................... Passed 0.03 sec
        Start 100: tst_h_dimscales4
100/108 Test #100: tst_h_dimscales4 ................. Passed 0.03 sec
        Start 101: ncdap_test_partvar
101/108 Test #101: ncdap_test_partvar ............... Passed 0.78 sec
        Start 102: ncdap_test_varm3
102/108 Test #102: ncdap_test_varm3 ................. Passed 2.93 sec
        Start 103: C_tests_simple_xy_wr
103/108 Test #103: C_tests_simple_xy_wr ............. Passed 0.02 sec
        Start 104: C_tests_simple_xy_rd
104/108 Test #104: C_tests_simple_xy_rd ............. Passed 0.02 sec
        Start 105: C_tests_sfc_pres_temp_wr
105/108 Test #105: C_tests_sfc_pres_temp_wr ......... Passed 0.02 sec
        Start 106: C_tests_sfc_pres_temp_rd
106/108 Test #106: C_tests_sfc_pres_temp_rd ......... Passed 0.03 sec
        Start 107: C_tests_pres_temp_4D_wr
107/108 Test #107: C_tests_pres_temp_4D_wr .......... Passed 0.02 sec
        Start 108: C_tests_pres_temp_4D_rd
108/108 Test #108: C_tests_pres_temp_4D_rd .......... Passed 0.02 sec

98% tests passed, 2 tests failed out of 108

Total Test time (real) = 124.43 sec

The following tests FAILED:
         31 - nc_test4_tst_vars (Failed)
         74 - nc_test4_tst_h_refs (Failed)
Errors while running CTest

···

------
Pedro Vicente, Earth System Science
University of California, Irvine
http://www.ess.uci.edu/

  ----- Original Message -----
  From: Ward Fisher
  To: netcdfgroup@unidata.ucar.edu
  Sent: Monday, April 22, 2013 11:40 AM
  Subject: Re: [netcdfgroup] [Hdf-forum] netCDF 4.3 Release Candidateavailable --- CMake build in Windows

  Good afternoon John,

  Currently, using find_package(HDF5 NO_MODULE) results in Visual Studio attempting to link against the shared libraries (.dll) themselves, instead of the associated import libraries (.lib). I'm still trying to figure out why this is, exactly, but in the mean time I am using the work-around mentioned in your previous email.

  As of now there are no 'known' failures, assuming you are linking against the release libraries; all tests are passing in my development environment. When linking against the debug libraries, there are a number of known failures, many of which relate to how memory is managed between the hdf5 and netcdf shared libraries (a fix has been discussed with a member of the hdf team for these).

  Can you provide any further information regarding the failures you're seeing? Ideally, this should work everywhere and not just in most development environments.

  Thanks, have a great afternoon,

  -Ward
  wfisher@unidata.ucar.edu

  On 4/21/13 3:53 AM, Biddiscombe, John A. wrote:

    Just a follow up, it turns out my code was linking to debug libraries for hdf, but release for hdf5_hl, I hadn't removed all the necessary hdf5 link crud, once that was fixed, tests are almost complete. Just 3 fails, which I'll look at later.

    JB

    c:\cmakebuild\netcdf-4.3>"c:\Program Files\cmake-2.8.10.1-win32-x86\bin\ctest.exe" -C Debug

    Test project C:/cmakebuild/netcdf-4.3

            Start 1: ncdump_ctest

      1/106 Test #1: ncdump_ctest ..................... Passed 0.18 sec

            Start 2: ncdump_ctest64

      2/106 Test #2: ncdump_ctest64 ................... Passed 0.02 sec

            Start 3: ncdump_tst_utf8

      3/106 Test #3: ncdump_tst_utf8 .................. Passed 0.02 sec

            Start 4: ncdump_tst_create_files

      4/106 Test #4: ncdump_tst_create_files .......... Passed 0.03 sec

            Start 5: ncdump_tst_group_data

      5/106 Test #5: ncdump_tst_group_data ............ Passed 0.11 sec

            Start 6: ncdump_tst_enum_data

      6/106 Test #6: ncdump_tst_enum_data ............. Passed 0.04 sec

            Start 7: ncdump_tst_opaque_data

      7/106 Test #7: ncdump_tst_opaque_data ........... Passed 0.03 sec

            Start 8: ncdump_tst_string_data

      8/106 Test #8: ncdump_tst_string_data ........... Passed 0.03 sec

            Start 9: ncdump_tst_vlen_data

      9/106 Test #9: ncdump_tst_vlen_data ............. Passed 0.04 sec

            Start 10: ncdump_tst_comp

    10/106 Test #10: ncdump_tst_comp .................. Passed 0.08 sec

            Start 11: ncdump_tst_comp2

    11/106 Test #11: ncdump_tst_comp2 ................. Passed 0.04 sec

            Start 12: ncdump_tst_nans

    12/106 Test #12: ncdump_tst_nans .................. Passed 0.02 sec

            Start 13: ncdump_tst_unicode

    13/106 Test #13: ncdump_tst_unicode ............... Passed 0.03 sec

            Start 14: nctest

    14/106 Test #14: nctest ........................... Passed 1.70 sec

            Start 15: tst_rename

    15/106 Test #15: tst_rename ....................... Passed 0.03 sec

            Start 16: nc_test_t_nc

    16/106 Test #16: nc_test_t_nc ..................... Passed 0.03 sec

            Start 17: nc_test_tst_small

    17/106 Test #17: nc_test_tst_small ................ Passed 2.03 sec

            Start 18: nc_test_tst_misc

    18/106 Test #18: nc_test_tst_misc ................. Passed 0.06 sec

            Start 19: nc_test_tst_norm

    19/106 Test #19: nc_test_tst_norm ................. Passed 0.02 sec

            Start 20: nc_test_tst_names

    20/106 Test #20: nc_test_tst_names ................ Passed 0.16 sec

            Start 21: nc_test_tst_nofill

    21/106 Test #21: nc_test_tst_nofill ............... Passed 0.24 sec

            Start 22: nc_test_tst_nofill2

    22/106 Test #22: nc_test_tst_nofill2 .............. Passed 0.09 sec

            Start 23: nc_test_tst_nofill3

    23/106 Test #23: nc_test_tst_nofill3 .............. Passed 0.07 sec

            Start 24: nc_test_tst_atts

    24/106 Test #24: nc_test_tst_atts ................. Passed 0.04 sec

            Start 25: nc_test

    25/106 Test #25: nc_test .......................... Passed 43.26 sec

            Start 26: nc_test4_tst_dims

    26/106 Test #26: nc_test4_tst_dims ................ Passed 0.20 sec

            Start 27: nc_test4_tst_dims2

    27/106 Test #27: nc_test4_tst_dims2 ............... Passed 4.89 sec

            Start 28: nc_test4_tst_dims3

    28/106 Test #28: nc_test4_tst_dims3 ............... Passed 0.25 sec

            Start 29: nc_test4_tst_files

    29/106 Test #29: nc_test4_tst_files ............... Passed 0.44 sec

            Start 30: nc_test4_tst_files4

    30/106 Test #30: nc_test4_tst_files4 .............. Passed 0.06 sec

            Start 31: nc_test4_tst_vars

    31/106 Test #31: nc_test4_tst_vars ................***Failed 45.60 sec

            Start 32: nc_test4_tst_varms

    32/106 Test #32: nc_test4_tst_varms ............... Passed 0.05 sec

            Start 33: nc_test4_tst_unlim_vars

    33/106 Test #33: nc_test4_tst_unlim_vars .......... Passed 0.07 sec

            Start 34: nc_test4_tst_converts

    34/106 Test #34: nc_test4_tst_converts ............ Passed 0.05 sec

            Start 35: nc_test4_tst_converts2

    35/106 Test #35: nc_test4_tst_converts2 ...........***Failed 1.39 sec

            Start 36: nc_test4_tst_grps

    36/106 Test #36: nc_test4_tst_grps ................ Passed 0.21 sec

            Start 37: nc_test4_tst_grps2

    37/106 Test #37: nc_test4_tst_grps2 ............... Passed 0.14 sec

            Start 38: nc_test4_tst_compounds

    38/106 Test #38: nc_test4_tst_compounds ........... Passed 0.12 sec

            Start 39: nc_test4_tst_compounds2

    39/106 Test #39: nc_test4_tst_compounds2 .......... Passed 0.04 sec

            Start 40: nc_test4_tst_compounds3

    40/106 Test #40: nc_test4_tst_compounds3 .......... Passed 0.04 sec

            Start 41: nc_test4_tst_opaques

    41/106 Test #41: nc_test4_tst_opaques ............. Passed 0.05 sec

            Start 42: nc_test4_tst_strings

    42/106 Test #42: nc_test4_tst_strings ............. Passed 0.16 sec

            Start 43: nc_test4_tst_strings2

    43/106 Test #43: nc_test4_tst_strings2 ............ Passed 0.03 sec

            Start 44: nc_test4_tst_interops

    44/106 Test #44: nc_test4_tst_interops ............ Passed 0.09 sec

            Start 45: nc_test4_tst_interops4

    45/106 Test #45: nc_test4_tst_interops4 ........... Passed 0.40 sec

            Start 46: nc_test4_tst_interops6

    46/106 Test #46: nc_test4_tst_interops6 ........... Passed 0.06 sec

            Start 47: nc_test4_tst_enums

    47/106 Test #47: nc_test4_tst_enums ............... Passed 0.07 sec

            Start 48: nc_test4_tst_coords

    48/106 Test #48: nc_test4_tst_coords .............. Passed 0.33 sec

            Start 49: nc_test4_tst_coords2

    49/106 Test #49: nc_test4_tst_coords2 ............. Passed 0.16 sec

            Start 50: nc_test4_tst_coords3

    50/106 Test #50: nc_test4_tst_coords3 ............. Passed 0.23 sec

            Start 51: nc_test4_tst_vars3

    51/106 Test #51: nc_test4_tst_vars3 ............... Passed 1.25 sec

            Start 52: nc_test4_tst_vars4

    52/106 Test #52: nc_test4_tst_vars4 ............... Passed 0.03 sec

            Start 53: nc_test4_tst_chunks

    53/106 Test #53: nc_test4_tst_chunks .............. Passed 0.41 sec

            Start 54: nc_test4_tst_chunks2

    54/106 Test #54: nc_test4_tst_chunks2 ............. Passed 1.37 sec

            Start 55: nc_test4_tst_utf8

    55/106 Test #55: nc_test4_tst_utf8 ................ Passed 0.05 sec

            Start 56: nc_test4_tst_fills

    56/106 Test #56: nc_test4_tst_fills ............... Passed 0.14 sec

            Start 57: nc_test4_tst_fills2

    57/106 Test #57: nc_test4_tst_fills2 .............. Passed 0.07 sec

            Start 58: nc_test4_tst_fillbug

    58/106 Test #58: nc_test4_tst_fillbug ............. Passed 0.04 sec

            Start 59: nc_test4_tst_xplatform

    59/106 Test #59: nc_test4_tst_xplatform ........... Passed 0.04 sec

            Start 60: nc_test4_tst_xplatform2

    60/106 Test #60: nc_test4_tst_xplatform2 .......... Passed 0.04 sec

            Start 61: nc_test4_tst_h_atts2

    61/106 Test #61: nc_test4_tst_h_atts2 ............. Passed 0.02 sec

            Start 62: nc_test4_tst_endian_fill

    62/106 Test #62: nc_test4_tst_endian_fill ......... Passed 0.04 sec

            Start 63: nc_test4_tst_atts

    63/106 Test #63: nc_test4_tst_atts ................ Passed 0.05 sec

            Start 64: nc_test4_t_type

    64/106 Test #64: nc_test4_t_type .................. Passed 0.02 sec

            Start 65: nc_test4_cdm_sea_soundings

    65/106 Test #65: nc_test4_cdm_sea_soundings ....... Passed 0.03 sec

            Start 66: nc_test4_tst_vl

    66/106 Test #66: nc_test4_tst_vl .................. Passed 0.06 sec

            Start 67: nc_test4_tst_atts1

    67/106 Test #67: nc_test4_tst_atts1 ............... Passed 0.17 sec

            Start 68: nc_test4_tst_atts2

    68/106 Test #68: nc_test4_tst_atts2 ............... Passed 0.06 sec

            Start 69: nc_test4_tst_vars2

    69/106 Test #69: nc_test4_tst_vars2 ............... Passed 0.35 sec

            Start 70: nc_test4_tst_files5

    70/106 Test #70: nc_test4_tst_files5 .............. Passed 0.03 sec

            Start 71: nc_test4_tst_files6

    71/106 Test #71: nc_test4_tst_files6 .............. Passed 0.03 sec

            Start 72: nc_test4_tst_sync

    72/106 Test #72: nc_test4_tst_sync ................ Passed 0.09 sec

            Start 73: nc_test4_tst_h_strbug

    73/106 Test #73: nc_test4_tst_h_strbug ............ Passed 0.10 sec

            Start 74: nc_test4_tst_h_refs

    74/106 Test #74: nc_test4_tst_h_refs .............. Passed 13.39 sec

            Start 75: tst_h_files

    75/106 Test #75: tst_h_files ...................... Passed 1.56 sec

            Start 76: tst_h_files2

    76/106 Test #76: tst_h_files2 ..................... Passed 0.32 sec

            Start 77: tst_h_files4

    77/106 Test #77: tst_h_files4 ..................... Passed 0.11 sec

            Start 78: tst_h_atts

    78/106 Test #78: tst_h_atts ....................... Passed 2.72 sec

            Start 79: tst_h_atts3

    79/106 Test #79: tst_h_atts3 ...................... Passed 0.09 sec

            Start 80: tst_h_atts4

    80/106 Test #80: tst_h_atts4 ...................... Passed 0.08 sec

            Start 81: tst_h_vars

    81/106 Test #81: tst_h_vars .......................***Failed 2.33 sec

            Start 82: tst_h_vars2

    82/106 Test #82: tst_h_vars2 ...................... Passed 2.96 sec

            Start 83: tst_h_vars3

    83/106 Test #83: tst_h_vars3 ...................... Passed 0.26 sec

            Start 84: tst_h_grps

    84/106 Test #84: tst_h_grps ....................... Passed 0.16 sec

            Start 85: tst_h_compounds

    85/106 Test #85: tst_h_compounds .................. Passed 0.27 sec

            Start 86: tst_h_compounds2

    86/106 Test #86: tst_h_compounds2 ................. Passed 0.05 sec

            Start 87: tst_h_wrt_cmp

    87/106 Test #87: tst_h_wrt_cmp .................... Passed 0.05 sec

            Start 88: tst_h_rd_cmp

    88/106 Test #88: tst_h_rd_cmp ..................... Passed 0.19 sec

            Start 89: tst_h_vl

    89/106 Test #89: tst_h_vl ......................... Passed 0.19 sec

            Start 90: tst_h_opaques

    90/106 Test #90: tst_h_opaques .................... Passed 0.06 sec

            Start 91: tst_h_strings

    91/106 Test #91: tst_h_strings .................... Passed 0.10 sec

            Start 92: tst_h_strings1

    92/106 Test #92: tst_h_strings1 ................... Passed 0.16 sec

            Start 93: tst_h_strings2

    93/106 Test #93: tst_h_strings2 ................... Passed 0.08 sec

            Start 94: tst_h_ints

    94/106 Test #94: tst_h_ints ....................... Passed 0.10 sec

            Start 95: tst_h_dimscales

    95/106 Test #95: tst_h_dimscales .................. Passed 0.74 sec

            Start 96: tst_h_dimscales1

    96/106 Test #96: tst_h_dimscales1 ................. Passed 0.09 sec

            Start 97: tst_h_dimscales2

    97/106 Test #97: tst_h_dimscales2 ................. Passed 0.19 sec

            Start 98: tst_h_dimscales3

    98/106 Test #98: tst_h_dimscales3 ................. Passed 0.06 sec

            Start 99: tst_h_enums

    99/106 Test #99: tst_h_enums ...................... Passed 0.09 sec

            Start 100: tst_h_dimscales4

    100/106 Test #100: tst_h_dimscales4 ................. Passed 0.14 sec

            Start 101: C_tests_simple_xy_wr

    101/106 Test #101: C_tests_simple_xy_wr ............. Passed 0.17 sec

            Start 102: C_tests_simple_xy_rd

    102/106 Test #102: C_tests_simple_xy_rd ............. Passed 0.07 sec

            Start 103: C_tests_sfc_pres_temp_wr

    103/106 Test #103: C_tests_sfc_pres_temp_wr ......... Passed 0.04 sec

            Start 104: C_tests_sfc_pres_temp_rd

    104/106 Test #104: C_tests_sfc_pres_temp_rd ......... Passed 0.08 sec

            Start 105: C_tests_pres_temp_4D_wr

    105/106 Test #105: C_tests_pres_temp_4D_wr .......... Passed 0.07 sec

            Start 106: C_tests_pres_temp_4D_rd

    106/106 Test #106: C_tests_pres_temp_4D_rd .......... Passed 0.07 sec

    97% tests passed, 3 tests failed out of 106

    Total Test time (real) = 136.75 sec

    The following tests FAILED:

             31 - nc_test4_tst_vars (Failed)

             35 - nc_test4_tst_converts2 (Failed)

             81 - tst_h_vars (Failed)

    Errors while running CTest

_______________________________________________
netcdfgroup mailing list
netcdfgroup@unidata.ucar.edu
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/

------------------------------------------------------------------------------

  _______________________________________________
  netcdfgroup mailing list
  netcdfgroup@unidata.ucar.edu
  For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/