<div dir="ltr"><div style>I was thinking cross compilation. Where you need boost headers in the compilation tools build and don't want to waste time building anything not strictly necessary.</div><div style><br></div><div style>
But otherwise yeah just turn on VisitBridge and that will in turn turn on boost.</div><div style><br></div><div style>Sorry for the misinformation.</div></div><div class="gmail_extra"><br clear="all"><div>David E DeMarle<br>
Kitware, Inc.<br>R&D Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div>
<br><br><div class="gmail_quote">On Thu, Aug 8, 2013 at 10:23 AM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Rick,<br>
<br>
Yea, you don't need any separate build of VisIt, by turning on<br>
ENABLE_visitbridge, ParaViewSuperbuild builds all the components<br>
needed (including parts of VisIt). BTW, you don't neeed to ensure<br>
ENABLE_boost is ON either (contrary to what Dave suggested). If<br>
ENABLE_visitbridge is ON, ParaViewSuperbuid will automatically turn on<br>
ENABLE_boost during its dependency determination pass.<br>
<br>
Utkarsh<br>
<br>
On Thu, Aug 8, 2013 at 8:13 AM, Angelini, Richard C (Rick) CIV USARMY<br>
<div class="HOEnZb"><div class="h5">ARL (US) <<a href="mailto:richard.c.angelini.civ@mail.mil">richard.c.angelini.civ@mail.mil</a>> wrote:<br>
> OK - maybe I'm taking this too literally. Does the VisIt_Bridge actually<br>
> link against the VisIt libraries? I built and compiled with the<br>
> ENABLE_visitbridge turned on and I somehow ended up with a working CGNS<br>
> reader. But at no point did I specify any paths to my VisIt installation<br>
> ..... 8-)<br>
><br>
><br>
><br>
> ________________________________<br>
> Rick Angelini<br>
><br>
> USArmy Research Laboratory<br>
> CISD/HPC Architectures Team<br>
> Building 120 Cube 315<br>
> Phone: <a href="tel:410-278-6266" value="+14102786266">410-278-6266</a><br>
> ________________________________<br>
> From: <a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a> [<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>] on<br>
> behalf of David E DeMarle [<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>]<br>
> Sent: Wednesday, August 07, 2013 4:39 PM<br>
><br>
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)<br>
> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
> Subject: Re: [Paraview] CGNS Reader<br>
><br>
> I think the only extra flag will be make sure boost is one of the projects<br>
> superbuild makes. When superbuild makes paraview it will see this and then<br>
> turn visitbridge on and link it in when it configures paraview.<br>
><br>
> Robert probably knows best the state of this particular file format.<br>
><br>
><br>
> David E DeMarle<br>
> Kitware, Inc.<br>
> R&D Engineer<br>
> 21 Corporate Drive<br>
> Clifton Park, NY 12065-8662<br>
> Phone: <a href="tel:518-881-4909" value="+15188814909">518-881-4909</a><br>
><br>
><br>
> On Wed, Aug 7, 2013 at 3:56 PM, Angelini, Richard C (Rick) CIV USARMY ARL<br>
> (US) <<a href="mailto:richard.c.angelini.civ@mail.mil">richard.c.angelini.civ@mail.mil</a>> wrote:<br>
>><br>
>> I was afraid you say that! 8-)<br>
>><br>
>> So, are there any additional parameters that need to be set, such as where<br>
>> the VisIt libraries are installed, etc? In the Superbuild, I've looked in<br>
>> the CMakeCache.txt file, and I don't see any additional parameters for the<br>
>> bridge or for cgns.<br>
>><br>
>> Is this page still current and correct?<br>
>> <a href="http://www.paraview.org/Wiki/VisIt_Database_Bridge#CGNS_Support" target="_blank">http://www.paraview.org/Wiki/VisIt_Database_Bridge#CGNS_Support</a><br>
>><br>
>><br>
>><br>
>> ________________________________<br>
>> Rick Angelini<br>
>><br>
>> USArmy Research Laboratory<br>
>> CISD/HPC Architectures Team<br>
>> Building 120 Cube 315<br>
>> Phone: <a href="tel:410-278-6266" value="+14102786266">410-278-6266</a><br>
>><br>
>> ________________________________________<br>
>> From: Utkarsh Ayachit [<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>]<br>
>> Sent: Wednesday, August 07, 2013 3:25 PM<br>
>> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)<br>
>> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>> Subject: Re: [Paraview] CGNS Reader<br>
>><br>
>> Rick,<br>
>><br>
>> Correct, VisItBridge is required for CGNS support. You can turn on<br>
>> VisItBridge by using the ENABLE_visitbridge cmake option.<br>
>><br>
>> Utkarsh<br>
>><br>
>> On Wed, Aug 7, 2013 at 3:05 PM, Angelini, Richard C (Rick) CIV USARMY<br>
>> ARL (US) <<a href="mailto:richard.c.angelini.civ@mail.mil">richard.c.angelini.civ@mail.mil</a>> wrote:<br>
>> > I'm using the Superbuild to build ParaView 4.0.1 .... and I'm enabling<br>
>> > CGNS<br>
>> > but the reader doesn't seem to be there. I can see that it downloaded<br>
>> > at<br>
>> > cgnslib tarball and it seems to have been built. I poked around on<br>
>> > the<br>
>> > Wiki and there's also a mention of using the VisIt bridge. Is the<br>
>> > VisIt<br>
>> > bridge (which I'm not using) the only way to read a CGNS file?<br>
>> ><br>
>> ><br>
>> ><br>
>> > ________________________________<br>
>> > Rick Angelini<br>
>> ><br>
>> > USArmy Research Laboratory<br>
>> > CISD/HPC Architectures Team<br>
>> > Building 120 Cube 315<br>
>> > Phone: <a href="tel:410-278-6266" value="+14102786266">410-278-6266</a><br>
>> ><br>
>> > _______________________________________________<br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>> ><br>
>> > Follow this link to subscribe/unsubscribe:<br>
>> > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>> ><br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Please keep messages on-topic and check the ParaView Wiki at:<br>
>> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
</div></div></blockquote></div><br></div>