[Nexus] [CF-metadata] [netcdfgroup] Introducing netCDF Explorer

[Pedro Vicente]

Chris

Thanks for the suggestion

We added this feature. To build:

Get source and switch to release branch:

git clone https://github.com/pedro-vicente/netcdf-explorer.git
git checkout release

Build with:

./configure
make

The logic for this behaviour is:

1) Have a master branch with only the upstream files. 
Upstream files are files used to auto-generate other files. 
These are the files that we write and commit often,
so it's important to focus on them, for example to see the differences in the web interface of git.

2) The release branch has all the extra user-ready to compile files, generated by autoreconf.

----------------------
Pedro Vicente
pedro.vicente at space-research.org
http://www.space-research.org/
  ----- Original Message ----- 
  From: Chris Barker 
  To: Pedro Vicente 
  Cc: netcdfgroup at unidata.ucar.edu ; hdf-forum at lists.hdfgroup.org ; nexus at nexusformat.org ; cf-metadata at cgd.ucar.edu ; Orion Poplawski 
  Sent: Monday, November 09, 2015 1:33 PM
  Subject: Re: [CF-metadata] [netcdfgroup] Introducing netCDF Explorer


  getting kind of off topic, but...



    Build with:

    autoreconf -vfi
    ./configure
    make

    For Mac:

    Mac does not include GNU Autoconf



  the usual convention is for teh developer to run autotools, and add the results to the source release, so end users can jump straight to:


  ./configure


  It's be great is you could do this for this project.


  -CHB



  -- 


  Christopher Barker, Ph.D.
  Oceanographer

  Emergency Response Division
  NOAA/NOS/OR&R            (206) 526-6959   voice
  7600 Sand Point Way NE   (206) 526-6329   fax
  Seattle, WA  98115       (206) 526-6317   main reception

  Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/pipermail/nexus/attachments/20151110/482a021f/attachment.html>