[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #LCN-240709]: RE: Fwd: RE: unidata summer workshops



> Hi Russ,
> 
> This was very helpful and I've made some progress now that I have CMake 
> supported version.  In the configuration step from the CMake GUI I'm getting 
> the following error that I'm hopeful you can help me resolve.
> 
> 
> 
> Thanks again for all your help,
> 
> Tim
> 
> 
> 
> The C compiler identification is MSVC 17.0.50727.1
> 
> Check for working C compiler using: Visual Studio 11
> 
> Check for working C compiler using: Visual Studio 11 -- works
> 
> Detecting C compiler ABI info
> 
> Detecting C compiler ABI info - done
> 
> Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)

The failure to find pkg-config.exe on Windows is not a fatal error; the build 
should continue. 

> HDF5_LIB-NOTFOUND, HDF5_HL_LIB-NOTFOUND, HDF5_INCLUDE_DIR-NOTFOUND
> 
> Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)

Here's an answer to a similar question from Ward Fisher, posted to the 
netcdfgroup mailing list:

  
http://www.unidata.ucar.edu/mailing_lists/archives/netcdfgroup/2013/msg00161.html

--Russ


> 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 
> C:/Users/twhawk/Documents/downloaded_programs/netcdf-4.3.0-rc3
> 
> used as include directory in directory 
> C:/Users/twhawk/Documents/downloaded_programs/netcdf-4.3.0-rc3
> 
> used as include directory in directory 
> C:/Users/twhawk/Documents/downloaded_programs/netcdf-4.3.0-rc3
> 
> used as include directory in directory 
> C:/Users/twhawk/Documents/downloaded_programs/netcdf-4.3.0-rc3
> 
> 
> 
> **********************************************
> 
> Timothy W. Hawkins
> 
> Professor and Graduate Program Coordinator
> 
> Department of Geography and Earth Science
> 
> Shippensburg University
> 
> 1871 Old Main Drive
> 
> Shippensburg, PA 17257
> 
> 
> 
> Email: address@hidden
> 
> Phone: (717) 477-1662
> 
> Fax: (717) 477-4029
> 
> Web: http://www.ship.edu/geo-ess/
> 
> 
> 
> -----Original Message-----
> From: Unidata netCDF Support [mailto:address@hidden
> Sent: Tuesday, March 19, 2013 11:24 AM
> To: Hawkins, Timothy (Tim)
> Cc: address@hidden
> Subject: [netCDF #LCN-240709]: RE: Fwd: RE: unidata summer workshops
> 
> 
> 
> Hi Tim,
> 
> 
> 
> > I've been fiddling with trying to install netCDF on windows using CMake as 
> > suggested in the link you sent me from last summer's workshop.  I've pasted 
> > the CMake error below but it looks like I'm missing or am not properly 
> > pointing to the directory that contains the "CMakeLists.txt" file.  Is this 
> > file a separate download? Is it included in my download of netCDF from 
> > unidata?  Should I be pointing to a subdirectory?  Any help is appreciated.
> 
> > CMake Error: The source directory 
> > "C:/Users/twhawk/Documents/downloaded_programs/netcdf-4.2.1.1" does not 
> > appear to contain CMakeLists.txt.
> 
> 
> 
> The netCDF version 4.2.1.1 release from last summer didn't contain the CMake 
> solution for building on Windows, which was only available at the time from a 
> separate web page with instructions for installing binary releases built from 
> CMake:
> 
> 
> 
> http://www.unidata.ucar.edu/software/netcdf/CompileCMake.html
> 
> 
> 
> However, the CMake support for building the netCDF C library on Windows has 
> now been integrated into a release candidate, netCDF-4.3-rc3, available from:
> 
> 
> 
> http://www.unidata.ucar.edu/downloads/netcdf/netcdf-rc
> 
> 
> 
> with instructions for building here:
> 
> 
> 
> http://www.unidata.ucar.edu/software/netcdf/docs_rc/winbin.html
> 
> 
> 
> I hope that helps ...
> 
> 
> 
> --Russ
> 
> 
> 
> > -----Original Message-----
> 
> > From: Russ Rew [mailto:address@hidden
> 
> > Sent: Wednesday, February 20, 2013 4:13 PM
> 
> > To: support-netcdf
> 
> > Cc: address@hidden<mailto:address@hidden>
> 
> > Subject: Re: Fwd: RE: unidata summer workshops
> 
> >
> 
> >
> 
> >
> 
> > Hi Tim,
> 
> >
> 
> >
> 
> >
> 
> > > ... Is there a crash course way I can learn netCDF.
> 
> >
> 
> > > I'm interested in using readily available netCDF files in my own
> 
> >
> 
> > > research and teaching but don't really have any experience with the
> 
> >
> 
> > > format.  I've fiddled around with netCDF files a bit but I was
> 
> > > hoping
> 
> >
> 
> > > for a user's course.
> 
> >
> 
> >
> 
> >
> 
> > Yes, I'd recommend at least the first day's worth of material from last 
> > year's netCDF workshop:
> 
> >
> 
> >
> 
> >
> 
> > http://www.unidata.ucar.edu/netcdf/workshops/2012/
> 
> >
> 
> >
> 
> >
> 
> > That would be the first 20 sessions, and it's OK to skip around, as some of 
> > the subjects are independent of earlier material, but session 3, 5, 6, 7, 
> > and 9 are pretty basic.  Most of the material is short HTML pages and you 
> > can just use the icons in the upper or lower left of each page to navigate 
> > through the material, but some of the pages just link to PowerPoint 
> > presentations.
> 
> >
> 
> >
> 
> >
> 
> > --Russ
> 
> >
> 
> >
> 
> Russ Rew                                         UCAR Unidata Program
> 
> address@hidden<mailto:address@hidden>                      
> http://www.unidata.ucar.edu
> 
> 
> 
> 
> 
> 
> 
> Ticket Details
> 
> ===================
> 
> Ticket ID: LCN-240709
> 
> Department: Support netCDF
> 
> Priority: Normal
> 
> Status: Closed
> 
> 
> 
Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: LCN-240709
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.