That sounds fine. Thanks John!<br><br><div class="gmail_quote">On Tue, Jun 15, 2010 at 10:41 AM, Biddiscombe, John A. <span dir="ltr"><<a href="mailto:biddisco@cscs.ch">biddisco@cscs.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Dave,<br>
<br>
Yes <a href="http://gitorious.org/hdf5/hdf5-v18" target="_blank">http://gitorious.org/hdf5/hdf5-v18</a> is correct.<br>
<br>
I've integrated everything in, and modified all the paraviewcommon.cmake and other sub projects which link to hdf to get it right (xdmf etc)<br>
<br>
I have not ensured that PARAVIEW_USE_SYSTEM_HDF5 works. If you use the new hdf5 bundled into paraview, fine, if not, ...<br>
However, it would be nice to have a cmakeified hdf installed somewhere and use that, then there'd be no need to check out the hdf5 sub-dir at all.<br>
<br>
I don't have a clean branch with only these changes on that you can pull from. But I can put one together tonight maybe. If I create an hdf5 branch locally and send you details tomorrow, then you can pull and clean up any bits that I didn't get right - OK?<br>
<div class="im"><br>
JB<br>
<br>
<br>
<br>
> -----Original Message-----<br>
> From: Dave Partyka [mailto:<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>]<br>
</div><div class="im">> Sent: 15 June 2010 16:04<br>
> To: Biddiscombe, John A.<br>
</div><div class="im">> Cc: Utkarsh Ayachit; <a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>; Brad King<br>
> Subject: Re: [Paraview-developers] Moving to hdf5-1.8.x<br>
><br>
</div><div><div></div><div class="h5">> Hi John,<br>
><br>
> I don't mind nursing the dashboard with your merge. Actually we would like<br>
> to make hdf5 a git submodule because currently xdmf (standalone) has it's<br>
> own copy of hdf5 and another project (titan) would also like to make use of<br>
> the latest hdf5.<br>
><br>
> That said, the best approach might be that we create the submodule and in<br>
> the process cleanup the two copies we have. After that we can pull in your<br>
> changes into that submodule. Just to be certain, the version of hdf5 you are<br>
> testing with paraview is the one at <a href="http://gitorious.org/hdf5/hdf5-v18" target="_blank">http://gitorious.org/hdf5/hdf5-v18</a>?<br>
><br>
><br>
> On Tue, Jun 15, 2010 at 9:27 AM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch">biddisco@cscs.ch</a>><br>
> wrote:<br>
><br>
><br>
> Utkarsh<br>
><br>
><br>
> > updated hdf5. What are your estimates?<br>
><br>
><br>
> I can push stuff in a few minutes - as long as there is someone at<br>
> kitware to patch everything that fails that I didn't know about!<br>
><br>
> I'm away from the end of this week, for two and a half weeks (until 6<br>
> july), I figured it wasn't a good idea to push stuff before I disappeared.<br>
><br>
> I also wanted to setup an 'official' git clone of the hdfgroup svn<br>
> repo. They said good idea, but someone has to actually do it.<br>
><br>
> We have the branch named 'official' at<br>
> <a href="http://gitorious.org/hdf5/hdf5-v18" target="_blank">http://gitorious.org/hdf5/hdf5-v18</a> but it doesn't track the svn repo. I just<br>
> manually update it every few days. When hdf5 1.8.1 goes out (we missed<br>
> 1.8.0) we should simply update the git repo. in my local clone of pv, I've<br>
> added a submodule to the gitorious repo. If this is good enough, then fine,<br>
> if not, I need time to do the git/svn hdf stuff properly.<br>
><br>
><br>
> JB<br>
><br>
><br>
> _______________________________________________<br>
> Paraview-developers mailing list<br>
> <a href="mailto:Paraview-developers@paraview.org">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>
</div></div></blockquote></div><br>