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

[netCDF #VAZ-231246]: Netcdf



Dave,

> Thanks.  But I keep getting tripped up on the things that should be
> "simple".  How do I download the whole directory structure of files that
> I need from http://svn.unidata.ucar.edu/repos/netcdf/trunk/ and how do I
> make sure I get all the files in the right place.

Oops, sorry, I should have explained about access to svn (Subversion) 
repositories. Subversion is probably the most widely used version control
system for open source software, though git may have passed it recently.

There are several freely available svn clients for checking out code trees 
from an svn repository for building on a local system.  TortoiseSVN

  http://tortoisesvn.tigris.org/

is one of the more popular Windows clients, and others are compared in 
this summary:

  http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients

> I downloaded the files in
> http://svn.unidata.ucar.edu/repos/netcdf/trunk/win32/NET/ (tediously one
> at a time) and tried to use the .sln file but the first error I received
> was Cannot open source file: '..\..\..\nf_test\fortlib.c': No such file
> or directory
> 
> I do not see any nf_test folder in
> http://svn.unidata.ucar.edu/repos/netcdf/trunk/

That's our problem, thanks for reporting it.  I'm guilty of not independently
checking this 23 November report on the status of the win32 sources in the 
current development snapshot:

  ... The windows port is checked into the trunk. I believe it will build and 
  test right now, but you'll just have to check and see. The solution file is 
  in the win32/NET directory.

I don't have a platform on which to check this, but it appears that the
Fortran dependencies have not been moved from the win32 sources, as they
were from the rest of the netCDF-C distribution, when we created a separate
netCDF-Fortran distribution a few months ago.

The solution may be as simple as removing references to the nf_test 
directory and any other Fortran directories you run across (fortran and f90,
for example).

As you may know, we're currently trying to recruit a developer with Windows
skills to clean up the netCDF port and provide a clean build with Visual
Studio compilers and development tools ...

--Russ

> On 12/19/2011 5:23 AM, Unidata netCDF Support wrote:
> > Hi David
> >
> >> What is the link to get the intermediate files you were suggesting I
> >> should get to try get a PC version of NetCDF going.
> > The latest C code for Windows is accessible from
> >
> >    http://svn.unidata.ucar.edu/repos/netcdf/trunk/
> >
> > in the win32/NET/ directory.
> >
> > In particular, that directory contains a Visual Studio solutions fil,
> > netcdf.sln, as well as some other Unix system files ported to Windows:
> >
> >    Makefile.am
> >    config.h
> >    examples/
> >    getopt.c
> >    inttypes.h
> >    libsrc/
> >    nc_test/
> >    ncdump/
> >    ncgen/
> >    nctest/
> >    netcdf.sln
> >    netcdff/
> >    stdint.h
> >
> > I hope this helps ...
> >
> > --Russ
> >
> > Russ Rew                                         UCAR Unidata Program
> > address@hidden                      http://www.unidata.ucar.edu
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: VAZ-231246
> > Department: Support netCDF
> > Priority: Normal
> > Status: Closed
> >
> > .
> >
> 
> 

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



Ticket Details
===================
Ticket ID: VAZ-231246
Department: Support netCDF
Priority: Normal
Status: Closed