Hello Ellen, When building on Windows with CMake for Visual Studio, I run into the same issue if I do not put 'netcdf.dll' in a directory which is on the system path. I suspect that the same thing is happening here. On my development system, I will perform the following steps when I want to run the netcdf tests: 1. Configure netCDF for use with MSVC via cmake. 2. Build the 'netcdf' target, e.g. c:\netcdf-build> cmake --build . --config Release --target netcdf 3. Copy the resultant netcdf.dll into C:\Windows\System Note that this is probably not the best practice; I do this on my dev environment, and it may be ok for your purposes, but if it's not, you'll need to edit your system path variable to include the directory where you want netcdf.dll to reside. 4. Run the tests via cmake, e.g. c:\netcdf-build> cmake --build . --config Release --target RUN_TESTS I'm sure these same steps can be accomplished within the Visual Studio GUI, but I typically invoke them from the command line. Also, please note that if you build the 'Debug' build, you receive a variety of warnings related to how netcdf and hdf5 manage memory between the two libraries. These warnings are harmless and may be ignored, but they are also intrusive and will interrupt each test, requiring you to select 'continue' from a modal dialog each time. I hope this helps; please let me know if it doesn't resolve the problem, or if you encounter any other issues! Have a great day, -Ward > Hello, > > I'm trying to build NetCDF 126.96.36.199 on Windows 64 using cmake and Visual > Studio 2011, and am running into a strange problem where the build > succeeds but most of the tests fail. > > I'm running the tests by building the project RUN_TESTS in Visual Studio. > > Only 6 tests pass - nc_test_tst_meta, nc_test4_tst_h_atts2, > tst_h_atts3,tst_h_atts4, ncdap_tst_remote3, ncdap_testurl. > > The rest either say "Failed", or "Exception: Other" -- I've included a > small snippet of the output below. > > I'm thinking there must be a lib/dll issue somewhere, perhaps I haven't > linked to a necessary library. > > Do you have any suggestions? Do the tests that pass give any hint as > to what is going wrong? > > Thank you! > ellen > > Copyright (C) Microsoft Corp. All rights reserved. > 2769 1>------ Build started: Project: RUN_TESTS, Configuration: Release x64 > ------ > 2770 1>Build started 3/17/2015 2:57:25 PM. > 2771 1>InitializeBuildStatus: > 2772 1> Creating "x64\Release\RUN_TESTS\RUN_TESTS.unsuccessfulbuild" because > "AlwaysCreate" was specified. > 2773 1>PostBuildEvent: > 2774 1> Test project F:/sandbox/ellenj/3p-tmw/3p/derived/win64/netcdf/build > 2775 1> Start 1: ncgen_run_tests > 2776 1> 1/143 Test #1: ncgen_run_tests ..................***Failed > 0.16 sec > 2777 1> Start 2: ncgen_run_nc4_tests > 2778 1> 2/143 Test #2: ncgen_run_nc4_tests ..............***Failed > 0.34 sec > 2779 1> Start 3: ncgen3_run_tests > 2780 1> 3/143 Test #3: ncgen3_run_tests .................***Failed > 0.21 sec > 2781 1> Start 4: ncgen3_run_nc4_tests > 2782 1> 4/143 Test #4: ncgen3_run_nc4_tests .............***Failed > 0.31 sec > 2783 1> Start 5: ncdump_run_tests > 2784 1> 5/143 Test #5: ncdump_run_tests .................***Failed > 0.19 sec > 2785 1> Start 6: ncdump_tst_64bit > 2786 1> 6/143 Test #6: ncdump_tst_64bit .................***Failed > 0.13 sec > 2787 1> Start 7: ncdump_ctest > 2788 1> 7/143 Test #7: ncdump_ctest .....................***Exception: > Other 0.06 sec > 2789 1> Start 8: ncdump_ctest64 > 2790 1> 8/143 Test #8: ncdump_ctest64 ...................***Exception: > Other 0.06 sec > > Ticket Details =================== Ticket ID: BXA-758661 Department: Support netCDF Priority: Normal Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.