Re: [Paraview] PythonProgrammableFilters Multiple Input Ports
Hi Gaël,
Thank you for your help! I was aware of this way to add multiple inputs to
a programmable filter and FYI if you would like to have a dialog appear in
the PV GUI to select the inputs in a non-arbitrary order then try making
several InputProperty attributes in the XML rather than using the
multiple_input variable.
Unfortunately, this still does not address my original issue. I need the
inputs to each be on their own port rather than multiple connections on a
single port. This is because I will implement the ability to select input
arrays from each port via drop down menus.
Does anyone know how to give the vtkPythonProgrammableFilter multiple input
ports or a means to select input arrays to process when having multiple
connections on one port? I have a robust means of selecting input arrays
for just one input but I cannot get it to work for more than one input.
Thank you,
Bane
On June 1, 2018 at 1:33:02 AM, Gaël Grail (gael.gr...@gmail.com) wrote:
Hi Bane,
I'm using the binary version of Paraview available in Kitware's website, so
I don't know much about what should be written in the C code.
But in the xml, I'm using this and it works perfectly:
...
Hope this helps,
Gaël
2018-06-01 2:40 GMT+02:00 Bane Sullivan :
> Hi there,
>
> I see an old thread here: https://paraview.markmail.org/thread/
> z7cy73444s7fjadk about setting multiple input ports for python
> programmable filters but I cannot get this to work.
>
> I want to declare multiple input ports in a ServerManagerConfiguration XML
> plugin but I have been unable to successfully add more than one input port
> to the vtkPythonProgrammableFilter.
>
> I see that in
> `paraview/ParaViewCore/ClientServerCore/Core/vtkPythonProgrammableFilter.h`
> the following is declared:
>
> /**
>* Set the number of input ports
>* This function is explicitly exposed to enable a
> vtkClientServerInterpreter to call it
>*/
> void SetNumberOfInputPorts(int numberOfInputPorts) VTK_OVERRIDE
> {
> this->Superclass::SetNumberOfInputPorts(numberOfInputPorts);
> }
>
>
> This leads me to believe that the functionality is there, but how exactly
> would I set the number of input ports from an XML plugin for a Programmable
> Filter? I have tried the following with no luck:
>
>
>
> name="TestMuliPort”
> class="vtkPythonProgrammableFilter”
> label=“TestMuliPort”
> post_creation=“SetNumberOfInputPorts"
> arguments="2”>
> ……..
>
>
> I get the following ERROR:
>
> ERROR: In /Users/kitware/dashboards/buildbot-slave/8275bd07/build/
> superbuild/paraview/src/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx,
> line 371
> vtkPVSessionCore (0x60cd4510): Object type:
> vtkPythonProgrammableFilter, could not find requested method:
> "SetNumberOfInputPorts"
> or the method was called with incorrect arguments.
>
> while processing
> Message 0 = Invoke
> Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter
> (0x60c0003abde0)}
> Argument 1 = string_value {SetNumberOfInputPorts}
>
>
>
> Any help would be greatly appreciated,
>
> Bane
>
>
>
> ___
> Powered by www.kitware.com
>
> ParaView discussion is moving! Please visit https://discourse.paraview.
> org/ for future posts.
>
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for
future posts.
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] vtk renderer
The renderer will ask for its container size when you call resize() on it.
So if that container keep growing due to the setup of your css, the size
propagation won't go to the server as the container will never shrink.
You need to fix the width in some way like you did for the height. You can
use 50vw or use a mix of absolute/relative position in your dom hierarchy.
On Thu, Jun 7, 2018 at 12:35 PM Sgouros, Thomas
wrote:
> Hi Sebastien:
>
> Looks like this:
>
> style={{position: 'relative',
> height: '80vh',
> overflow: 'hidden',
> zIndex: '10',
> }}
> />
>
> Another data point: when I shrink or grow the window in the vertical, the
> *height* of the canvas element changes in both directions, but the width
> only changes when I grow the window and not when I shrink it. Maybe what
> you're saying though is that I should travel up the hierarchy and see where
> I'm setting heights and widths in non-parallel ways?
>
> Thank you,
>
> -Tom
>
>
> On Thu, Jun 7, 2018 at 2:28 PM, Sebastien Jourdain <
> sebastien.jourd...@kitware.com> wrote:
>
>> Hi Tom,
>>
>> That would be a ParaViewWeb question. The issue is related to the css for
>> your div that contains the renderer.
>> To allow the renderer to shrink you need to set "overflow: hidden;"
>> assuming the rest of the size of the div is defined by other constraints.
>>
>> Seb
>>
>> On Thu, Jun 7, 2018 at 11:41 AM Sgouros, Thomas
>> wrote:
>>
>>> Hi All:
>>>
>>> I'm not sure if this is a VTK question or a Paraview question, so
>>> apologies in advance. In a ParaViewWeb application, I have a vtkRenderer in
>>> a div in another div, etc. The vtkRenderer seems to adjust when I make the
>>> window it's in bigger or the container, but it does not resize when I make
>>> the window smaller. Using the browser's element viewer, I can see the
>>> object inside, and see its width reach when I expand elements and
>>> refuse to react when I contract the window or container.
>>>
>>> When I create the vtk renderer, I use this code:
>>>
>>>this.renderers.push(VtkRenderer.newInstance({
>>> client: this.model.pvwClient,
>>> viewId: result,
>>> }) );
>>>
>>> ... and then later...
>>>
>>> SizeHelper.onSizeChange(() => {
>>> this.renderers[0].resize();
>>> this.renderers[1].resize();
>>> });
>>> SizeHelper.startListening();
>>>
>>> I invoke the SizeHelper.triggerChange() method regularly and it seems to
>>> work, though again only to make the renderer bigger.
>>>
>>> Should I be resizing these with a direct call to some method? What is
>>> the way I should be doing this?
>>>
>>> Thank you,
>>>
>>> -Tom
>>>
>>>
>>>
>>> ___
>>> Powered by www.kitware.com
>>>
>>> ParaView discussion is moving! Please visit
>>> https://discourse.paraview.org/ for future posts.
>>>
>>> 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
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> https://public.kitware.com/mailman/listinfo/paraview
>>>
>>
>
___
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for
future posts.
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] vtk renderer
Hi Sebastien:
Looks like this:
Another data point: when I shrink or grow the window in the vertical, the
*height* of the canvas element changes in both directions, but the width
only changes when I grow the window and not when I shrink it. Maybe what
you're saying though is that I should travel up the hierarchy and see where
I'm setting heights and widths in non-parallel ways?
Thank you,
-Tom
On Thu, Jun 7, 2018 at 2:28 PM, Sebastien Jourdain <
sebastien.jourd...@kitware.com> wrote:
> Hi Tom,
>
> That would be a ParaViewWeb question. The issue is related to the css for
> your div that contains the renderer.
> To allow the renderer to shrink you need to set "overflow: hidden;"
> assuming the rest of the size of the div is defined by other constraints.
>
> Seb
>
> On Thu, Jun 7, 2018 at 11:41 AM Sgouros, Thomas
> wrote:
>
>> Hi All:
>>
>> I'm not sure if this is a VTK question or a Paraview question, so
>> apologies in advance. In a ParaViewWeb application, I have a vtkRenderer in
>> a div in another div, etc. The vtkRenderer seems to adjust when I make the
>> window it's in bigger or the container, but it does not resize when I make
>> the window smaller. Using the browser's element viewer, I can see the
>> object inside, and see its width reach when I expand elements and
>> refuse to react when I contract the window or container.
>>
>> When I create the vtk renderer, I use this code:
>>
>>this.renderers.push(VtkRenderer.newInstance({
>> client: this.model.pvwClient,
>> viewId: result,
>> }) );
>>
>> ... and then later...
>>
>> SizeHelper.onSizeChange(() => {
>> this.renderers[0].resize();
>> this.renderers[1].resize();
>> });
>> SizeHelper.startListening();
>>
>> I invoke the SizeHelper.triggerChange() method regularly and it seems to
>> work, though again only to make the renderer bigger.
>>
>> Should I be resizing these with a direct call to some method? What is the
>> way I should be doing this?
>>
>> Thank you,
>>
>> -Tom
>>
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> ParaView discussion is moving! Please visit https://discourse.paraview.
>> org/ for future posts.
>>
>> 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
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> https://public.kitware.com/mailman/listinfo/paraview
>>
>
___
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for
future posts.
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
[Paraview] vtk renderer
Hi All:
I'm not sure if this is a VTK question or a Paraview question, so apologies
in advance. In a ParaViewWeb application, I have a vtkRenderer in a div in
another div, etc. The vtkRenderer seems to adjust when I make the window
it's in bigger or the container, but it does not resize when I make the
window smaller. Using the browser's element viewer, I can see the
object inside, and see its width reach when I expand elements and refuse to
react when I contract the window or container.
When I create the vtk renderer, I use this code:
this.renderers.push(VtkRenderer.newInstance({
client: this.model.pvwClient,
viewId: result,
}) );
... and then later...
SizeHelper.onSizeChange(() => {
this.renderers[0].resize();
this.renderers[1].resize();
});
SizeHelper.startListening();
I invoke the SizeHelper.triggerChange() method regularly and it seems to
work, though again only to make the renderer bigger.
Should I be resizing these with a direct call to some method? What is the
way I should be doing this?
Thank you,
-Tom
___
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for
future posts.
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] [Paraview-developers] [ANNOUNCE] ParaView 5.5.1 now available for download
If we are looking for 5.5.2 bits: In 5.5.1 it seems that I still need to patch VTK/ThirdParty/vtkm/vtk-m/CMake/VTKmDetermineVersion.cmake (commit cf91ca520e38faa1afae5d0bcc6788b2b4660c3e) I that Andy's catalyst changes might have made it in, but wasn't really surprised not to see them since they do change the API. Nonetheless, I'll express them as a wish: CoProcessing/Catalyst/vtkCPProcessor.cxx CoProcessing/Catalyst/vtkCPProcessor.h CoProcessing/Catalyst/vtkCPXMLPWriterPipeline.cxx Wrapping/Python/paraview/coprocessing.py Cheers, /mark ___ Powered by www.kitware.com ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts. 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
[Paraview] Odd problem slicing/cutting complex polyhedron
Hi,I have attached two files. One is a single-cell complex polyhedron which I wish to be able to use and visualise (as is, without tessellation and tetrahedralization). Using 5.5.0 this fails to slice/cut in paraview in any major plane. Paraview complains about non-manifold (under-connected) edges. To debug I wrote out as a vtkPolyData containing all the faces of this single cell polyhedron. This polyData Slices/cuts just fine. All faces added to the vtp file as VTK_POLYGON, likewise are added as a face-stream when added as a VTK_POLYHEDRON to the vtu file. To be clear, I write the faces out to the vtp in the same loop I build the faces for the single cell vtu mesh, so they are carbon copies of the faces, including numbering, ordering etc. I am aware there are more vertices in the file than need be (27 rather than 19), but it was easier...My working assumption is that there is no problem visualising and working with cells of this type (non-convex) in paraview (real use cases includes a mesh with many of these types of cells). Clarity on this point would also be good…I believe paraview should work for concave cells and I suspect it’s a bug (either in paraview or my face-data) because if I use 5.4.1 (or indeed 5.2.0) I can clip the singleCell in the x-plane (with inside-out flag on/off) and I get the expected results. However, in the y and z planes I do not get the expected results and those versions either return an empty result or the whole cell. I get no results in 5.5.0 regardless of plane. Finally, I get no results in 5.5.1 either. So it sort of used to work in earlier versions depending on the plane of slicing, but now does not. I’m not sure what I’m doing wrong, can somebody shed some light or spot an error in the attached file? This may be linked to:https://gitlab.kitware.com/paraview/paraview/issues/18003Thanks again,Andy singleCell.vtu Description: Binary data cellFaces.vtp Description: Binary data ___ Powered by www.kitware.com ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts. 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Find the intersection point between a connectivity and a stream tracer
On Wed, Jun 6, 2018 at 11:00 AM Caffagni, Andrea < andrea.caffa...@ferrari.com> wrote: > Thank you Cory for the answer, > > Your idea works also if I have, instead of a slice, only a portion of a > slice (I cut slices portions thanks to the connectivity filter)? > No, my solution is for the special case of a plane. For your case, please see my tip on our Discourse forum that will explain how to do this for your portion of a slice: https://discourse.paraview.org/t/compute-the-signed-distance-field-from-a-polygonal-mesh/123 Once you have followed the steps in the tip, apply a Contour filter to the output of the Programmable Filter. Set the isovalue to 0 and the Contour By property to Distance. The output will consist of your intersection points. See the attached image where I have done this. The red spheres show the intersection points. HTH, Cory > In the image attached, I have created a connectivity (in blue) of a slice > and a streamline in red that crosses it. > > > > Best Regards, > > Andrea > > > > *From:* Cory Quammen [mailto:cory.quam...@kitware.com] > *Sent:* Wednesday, June 06, 2018 15:27 > *To:* Caffagni, Andrea > *Cc:* paraview@public.kitware.com > *Subject:* Re: [Paraview] Find the intersection point between a > connectivity and a stream tracer > > > > Andrea, > > > > In fact, you can use the Slice filter itself to compute the intersection > of streamlines with a plane. Just apply a Slice filter to your StreamTracer > output, align the Slice with your desired plane, and you will get the > intersection points. > > > > See the attached image that shows stream tracer output, the plane widget > from the Slice filter (red rectangle), and the intersection points depicted > with blue spherical glyphs. > > > > HTH, > > Cory > > > > On Wed, Jun 6, 2018 at 7:23 AM Caffagni, Andrea < > andrea.caffa...@ferrari.com> wrote: > > Does anyone have an idea on how to deal with this problem? > > Does Paraview have no tools to easily find a point of intersection between > plan and line? > > > > Best Regards, > > Andrea > > > > *From:* Caffagni, Andrea > *Sent:* Thursday, May 31, 2018 14:19 > *To:* paraview@public.kitware.com > *Subject:* Find the intersection point between a connectivity and a > stream tracer > > > > Dear Users, > > I need to find the intersection point between a connectivity surface > (portion of a slice) and a stream tracer that runs through this. > I have tried the IntersectFragments it doesn’t work with stream tracer. > Someone > of you have some suggestions? Best regards, Andrea > > > > > _ > > > > Questo messaggio è da intendersi esclusivamente ad uso del destinatario e > può contenere informazioni che sono di natura privilegiata, confidenziale o > non divulgabile secondo le leggi vigenti. Se il lettore del presente > messaggio non è il destinatario designato, o il dipendente/agente > responsabile per la consegna del messaggio al destinatario designato, si > informa che ogni disseminazione, distribuzione o copiatura di questa > comunicazione è vietata anche ai sensi della normativa vigente in materia > di protezione dei dati personali. Se avete ricevuto questo messaggio per > errore, vi preghiamo di notificarcelo immediatamente a mezzo e-mail di > risposta e successivamente di procedere alla cancellazione di questa e-mail > e relativi allegati dal vostro sistema. > > > _ > > > > This message is intended only for the use of the addressee and may contain > information that is privileged, confidential and exempt from disclosure > under applicable law. If the reader of this message is not the intended > recipient, or the employee or agent responsible for delivering the message > to the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is prohibited under the > applicable data protection law. If you have received this e-mail by > mistake, please notify us immediately by return e-mail and delete this > e-mail and all attachments from your system. > > > > > _ > > ___ > Powered by www.kitware.com > > ParaView discussion is moving! Please visit > https://discourse.paraview.org/ for future posts. > > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview > > > > > -- > > Cory Quammen > Staff R Engineer > Kitware, Inc. > > >
Re: [Paraview] Adding Filters to Catalyst
Hi Gregg, Catalyst will use all of the MPI ranks in the global communicator unless you pass it another MPI communicator upon initialization. It sounds like the data isn't getting constructed in the adaptor the way you think it is. You may want to try the Process Id Scalars filter to see where the data is really located and add some print statements in the adaptor to verify the behavior. Best, Andy On Wed, Jun 6, 2018 at 2:08 PM Gregg Streuber < gregg.streu...@aero.bombardier.com> wrote: > Hey Andy, > > > > Apologies, I must have hit “reply” without thinking, rather than reply > all. I’ve actually managed to resolve that issue, it turned out to be a > configuration issue with my build of OpenGL. > > > > I do have another question though. I’ve been playing around processing > some data using Catalyst’s python scripting in parallel and the results > aren’t quite what I expected. What I’ve been using is a toy 50,000,000 > node cube mesh with an arbitrary velocity field, and having Catalyst do > some assorted processing – taking cuts etc. I’ve divided the mesh into 256 > blocks using the VTKMultiBlockDataSet structure, on 256 cores. But when I > load the results into Paraview it only indicates 12 VTKBlocks on the > VTBBlockColors filter. There are 256 divisions in the mesh, but 244 of them > are duplicates, coloured with one of the 1st 12 colours. > > > > Adding new lines to the color map, mapped to values >11, doesn’t appear to > change anything. > > > > I’m also not seeing much in the way of performance variation when I use > 13-256 cores, it’s only when I drop below 12 that things take appreciably > longer. > > > > Is Paraview by default only taking advantage of 12 cores at a time? Is > this something I can change? > > > > *From:* Andy Bauer [mailto:andy.ba...@kitware.com] > *Sent:* Wednesday, June 06, 2018 10:18 AM > *To:* Gregg Streuber ; Paraview ( > parav...@paraview.org) > *Subject:* Re: [Paraview] Adding Filters to Catalyst > > > > Hi Gregg, > > > > Please keep the conversations on the mailing list so that everyone can > participate (also, emails get lost in my inbox so that can also delay a > quick response). > > > > I believe that the Catalyst examples should compile properly with all of > the Catalyst editions (though I haven't tested them). If you were able to > use an OpenGL with some editions then that should work for any edition that > depends on OpenGL. Are you working with a Catalyst edition build directory > or an install directory? If you give me some more information on how to > reproduce the error I can try and track things down. > > > > Also, what version of ParaView are you using? > > > > Cheers, > > Andy > > > > On Fri, Jun 1, 2018 at 3:37 PM Gregg Streuber < > gregg.streu...@aero.bombardier.com> wrote: > > Hi Andy, > > > > Thanks for the information. I had a full compile of Paraview running on > the side just in case, I was just curious if there was an easy and > efficient way to customize a Catalyst install. > > > > I’ve since gotten Paraview compiled, but when I try to test the > functionality using some of the included Catalyst examples > (Examples/Catalyst) they don’t work. Specifically several of them throw > “undefined reference” errors during compilation, referring to a couple of > OpenGL files in the Paraview install. These examples worked fine when I > compiled them with the Catalyst build I was testing before. Do these > examples require a specific build of OpenGL (or are they incompatible with > certain other modules)? > > > > Thanks, > Gregg > > > > *From:* Andy Bauer [mailto:andy.ba...@kitware.com] > *Sent:* Friday, June 01, 2018 11:46 AM > *To:* Gregg Streuber > *Cc:* paraview@public.kitware.com > *Subject:* Re: [Paraview] Adding Filters to Catalyst > > > > Hi Gregg, > > > > You can always use a full build of ParaView for Catalyst to make sure you > get all of the filters available during Catalyst runs. > > > > There is information at > https://blog.kitware.com/paraview-catalyst-editions-what-are-they/ which > gives details about the editions but there's currently not a lot of details > on how to make your own edition. Editing the cmake.sh script to add in more > VTK filters will likely not work as the Catalyst editions don't even have > all of the source code from the ParaView source. > > > > As for finding the full list of filters and modules available, the blog > post has some of that but it's changed some. My recommendation would be to > build an edition with Python enabled and then use pvpython to see what's > available. Alternatively you could look at files like filters.xml in the > Catalyst source code to see what's there. It's not ideal but allows you to > check on stuff before actually running a simulation. > > > > Best, > > Andy > > > > On Fri, Jun 1, 2018 at 10:10 AM Gregg Streuber < > gregg.streu...@aero.bombardier.com> wrote: > > Hi All, > > > > I’ve recently installed the most full-featured version of Catalyst > available on the website,
Re: [Paraview] [ANNOUNCE] ParaView 5.5.1 now available for download
Thanks, Burlen. I'll plan to look into it before we tag 5.5.2.
Utkarsh
On Wed, Jun 6, 2018 at 5:58 PM Burlen Loring wrote:
> Hi Utkarsh,
>
> Sorry I missed your reply, I thought my post got bounced and didn't look.
>
> BUILD_SHARED_LIBS=OFF and PARAVIEW_USE_VISITBRIDGE=ON will reproduce the
> issue.
>
> I was able to quickly move past it by finding VISIT_STATIC in the cmake
> code and making the following change
>
> ParaView/Utilities/VisItBridge$git diff
> diff --git a/Library/VisItLib/CMake/VisItCommon.cmake
> b/Library/VisItLib/CMake/VisItCommon.cmake
> index 0bfad93..b4f136c 100644
> --- a/Library/VisItLib/CMake/VisItCommon.cmake
> +++ b/Library/VisItLib/CMake/VisItCommon.cmake
> @@ -26,14 +26,14 @@ if(VISIT_DISABLE_COMPILER_WARNINGS)
> endif(VISIT_DISABLE_COMPILER_WARNINGS)
>
> #set up some vars we need to compile
> -set(VISIT_STATIC)
> -if (BUILD_SHARED_LIBS)
> +#set(VISIT_STATIC)
> +#if (BUILD_SHARED_LIBS)
> set(VISIT_STATIC 0)
> add_definitions(-DVISIT_BUILD_SHARED_LIBS)
> -else(VISIT_STATIC)
> - set(VISIT_STATIC 1)
> - add_definitions(-DVISIT_STATIC -DGLEW_STATIC)
> -endif()
> +#else(VISIT_STATIC)
> +# set(VISIT_STATIC 1)
> +# add_definitions(-DVISIT_STATIC -DGLEW_STATIC)
> +#endif()
>
> set(VISIT_SOURCE_DIR ${VisItBridgePlugin_SOURCE_DIR})
> set(VISIT_BINARY_DIR ${VisItBridgePlugin_BINARY_DIR})
>
>
> On 06/05/2018 01:15 PM, Utkarsh Ayachit wrote:
> > Burlen,
> >
> > Are you doing a static build of ParaView? What Cmake flags did you use?
> >
> > Utkarsh
>
>
___
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for
future posts.
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
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
