The same is true for OverView. Jeff On Tue, Jun 30, 2009 at 4:43 PM, David E DeMarle <[email protected]>wrote:
> Thanks for doing the packaging work Orion! > > I recommend not enabling either of the new applications, nor the > non-default plugins. > > To answer your questions in more detail: > > One configure and make is sufficient to build all three. I am unsure > about installation. I believe make install places all three in the > same directory, but I know that at least on OS-X you need to run > separate scripts to package the standard ParaView client and > StreamingParaview. > > OverView and StreamingParaView are both in Pre-Alpha development > stage. At least for StreamingParaView this means that it is too > unstable to bother packaging. People should be brave enough to compile > from source if they want to try it, which is why it is not enabled by > default. The OverView developers can correct me if the same is not > true for OverView. > > thanks again, > David E DeMarle > Kitware, Inc. > R&D Engineer > 28 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-371-3971 x109 > > > > On Tue, Jun 30, 2009 at 10:10 PM, Orion Poplawski<[email protected]> > wrote: > > Okay, with 2.6.0 there are now 3 applications: > > > > -- Application: Standard ParaView Client enabled > > -- Application: OverView Informatics Client enabled > > -- Application: Streaming ParaView Application enabled > > > > I'm packaging for Fedora - does it make sense to build all three? Are > they > > mutually exclusive? Would I need to run 3 builds? Not that with the > above > > I get: > > > > CMake Warning (dev) at Applications/StreamingParaView/CMakeLists.txt:181 > > (ADD_EXECUTA > > BLE): > > Policy CMP0002 is not set: Logical target names must be globally unique. > > Run "cmake --help-policy CMP0002" for policy details. Use the > cmake_policy > > command to set the policy and suppress this warning. > > This warning is for project developers. Use -Wno-dev to suppress it. > > > > Anywhere that talks about this? > > > > Also, any problem with building all of the plugins (including > "Streaming")? > > Any incompatibilities? > > > > Thanks! > > > > -- > > Orion Poplawski > > Technical Manager 303-415-9701 x222 > > NWRA/CoRA Division FAX: 303-415-9702 > > 3380 Mitchell Lane [email protected] > > Boulder, CO 80301 http://www.cora.nwra.com > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://www.paraview.org/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > -- Jeff Baumes, Ph.D. R&D Engineer, Kitware Inc. (518) 881-4932 [email protected]
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
