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

[netCDF #NFG-783720]: Question regarding using the CMake utility to make the Visual Studio project file for NetCDF3

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [netCDF #NFG-783720]: Question regarding using the CMake utility to make the Visual Studio project file for NetCDF3
  • Date: Tue, 18 Jul 2017 14:53:50 -0600
Hello Andy,

NetCDF 3 is enabled by default all of the time; there's no way to turn it off.  
NetCDF4 refers to the enhanced file format/data model, and not the 'latest 
version', so to speak.  

That said, you can turn off netCDF4 support and netCDF3 will be implied, as 
will netCDF2 and netCDF1!

I hope this helps,

-Ward

> Hi,
> 
> I would like to use the CMake utility to produce the Visual Studio project
> files in order to build NetCDF with version 3, rather than version 4.
> 
> In the CMake configuration window, I have the option of enabling NetCDF 4
> (ENABLE_NETCDF_4), but not for enabling NetCDF 3. How do I use the CMake
> utility for producing a Visual Studio project file for building NetCDF
> with version 3 using Visual Studio?
> 
> Many thanks,
> 
> Andy
> 
> Oxford e-Research Centre
> University of Oxford
> 7 Keble Road, Oxford, OX1 3QG
> 
> www.oerc.ox.ac.uk
> 
> 


Ticket Details
===================
Ticket ID: NFG-783720
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.