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

[netCDF #MSV-188900]: C++ API for NETCDF version 4.0

>
> > Most C++ programmes have their class declarations and definitions in
> > individual .h and .cpp. A separate .h file (hdf5.h) then "includes" all
> > the .h files  for the constituent objects. This is the case for HDF5.
> > Would you agree to me doing the same for NETCDF C++? It would make
> > things easier for me to work on! If so, please can you provide some
> > guidance about the make process. I can't see how the Make process works
> > out which .cpp to pick up, and also whether the dependencies are
> > automatically worked out  (with makedepend).
>
> Yes, please feel free to create a single .h file that includes all the other
> needed .h files so the resulting API is easier to use.  As far as guidance
> about the make process, we use autoconf, automake, and libtool, so our
> Makefiles are supposed to be generated from a Makefile.am when the configure
> script (generated by autoconf in the top-level netCDF directory) runs.  I
> don't think we use makedepend, but instead a "depcomp" script, available from
> the top-level source directory, to maintain dependencies.  It's apparently
> not perfect, because I have occasionally had to do a "make clean" after a
change
> to a header file to get everything to work that should have depended on the
> change.  For more details on the use of depcomp, I'll have to refer you to Ed
> Hartnett, who has developed the build, testing, and release systems we use.
>

Howdy!

A little more information: you should modify the Makefile.am file in the cxx4
directory. It's an automake file. Google and you will find a lot of
documentation on how automake works.

Good luck!

Ed

Ticket Details
===================
Ticket ID: MSV-188900
Department: Support netCDF
Priority: Normal
Status: Closed