<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.9600.18057">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Chris</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Thanks for the suggestion</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>We added this feature. To build:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Get source and switch to release
branch:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>git clone <A
href="https://github.com/pedro-vicente/netcdf-explorer.git">https://github.com/pedro-vicente/netcdf-explorer.git</A><BR>git
checkout release</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Build with:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>./configure<BR>make</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>The logic for this behaviour is:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>1) Have a master branch with only the upstream
files. <BR>Upstream files are files used to auto-generate other files. <BR>These
are the files that we write and commit often,<BR>so it's important to focus on
them, for example to see the differences in the web interface of
git.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>2) The release branch has all the extra user-ready
to compile files, generated by autoreconf.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>----------------------<BR>Pedro Vicente<BR><A
href="mailto:pedro.vicente@space-research.org">pedro.vicente@space-research.org</A><BR><A
href="http://www.space-research.org/">http://www.space-research.org/</A></FONT></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=chris.barker@noaa.gov href="mailto:chris.barker@noaa.gov">Chris
Barker</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=pedro.vicente@space-research.org
href="mailto:pedro.vicente@space-research.org">Pedro Vicente</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=netcdfgroup@unidata.ucar.edu
href="mailto:netcdfgroup@unidata.ucar.edu">netcdfgroup@unidata.ucar.edu</A> ;
<A title=hdf-forum@lists.hdfgroup.org
href="mailto:hdf-forum@lists.hdfgroup.org">hdf-forum@lists.hdfgroup.org</A> ;
<A title=nexus@nexusformat.org
href="mailto:nexus@nexusformat.org">nexus@nexusformat.org</A> ; <A
title=cf-metadata@cgd.ucar.edu
href="mailto:cf-metadata@cgd.ucar.edu">cf-metadata@cgd.ucar.edu</A> ; <A
title=orion@cora.nwra.com href="mailto:orion@cora.nwra.com">Orion
Poplawski</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, November 09, 2015 1:33
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [CF-metadata] [netcdfgroup]
Introducing netCDF Explorer</DIV>
<DIV><BR></DIV>
<DIV dir=ltr>getting kind of off topic, but...<BR>
<DIV class=gmail_extra><BR>
<DIV class=gmail_quote>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Build
with:<BR><BR>autoreconf -vfi<BR>./configure<BR>make<BR><BR>For
Mac:<BR><BR>Mac does not include GNU Autoconf<BR></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>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:</DIV>
<DIV><BR></DIV>
<DIV>./configure</DIV>
<DIV><BR></DIV>
<DIV>It's be great is you could do this for this project.</DIV>
<DIV><BR></DIV>
<DIV>-CHB</DIV>
<DIV> </DIV>
<DIV><BR></DIV></DIV>-- <BR>
<DIV class=gmail_signature><BR>Christopher Barker,
Ph.D.<BR>Oceanographer<BR><BR>Emergency Response Division<BR>NOAA/NOS/OR&R
(206) 526-6959
voice<BR>7600 Sand Point Way NE (206) 526-6329
fax<BR>Seattle, WA 98115 (206)
526-6317 main reception<BR><BR><A
href="mailto:Chris.Barker@noaa.gov"
target=_blank>Chris.Barker@noaa.gov</A></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTML>