Very Cool John! I have been having the same thoughts about doing an upgrade of that library for a while now, but never getting to it. Once this does make it in we can upgrade netcdf as well! :-)<div><br></div><div>When your changes get in I can most definitely help you with install rules issues etc.<br>
<br><div class="gmail_quote">On Thu, Mar 18, 2010 at 12:19 PM, Berk Geveci <span dir="ltr"><<a href="mailto:berk.geveci@kitware.com" target="_blank">berk.geveci@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I vote for (2). I also vote for waiting until after we branch 3.8 and<br>
after we switch to Git (which will follow the 3.8 branch by a week or<br>
two). In all, it will probably be around 4 weeks before we switch to<br>
Git.<br>
<br>
-berk<br>
<div><div></div><div><br>
On Thu, Mar 18, 2010 at 12:14 PM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch" target="_blank">biddisco@cscs.ch</a>> wrote:<br>
> As some of you may know, I’ve been helping towards cmakeifying hdf5 1.8.x ,<br>
> and I have a stable version working inside paraview – and it has been ok for<br>
> some time.<br>
><br>
><br>
><br>
> I’d like to check this into paraview/Utilities under hdf-1.8 and I’ll make<br>
> sure any compile issues are tidied up.<br>
><br>
><br>
><br>
> All the relevant filters which make use of HDF5 are compiling ok and as far<br>
> as I know the tests are fine. Will rerun later a full suite as I did some<br>
> cmake tweaking today.<br>
><br>
><br>
><br>
> I’m keen to have 1.8.x support in the next paraview release as I think it’s<br>
> important for plugins like H5Part which are out of date (and I wish to<br>
> update at the same time), and other ones we are developing (Xdmf stuff etc).<br>
><br>
><br>
><br>
> Possibility 1)<br>
><br>
> Check in the new /hdf5-1.8 directory, leave the old /hdf5 (1.6) one where it<br>
> is but switch all builds to use 1.8.x by default. Breakages will be reported<br>
> quite quickly as any affected dashboards will start emailing me instantly<br>
> and users will vent their spleens too.<br>
><br>
> 2) Remove the old hdf5 completely when I check in the new (my preferred<br>
> option)<br>
><br>
> 3) Leave both, leave the default as 1.6, but allow user to switch to 1.8 if<br>
> they want. Extra Cmake maintenance required. option 1 assumes code is left<br>
> in place, but cmake uses new version.<br>
><br>
><br>
><br>
> NB. Install rules for hdf5 on its own are good, but I’m not so confident on<br>
> a make install on paraview to see if it installs the sub items well. Might<br>
> need a spot of help from a kitware boffin here.<br>
><br>
><br>
><br>
> All being well, I’d like to get this in within a few weeks please. I asked a<br>
> few months ago about this and nobody objected much (Ken voiced concerns over<br>
> compatibility). If you wish to comment – please do.<br>
><br>
><br>
><br>
> JB<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
> John Biddiscombe, email:biddisco @ <a href="http://cscs.ch" target="_blank">cscs.ch</a><br>
><br>
> <a href="http://www.cscs.ch/" target="_blank">http://www.cscs.ch/</a><br>
><br>
> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07<br>
><br>
> Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82<br>
><br>
><br>
><br>
</div></div>> _______________________________________________<br>
> Paraview-developers mailing list<br>
> <a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
><br>
><br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></div><br></div>