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

[netCDF #MBZ-999089]: a better windows build

Hi Paul,

> our team of developers have put some solid time into improving the build
> process of NetCDF for windows (we are a windows shop).  We now have an
> easy build process for Visual Studio 2010, which includes making
> wrappers for c# and VBA (Excel)  How would we go about submitting this
> back to the community?

Thanks for the generous offer to make the results of your work available for
the netCDF community!  We get a lot of questions about building netCDF with
Visual Studio 2010, and we currently can't provide much support for that 
platform due to lack of resources and expertise.

Which version of netCDF have you ported?  We have a similar port of 4.1.1
contributed by Viet Eitner that we were unable to maintain through a major
refactor of the library code, as explained in our FAQ on building for 


but if you managed to port a more recent version, I'd like to add information
about how to get it to that FAQ document.  If you can't host the necessary
documents, file patches, or new sources, we could offer a subdirectory of our
"contrib/" directory, with the understanding that we couldn't support or 
the contents of that directory.

If you can host the documents and files for porting netCDF to Windows Visual
Studio, then I would suggest an announcement of what you've done and its
availability on the address@hidden mailing list.

On behalf of the netCDF user and developer communities, thanks again for 
to make this available.


Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: MBZ-999089
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.