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.
> > There is an incredible amount of stuff in the tar.gz file. Yes, there sure is! > > I have copied the libsrc files into the cxx folder and almost have a working compilation, basked on the 'hand made' info at the top of makefile. > Umm, why are you doing this? > What is the minimum files needed to build a working C++ interface? Do I need .deps? How do I configure config.h? Do I need the .m4 files? > > Simply put: on a deserted island with one floppy disc, what would I need? > Can you tell me why you are doing this? It is not that good an idea. If you have a system that is really too small to handled the full distribution, that is a surprise to me. Why not just run the configure script and build netCDF normally? Thanks, Ed Ticket Details =================== Ticket ID: SEZ-677429 Department: Support netCDF Priority: Normal Status: Closed