From bastien.jacquet at kitware.com Tue Nov 1 07:48:15 2016 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Tue, 1 Nov 2016 12:48:15 +0100 Subject: [Paraview-developers] Proxy Property names & labels In-Reply-To: References: Message-ID: Hello Utkarsh, I also spent a few hours the other day, just to discover that my problem was this mismatch between proxy's name and label, through python access. Maybe we should throw the developers a warning at compile time when the two mismatch, to avoid confusion. The other "solution" I can think of is to allow property access through both name and label. But this looks like a hack, and might have side-effect I'm not aware of. Best, Bastien On Mon, Oct 31, 2016 at 10:16 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > When we started, we indeed used the property's XMLName as the name for > the parameter in the Python script. However, it was noted that the > parameter name in Python would not match what the user saw in the UI > and hence he had no clue how to look for it. Hence, we changed it such > that the Python parameter name uses label instead. > > This would not have been an issue if a property's (or proxy's) name > and label are the same, however this didn't happen for historical > reasons. > > Now changing property names after the fact is harder since we need to > ensure backwards compability for pvsm and py files. > > Utkarsh > > On Mon, Oct 31, 2016 at 2:06 PM, Joachim Pouderoux > wrote: > > Hi, > > > > Writing a python script for PV5.2, I needed to save a temporal ptvtu file > > and faced this problem again: looking at the proxy's XML definition, the > > writer has the name=WriteAllTimeSteps property. > > > > > default_values="0" > > label="Write all timesteps as file-series" > > name="WriteAllTimeSteps" > > number_of_elements="1"> > > > > So I tried something like this: > > > > SaveData("test.pvtu", WriteAllTimeSteps=1) > > > > But it failed claiming that the writer has no WriteAllTimeSteps property! > > Well, looking at the help() on the writer instance it looked like indeed, > > the exposed python property is not call WriteAllTimeSteps but > > Writealltimestepsasfileseries: > > | Writealltimestepsasfileseries > > | When WriteAllTimeSteps is turned ON, the writer is > > | executed once for each timestep available from the > > | reader. > > > > Isn't it ugly? > > So is the choice of exposing the property using its concatenated label a > > deliberate choice or a bug? > > It seems to me very unnatural, the label should be reserved for better > human > > readable UI printing. > > > > What do you think? > > > > Best, > > > > Joachim Pouderoux, PhD > > > > Technical Expert - Scientific Computing Team > > Kitware SAS > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Nov 1 09:53:30 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 1 Nov 2016 09:53:30 -0400 Subject: [Paraview-developers] Proxy Property names & labels In-Reply-To: References: Message-ID: > Maybe we should throw the developers a warning at compile time when the two > mismatch, to avoid confusion. We should indeed, however it's a longer process since we need to fix the existing discrepancies first. Doing that while ensuring backwards compatibility is tedious, though not impossible. > The other "solution" I can think of is to allow property access through both > name and label. But this looks like a hack, and might have side-effect I'm > not aware of. That should be doable fairly easily. Can't think of any major pitfalls with that. From dan.lipsa at kitware.com Tue Nov 1 10:04:20 2016 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 1 Nov 2016 10:04:20 -0400 Subject: [Paraview-developers] Proxy Property names & labels In-Reply-To: References: Message-ID: What works nicely to avoid confusion in the future is to only use "name". Paraview will use that in the interface if the "label" is not present. See a recent change I made https://gitlab.kitware.com/paraview/paraview/merge_requests/1152/diffs#note_ 188653 and how it looks in ParaView https://blog.kitware.com/enhancements-to-the-community- atmospheric-model-cam-netcdf-reader/ I just tried accessing this from python and it works fine. Dan On Mon, Oct 31, 2016 at 5:16 PM, Utkarsh Ayachit < utkarsh.ayachit at kitware.com> wrote: > When we started, we indeed used the property's XMLName as the name for > the parameter in the Python script. However, it was noted that the > parameter name in Python would not match what the user saw in the UI > and hence he had no clue how to look for it. Hence, we changed it such > that the Python parameter name uses label instead. > > This would not have been an issue if a property's (or proxy's) name > and label are the same, however this didn't happen for historical > reasons. > > Now changing property names after the fact is harder since we need to > ensure backwards compability for pvsm and py files. > > Utkarsh > > On Mon, Oct 31, 2016 at 2:06 PM, Joachim Pouderoux > wrote: > > Hi, > > > > Writing a python script for PV5.2, I needed to save a temporal ptvtu file > > and faced this problem again: looking at the proxy's XML definition, the > > writer has the name=WriteAllTimeSteps property. > > > > > default_values="0" > > label="Write all timesteps as file-series" > > name="WriteAllTimeSteps" > > number_of_elements="1"> > > > > So I tried something like this: > > > > SaveData("test.pvtu", WriteAllTimeSteps=1) > > > > But it failed claiming that the writer has no WriteAllTimeSteps property! > > Well, looking at the help() on the writer instance it looked like indeed, > > the exposed python property is not call WriteAllTimeSteps but > > Writealltimestepsasfileseries: > > | Writealltimestepsasfileseries > > | When WriteAllTimeSteps is turned ON, the writer is > > | executed once for each timestep available from the > > | reader. > > > > Isn't it ugly? > > So is the choice of exposing the property using its concatenated label a > > deliberate choice or a bug? > > It seems to me very unnatural, the label should be reserved for better > human > > readable UI printing. > > > > What do you think? > > > > Best, > > > > Joachim Pouderoux, PhD > > > > Technical Expert - Scientific Computing Team > > Kitware SAS > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Tue Nov 1 15:17:37 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 1 Nov 2016 15:17:37 -0400 Subject: [Paraview-developers] [ANN] Dropping 32bit binaries for 5.3 and beyond In-Reply-To: Message-ID: <20161101191737.GA28502@megas.kitware.com> Hi, We're planning on dropping 32bit binaries (currently only provided on Windows) for post-5.2 development. Any objections? --Ben From magnus_elden at hotmail.com Wed Nov 2 01:28:57 2016 From: magnus_elden at hotmail.com (Magnus Elden) Date: Wed, 2 Nov 2016 05:28:57 +0000 Subject: [Paraview-developers] What I have learned about providing a VR system that is intuitive to use while keeping discomfort to a minimum. In-Reply-To: <1e6d01d234c7$64aea8b0$2e0bfa10$@hotmail.com> References: <1e6d01d234c7$64aea8b0$2e0bfa10$@hotmail.com> Message-ID: Hello! I sent a mail to Kitware and got a reply that I should send this info to the VTK and Paraview developer mailing lists. I would like to start with saying that the following words are based on my personal experience and the feedback I have gotten from the small group of people around me who have tried VR systems. As such, please think about what I have to say and then do your own testing to see what works for your own systems and use cases. I have been working on using Paraview with UE4 to provide a platform for VR to be used as a tool of scientific visualisation. I have been working on this for only half a year, and I started by looking into maybe modifying Paraview to render to OpenVR. However, I was defeated by the fact that I could not for the life of me understand how to use VTK to open xdmf files. I got errors complaining about time all the time. I eventually hacked a python script together to render and create a bunch of slices that I imported to UE4 and I wrote my own volume renderer there. You are basically doing what I am doing for my master's thesis and I believe that having VR support directly integrated into VTK or Paraview is the best way to go for VR visualization for researchers. Since I am not that well versed with the Paraview and VTK systems I was unable to help directly by adding code, especially since I had nobody to really turn to, but I can at least provide some hints based on my experience. First and foremost, when running in a VR environment it is very important for the user that they have a floor and maybe some walls which they can use for reference. Blurring, depth of field and motion blur are also enemies of a good VR experience. The Paraview overlap detection also seemed slightly wonky as I had to re-grab several times. Unlike a standard screen a VR system covers the entire visual field and makes it impossible for the brain to calibrate using peripheral vision. This leads to mismatch between visual cues and the other signals the brain receives. This mismatch leads to the users feeling nausea and other discomforts. This makes the standard systems used for visualizing 3D models and volumes are not optimal. In short, make it feel like you have the model in front of you inside a world you have created. Imagine a hologram in a science fiction film. Finally, from feedback, the handling should be similar to handling objects in real life in order to minimize confusion and make it natural. This means that the model is not necessarily in the center of the space around which the camera rotates. The models can be moved by grabbing with the controllers and scaled in the models local space, not world space, by grabbing the model with both hands. Handling things like cutting planes will also have to be like moving a stick or something else physical we handle in the real world with our hands. The way the cutting plane in Paraview is already working is a very good example of how it can be. Grab the center with your left hand and place it where you want it to be while you grab the rotational "stick" with your right hand and orient it. Quickly I want to answer what I find to be the strengths and weaknesses of both the Paraview, and similar platforms, and game engines like UE4. Paraview is great for volumetric visualisations and quick iterative analysis. Colour encoding and iso-surface generation and all the other powerful tools of Paraview is great for the researchers who can understand the colours, symbols and encoded data. It is not good for creating a interactive, wholesome experience that can be experiences by several users at once. This is where UE4 can shine. As a research tool it is not great, but it is great at presentation. Simplified and processed models can be made to move and interact with any number of concurrent users while showing animations and playing sounds. This allows UE4 to be a great tool to Conway the processed data to those learning or otherwise without the required specialized knowledge. For education and presentation I can see a lot of use for these simplified and processed models. I wrote this because I believe VR can be a great aid for research. I also know that Paraview and similar software are made for the researchers and I want to stress that Paraview should keep that focus. It can be among the best tools a researcher has and as such it should not diminish itself by trying to also be something it is not. I hope that this will lead to Paraview and VTK being used to give even better functionality for the scientific world. Yours, Magnus Elden If you want some info on what I am doing and the state of the volume rendering in VR in UE4, please refer to this forum thread: https://forums.unrealengine.com/showthread.php?119267-Your-thoughts-on-and-comments-to-Volume-Rendering-in-Unreal-Engine-4/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bastien.jacquet at kitware.com Wed Nov 2 11:27:45 2016 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Wed, 2 Nov 2016 16:27:45 +0100 Subject: [Paraview-developers] ParaViewDetermineVersion: when is _VERSION_IS_RELEASE FALSE ? Message-ID: Hello Folks, It seems to me that PARAVIEW_VERSION_IS_RELEASE is always set to TRUE when using git describe output. This is due to the following test relying on VERSION_EQUAL instead of STR_EQUAL: CMake/ParaViewDetermineVersion.cmake:83 if("${major}.${minor}.${patch}" VERSION_EQUAL "${full}") It seems that CMake VERSION_EQUAL test has been designed to only compare the dot-separated digits ... which makes it always true for our "X.Y.Z-RCW" scheme. Only a "X.Y.Z.W" scheme would make it work as expected. Is there anything I missed? If not, I'll do a merge request to replace the VERSION_EQUAL with STR_EQUAL. Best, Bastien Jacquet, PhD Technical Leader - Computer Vision Team Kitware SAS 26 rue Louis Gu?rin - 69100 Villeurbanne - France F: +33 (0)4.37.45.04.15 -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Nov 2 12:58:47 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 2 Nov 2016 12:58:47 -0400 Subject: [Paraview-developers] ParaViewDetermineVersion: when is _VERSION_IS_RELEASE FALSE ? In-Reply-To: References: Message-ID: You suggestion sounds reasonable to me. On Wed, Nov 2, 2016 at 11:27 AM, Bastien Jacquet wrote: > Hello Folks, > > It seems to me that PARAVIEW_VERSION_IS_RELEASE is always set to TRUE when > using git describe output. > This is due to the following test relying on VERSION_EQUAL instead of > STR_EQUAL: > CMake/ParaViewDetermineVersion.cmake:83 > if("${major}.${minor}.${patch}" VERSION_EQUAL "${full}") > > It seems that CMake VERSION_EQUAL test has been designed to only compare the > dot-separated digits ... which makes it always true for our "X.Y.Z-RCW" > scheme. > Only a "X.Y.Z.W" scheme would make it work as expected. > > Is there anything I missed? > If not, I'll do a merge request to replace the VERSION_EQUAL with STR_EQUAL. > > Best, > > Bastien Jacquet, PhD > Technical Leader - Computer Vision Team > Kitware SAS > 26 rue Louis Gu?rin - 69100 Villeurbanne - France > F: +33 (0)4.37.45.04.15 From egoli2 at illinois.edu Thu Nov 3 12:31:01 2016 From: egoli2 at illinois.edu (egoli2) Date: Thu, 3 Nov 2016 09:31:01 -0700 (MST) Subject: [Paraview-developers] Error using Paraview calculator Message-ID: <1478190661529-4855.post@n6.nabble.com> Hi everyone When I use calculator in Paraview to change the value of the one of the output I get this error: ---------------------------------------------------------------------------------------------------------------- ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, line 1484 vtkFunctionParser (0x6e70250): Syntax error: expecting a variable name; see position 12 ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, line 1484 vtkFunctionParser (0x6e70250): Syntax error: expecting a variable name; see position 12 Warning: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Filters/Core/vtkArrayCalculator.cxx, line 401 vtkPVArrayCalculator (0x6e6f900): An error occurred when parsing the calculator's function. See previous errors. ----------------------------------------------------------------------------------------------------------------------------------------- it happens when I type a + or - or * next to the temperature (the main field in my simulation). And, by the way, the apply button is always off! I do not know really why! Do you have any idea to avoid this problem? Best, Elyas -- View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Error-using-Paraview-calculator-tp4855.html Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com. From andy.bauer at kitware.com Thu Nov 3 12:57:14 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 3 Nov 2016 12:57:14 -0400 Subject: [Paraview-developers] Error using Paraview calculator In-Reply-To: <1478190661529-4855.post@n6.nabble.com> References: <1478190661529-4855.post@n6.nabble.com> Message-ID: Hi, What OS are you on and what version of ParaView are you using? I suspect that it's the auto-apply feature that is causing problems. When this is done then the apply button will pretty much always be off because actions that you're doing in the GUI are automatically executed/updated by the server. To disable this feature you can click on the button at the top of the GUI with the little workstation with a green arrow pointing up and to the right. Best, Andy On Thu, Nov 3, 2016 at 12:31 PM, egoli2 wrote: > Hi everyone > > When I use calculator in Paraview to change the value of the one of the > output I get this error: > > ------------------------------------------------------------ > ---------------------------------------------------- > ERROR: In > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/ > paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, > line 1484 > vtkFunctionParser (0x6e70250): Syntax error: expecting a variable name; > see > position 12 > > > ERROR: In > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/ > paraview/src/paraview/VTK/Common/Misc/vtkFunctionParser.cxx, > line 1484 > vtkFunctionParser (0x6e70250): Syntax error: expecting a variable name; > see > position 12 > > > Warning: In > /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/ > paraview/src/paraview/VTK/Filters/Core/vtkArrayCalculator.cxx, > line 401 > vtkPVArrayCalculator (0x6e6f900): An error occurred when parsing the > calculator's function. See previous errors. > > ------------------------------------------------------------ > ------------------------------------------------------------ > ----------------- > > it happens when I type a + or - or * next to the temperature (the main > field > in my simulation). > > And, by the way, the apply button is always off! I do not know really why! > > Do you have any idea to avoid this problem? > > Best, > Elyas > > > > -- > View this message in context: http://the-unofficial- > paraview-developers-forum.34153.x6.nabble.com/Error- > using-Paraview-calculator-tp4855.html > Sent from the The Unofficial ParaView Developers Forum mailing list > archive at Nabble.com. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From egoli2 at illinois.edu Thu Nov 3 13:26:45 2016 From: egoli2 at illinois.edu (egoli2) Date: Thu, 3 Nov 2016 10:26:45 -0700 (MST) Subject: [Paraview-developers] Error using Paraview calculator In-Reply-To: References: <1478190661529-4855.post@n6.nabble.com> Message-ID: <1478194004999-4857.post@n6.nabble.com> Thanks! Yes, you are absolutely right. It is solved now. I just turn the auto-apply off and it worked perfect! Many thanks! Best, Elyas -- View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Error-using-Paraview-calculator-tp4855p4857.html Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com. From andy.bauer at kitware.com Thu Nov 3 13:32:08 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 3 Nov 2016 13:32:08 -0400 Subject: [Paraview-developers] Error using Paraview calculator In-Reply-To: <1478194004999-4857.post@n6.nabble.com> References: <1478190661529-4855.post@n6.nabble.com> <1478194004999-4857.post@n6.nabble.com> Message-ID: By the way, what version of ParaView are you using and what OS? Also, did you build it yourself or use an installer? Even when I have the auto-apply option enabled I don't get the bad behavior that you see but I'd like to make sure it's working properly on all platforms for the PV 5.2 release. Thanks, Andy On Thu, Nov 3, 2016 at 1:26 PM, egoli2 wrote: > Thanks! Yes, you are absolutely right. It is solved now. I just turn the > auto-apply off and it worked perfect! > Many thanks! > > Best, > Elyas > > > > -- > View this message in context: http://the-unofficial- > paraview-developers-forum.34153.x6.nabble.com/Error- > using-Paraview-calculator-tp4855p4857.html > Sent from the The Unofficial ParaView Developers Forum mailing list > archive at Nabble.com. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From egoli2 at illinois.edu Thu Nov 3 13:37:47 2016 From: egoli2 at illinois.edu (egoli2) Date: Thu, 3 Nov 2016 10:37:47 -0700 (MST) Subject: [Paraview-developers] Error using Paraview calculator In-Reply-To: References: <1478190661529-4855.post@n6.nabble.com> <1478194004999-4857.post@n6.nabble.com> Message-ID: <1478194667650-4859.post@n6.nabble.com> Linux OS and version 3.98.1 64-bit. I am using paraview to read a .e data file. I am not sure if I completely understood your last question. Best, Elyas Goli -- View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Error-using-Paraview-calculator-tp4855p4859.html Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com. From andy.bauer at kitware.com Thu Nov 3 13:41:07 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 3 Nov 2016 13:41:07 -0400 Subject: [Paraview-developers] Error using Paraview calculator In-Reply-To: <1478194667650-4859.post@n6.nabble.com> References: <1478190661529-4855.post@n6.nabble.com> <1478194004999-4857.post@n6.nabble.com> <1478194667650-4859.post@n6.nabble.com> Message-ID: Ok, this should be fixed in the upcoming 5.2 release on Linux. You can download ParaView from www.paraview.org/download but it sounds like you installed ParaView from a Linux package manager which are sometimes fairly far behind the latest stable release. On Thu, Nov 3, 2016 at 1:37 PM, egoli2 wrote: > Linux OS and version 3.98.1 64-bit. I am using paraview to read a .e data > file. I am not sure if I completely understood your last question. > > Best, > Elyas Goli > > > > -- > View this message in context: http://the-unofficial- > paraview-developers-forum.34153.x6.nabble.com/Error- > using-Paraview-calculator-tp4855p4859.html > Sent from the The Unofficial ParaView Developers Forum mailing list > archive at Nabble.com. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Fri Nov 4 09:41:43 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Fri, 4 Nov 2016 09:41:43 -0400 Subject: [Paraview-developers] New build failure with 5.2.0-RC3 In-Reply-To: <20161031132234.GA5084@megas.kitware.com> References: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com> <20161031132234.GA5084@megas.kitware.com> Message-ID: Hi Orion, Just to clarify, you'll need to turn off VTK_USE_SYSTEM_GL2PS to get ParaView to build with its own internal version with the necessary patches. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Mon, Oct 31, 2016 at 9:22 AM, Ben Boeckel wrote: > On Sun, Oct 30, 2016 at 08:34:28 -0600, Orion Poplawski wrote: > > This appears to be new with RC3 (over RC2); > > VTK updated its GL2PS requirements; the patches we need has been > submitted upstream, but has not been released yet. > > http://www.geuz.org/pipermail/gl2ps/2016/000429.html > http://www.geuz.org/pipermail/gl2ps/2016/000424.html > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From orion at cora.nwra.com Fri Nov 4 10:33:45 2016 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 4 Nov 2016 08:33:45 -0600 Subject: [Paraview-developers] New build failure with 5.2.0-RC3 In-Reply-To: References: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com> <20161031132234.GA5084@megas.kitware.com> Message-ID: On 11/04/2016 07:41 AM, Chuck Atkins wrote: > Hi Orion, > > Just to clarify, you'll need to turn off VTK_USE_SYSTEM_GL2PS to get ParaView > to build with its own internal version with the necessary patches. Yup, got it. Thanks. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 http://www.nwra.com From orion at cora.nwra.com Fri Nov 4 14:04:59 2016 From: orion at cora.nwra.com (Orion Poplawski) Date: Fri, 4 Nov 2016 12:04:59 -0600 Subject: [Paraview-developers] New build failure with 5.2.0-RC3 In-Reply-To: <20161031132234.GA5084@megas.kitware.com> References: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com> <20161031132234.GA5084@megas.kitware.com> Message-ID: <2796d096-5d6d-4652-9572-88c438d4d6b5@cora.nwra.com> On 10/31/2016 07:22 AM, Ben Boeckel wrote: > On Sun, Oct 30, 2016 at 08:34:28 -0600, Orion Poplawski wrote: >> This appears to be new with RC3 (over RC2); > > VTK updated its GL2PS requirements; the patches we need has been > submitted upstream, but has not been released yet. > > http://www.geuz.org/pipermail/gl2ps/2016/000429.html > http://www.geuz.org/pipermail/gl2ps/2016/000424.html > > --Ben > One issue - later on in gl2ps development with revision 620: r620 | geuzaine | 2016-09-03 04:51:32 -0600 (Sat, 03 Sep 2016) | 2 lines new gl2psLineCap and gl2psLineJoin + fixed scaling of PDF images: patch from Pantxo Diribarne +/* referenced in the documentation, but not fully documented */ +GL2PSDLL_API GLint gl2psForceRasterPos(GL2PSvertex *vert); +GL2PSDLL_API void gl2psAddPolyPrimitive(GLshort type, GLshort numverts, + GL2PSvertex *verts, GLint offset, + GLfloat ofactor, GLfloat ounits, + GLushort pattern, GLint factor, + GLfloat width, GLint linecap, + GLint linejoin, char boundary); + /* undocumented */ GL2PSDLL_API GLint gl2psDrawImageMap(GLsizei width, GLsizei height, const GLfloat position[3], @@ -219,12 +241,6 @@ GL2PSDLL_API const char *gl2psGetFileExtension(GLint format); GL2PSDLL_API const char *gl2psGetFormatDescription(GLint format); GL2PSDLL_API GLint gl2psGetFileFormat(); -GL2PSDLL_API GLint gl2psForceRasterPos(GL2PSvertex *vert); -GL2PSDLL_API void gl2psAddPolyPrimitive(GLshort type, GLshort numverts, - GL2PSvertex *verts, GLint offset, - GLfloat ofactor, GLfloat ounits, - GLushort pattern, GLint factor, - GLfloat width, char boundary); the interface for gl2psAddPolyPrimitive was changed. I don't know if there has been any coordination around this or not. But obviously current VTK/paraview doesn't build with current gl2ps trunk. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion at nwra.com Boulder, CO 80301 http://www.nwra.com From david.lonie at kitware.com Fri Nov 4 14:43:21 2016 From: david.lonie at kitware.com (David Lonie) Date: Fri, 4 Nov 2016 14:43:21 -0400 Subject: [Paraview-developers] New build failure with 5.2.0-RC3 In-Reply-To: <2796d096-5d6d-4652-9572-88c438d4d6b5@cora.nwra.com> References: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com> <20161031132234.GA5084@megas.kitware.com> <2796d096-5d6d-4652-9572-88c438d4d6b5@cora.nwra.com> Message-ID: On Fri, Nov 4, 2016 at 2:04 PM, Orion Poplawski wrote: > On 10/31/2016 07:22 AM, Ben Boeckel wrote: > > On Sun, Oct 30, 2016 at 08:34:28 -0600, Orion Poplawski wrote: > >> This appears to be new with RC3 (over RC2); > > > > VTK updated its GL2PS requirements; the patches we need has been > > submitted upstream, but has not been released yet. > > > > http://www.geuz.org/pipermail/gl2ps/2016/000429.html > > http://www.geuz.org/pipermail/gl2ps/2016/000424.html > > > > --Ben > > > > One issue - later on in gl2ps development with revision 620: > Indeed it has, thanks for the heads up! We'll deal with that when gl2ps cuts a new release. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Sat Nov 5 06:53:16 2016 From: cornelis.bockemuehl at gmail.com (cobo) Date: Sat, 5 Nov 2016 03:53:16 -0700 (MST) Subject: [Paraview-developers] Filter/pipeline design question - any helpful hints? Message-ID: <1478343196722-4865.post@n6.nabble.com> Good morning all, Since a couple of weeks I am developing a set of custom filters for some speciai purpose, and it's amazing how quickly I could manage to achieve rather good results: add data attributes to models, convert from points to some grid, etc.! But now I want to perform some more complicated computations and visualize the results. Input to my filter is an unordered grid, with every cell having a couple of attributes. Coloring them by attribute nicely is a great built in feature of Paraview already! The filter will add one additional attribute (data array) to the model. This attribute is not really a number, but only "on" or "off", like 0 or 1. That's no problem. But in addition to visualizing ANY of the attributes I now want to have the possibility to visualize this new attribute with some kind of flag: some pattern, dot, frame on the cell faces that could be black or white, to be still easily visible among the colors that represent any other attribute. This pattern would be either on or off, depending on the new attribute. Actually I want to see this additional attribute even if I generate a cut through the model - which makes the job not easier.,. So far I understand that this is not currently an option in Paraviev, so some kind of "workaround" would be required, and I do not know which one would be best. Two variants I am thinking about, but both have their very clear disadvantages also. Both require the generation of a second 3d geometry from the first and contain only "items" (unordered grid cells of different size) at points where the new attribute is 1. >From then on I see two options: 1. Make this second model a completely independent second model, like a second output from the filter. The user would be able to turn it on or off, and color it in a completely independent way from the first. If both models would be turned on, it would look like there is the first model with some "patterns" on the faces - which is what I wanted to achieve. Disadvantage: If I apply a cut filter on the first model, the second would still be fully 3d - or I manage to apply another cut filter to it as well. For the user this is a bit tedious because he would have to manage the two cut planes such that they are identical. 2. Generate one single multi-part model, with the second just another "part" of the first. This solves the problem with the cut view, and it is still possible to turn visualization of the parts on or off individually. However, now I have a problem with the independent coloring of the two parts: So far I did not find a way to say that part 1 should be colored according to attribute X and part 2 should be colored in black, white or whatever else I would define. Another disadvantage of the second option is the fact that it generates a much more complex geometrical setup. I also tried already to achieve the coloring by using a 1-pixel texture for making part 2 all one color and exclude part 1 by simply not providing texture coordinates. This works, but disappears if I apply a cut, so not much gained in comparison to the much simpler option 1... 3. As a 3-rd option I could imagine that there are possibilities that I did not understand yet that would make my job much easier than I thought? 4. Derive a new cut filter that takes two input ports and works on both simultaneously...(??) It is to say that I am an experienced programmer (which is why I am so quickly "starting" with paraview filters), but I am still rather new to paraview, reading a lot in the docs, trying around... Thanks for any helpful hints, considerations or tipps! Cornelis -- View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Filter-pipeline-design-question-any-helpful-hints-tp4865.html Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com. From utkarsh.ayachit at kitware.com Sun Nov 6 10:28:21 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 6 Nov 2016 10:28:21 -0500 Subject: [Paraview-developers] Filter/pipeline design question - any helpful hints? In-Reply-To: <1478343196722-4865.post@n6.nabble.com> References: <1478343196722-4865.post@n6.nabble.com> Message-ID: Cornelis, Option 2 is probably the easiest. As for each of the disadvantages for that option you mention, here's some more info: > However, > now I have a problem with the independent coloring of the two parts: So far > I did not find a way to say that part 1 should be colored according to > attribute X and part 2 should be colored in black, white or whatever else I > would define. Multiple options for this: 1. For part 2, remove all attribute arrays. Now when you choose to color by attribute X, since X is missing on part 2, ParaView will simply color by the solid color set before choosing the attribute to color with. 2. Use the "Multiblock Inspector" [a] to manually set the solid color to use for specific part/block. When such a color is specified, the attribute chosen is ignored. This does need to be set after each filter application, however. > Another disadvantage of the second option is the fact that it generates a > much more complex geometrical setup. Can you elaborate what you mean by that? Utkarsh [a]: https://blog.kitware.com/color-multiblock-datasets/ > > 3. As a 3-rd option I could imagine that there are possibilities that I did > not understand yet that would make my job much easier than I thought? > > 4. Derive a new cut filter that takes two input ports and works on both > simultaneously...(??) > > It is to say that I am an experienced programmer (which is why I am so > quickly "starting" with paraview filters), but I am still rather new to > paraview, reading a lot in the docs, trying around... > > Thanks for any helpful hints, considerations or tipps! > Cornelis > > > > -- > View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Filter-pipeline-design-question-any-helpful-hints-tp4865.html > Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers From cornelis.bockemuehl at gmail.com Sun Nov 6 16:41:11 2016 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Sun, 6 Nov 2016 22:41:11 +0100 Subject: [Paraview-developers] Filter/pipeline design question - any helpful hints? In-Reply-To: References: <1478343196722-4865.post@n6.nabble.com> Message-ID: Thanks a lot for that quick and precise answer - and this even in the middle of the Sunday! Looks like indeed the "multiblock inspector" is doing what I need, so "option 2" comes obviously closest to what I want, so I will certainly go for that solution. Is there a way to include some "color hint" already in the data file, like "preferred color for part 2 would be red" etc.? My guess is that it is not - because it contradicts a bit the "paraview philosophy" that is to my understanding: define geometry and data in the data files, then define the details of the view interactively. Regards, Cornelis 2016-11-06 16:28 GMT+01:00 Utkarsh Ayachit : > Cornelis, > > Option 2 is probably the easiest. As for each of the disadvantages for > that option you mention, here's some more info: > > > However, > > now I have a problem with the independent coloring of the two parts: So > far > > I did not find a way to say that part 1 should be colored according to > > attribute X and part 2 should be colored in black, white or whatever > else I > > would define. > > Multiple options for this: > 1. For part 2, remove all attribute arrays. Now when you choose to > color by attribute X, since X is missing on part 2, ParaView will > simply color by the solid color set before choosing the attribute to > color with. > 2. Use the "Multiblock Inspector" [a] to manually set the solid color > to use for specific part/block. When such a color is specified, the > attribute chosen is ignored. This does need to be set after each > filter application, however. > > > Another disadvantage of the second option is the fact that it generates a > > much more complex geometrical setup. > > Can you elaborate what you mean by that? > > Utkarsh > > [a]: https://blog.kitware.com/color-multiblock-datasets/ > > > > > 3. As a 3-rd option I could imagine that there are possibilities that I > did > > not understand yet that would make my job much easier than I thought? > > > > 4. Derive a new cut filter that takes two input ports and works on both > > simultaneously...(??) > > > > It is to say that I am an experienced programmer (which is why I am so > > quickly "starting" with paraview filters), but I am still rather new to > > paraview, reading a lot in the docs, trying around... > > > > Thanks for any helpful hints, considerations or tipps! > > Cornelis > > > > > > > > -- > > View this message in context: http://the-unofficial- > paraview-developers-forum.34153.x6.nabble.com/Filter- > pipeline-design-question-any-helpful-hints-tp4865.html > > Sent from the The Unofficial ParaView Developers Forum mailing list > archive at Nabble.com. > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Sun Nov 6 16:51:37 2016 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Sun, 6 Nov 2016 22:51:37 +0100 Subject: [Paraview-developers] Filter/pipeline design question - any helpful hints? In-Reply-To: References: <1478343196722-4865.post@n6.nabble.com> Message-ID: And regarding the "more complex geometrical setup" I was not sure whether saving the data to some simple table (CSV) might be more difficult, because there would be one part with associated data arrays and another one without... Now I simply created a test object with the characteristics manually - and I realized that things are much more easy: Exporting "cell data" to CSV simply creates two tables - one with the data I would need to export, and a second one that can be deleted. Regards, Cornelis 2016-11-06 22:41 GMT+01:00 Cornelis Bockem?hl : > Thanks a lot for that quick and precise answer - and this even in the > middle of the Sunday! > > Looks like indeed the "multiblock inspector" is doing what I need, so > "option 2" comes obviously closest to what I want, so I will certainly go > for that solution. > > Is there a way to include some "color hint" already in the data file, like > "preferred color for part 2 would be red" etc.? > > My guess is that it is not - because it contradicts a bit the "paraview > philosophy" that is to my understanding: define geometry and data in the > data files, then define the details of the view interactively. > > Regards, Cornelis > > > 2016-11-06 16:28 GMT+01:00 Utkarsh Ayachit : > >> Cornelis, >> >> Option 2 is probably the easiest. As for each of the disadvantages for >> that option you mention, here's some more info: >> >> > However, >> > now I have a problem with the independent coloring of the two parts: So >> far >> > I did not find a way to say that part 1 should be colored according to >> > attribute X and part 2 should be colored in black, white or whatever >> else I >> > would define. >> >> Multiple options for this: >> 1. For part 2, remove all attribute arrays. Now when you choose to >> color by attribute X, since X is missing on part 2, ParaView will >> simply color by the solid color set before choosing the attribute to >> color with. >> 2. Use the "Multiblock Inspector" [a] to manually set the solid color >> to use for specific part/block. When such a color is specified, the >> attribute chosen is ignored. This does need to be set after each >> filter application, however. >> >> > Another disadvantage of the second option is the fact that it generates >> a >> > much more complex geometrical setup. >> >> Can you elaborate what you mean by that? >> >> Utkarsh >> >> [a]: https://blog.kitware.com/color-multiblock-datasets/ >> >> > >> > 3. As a 3-rd option I could imagine that there are possibilities that I >> did >> > not understand yet that would make my job much easier than I thought? >> > >> > 4. Derive a new cut filter that takes two input ports and works on both >> > simultaneously...(??) >> > >> > It is to say that I am an experienced programmer (which is why I am so >> > quickly "starting" with paraview filters), but I am still rather new to >> > paraview, reading a lot in the docs, trying around... >> > >> > Thanks for any helpful hints, considerations or tipps! >> > Cornelis >> > >> > >> > >> > -- >> > View this message in context: http://the-unofficial-paraview >> -developers-forum.34153.x6.nabble.com/Filter-pipeline- >> design-question-any-helpful-hints-tp4865.html >> > Sent from the The Unofficial ParaView Developers Forum mailing list >> archive at Nabble.com. >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > > -- > Cornelis Bockem?hl > Basel, Schweiz > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Mon Nov 7 05:43:23 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Mon, 7 Nov 2016 16:13:23 +0530 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype Message-ID: HI All, I am trying to build ParaView 5.2 in Ubuntu 16.04 using superbuild. My compilation crashes with issues related to "freetype" libraries. I can find that many other users/developers also faced similar issues. However, I could not find a solution. Any help? Attached here is the screenshot of the error messages. [image: Inline image 1] Thanks, Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 88656 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Mon Nov 7 09:44:41 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 7 Nov 2016 09:44:41 -0500 Subject: [Paraview-developers] Filter/pipeline design question - any helpful hints? In-Reply-To: References: <1478343196722-4865.post@n6.nabble.com> Message-ID: > Is there a way to include some "color hint" already in the data file, like > "preferred color for part 2 would be red" etc.? > My guess is that it is not - because it contradicts a bit the "paraview > philosophy" that is to my understanding: define geometry and data in the > data files, then define the details of the view interactively. You guessed it right :). But don't let that stop you providing such metadata (say as arrays in field data) and create a plugin, for example, or a toolbar button that when clicked uses that meta-data to setup the coloring. From cory.quammen at kitware.com Mon Nov 7 10:25:14 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 7 Nov 2016 10:25:14 -0500 Subject: [Paraview-developers] ParaView 5.2.0-RC4 tagged Message-ID: Folks, v5.2.0-RC4 has just been tagged. Please do not merge anything into `master` until the dashboards have cycled through and built the binaries for this version. I'll send an email when it is okay to merge to `master` again. Note that this is the last scheduled release candidate before the final 5.2 release this Friday, November 11. Thanks, Cory -- Cory Quammen Staff R&D Engineer Kitware, Inc. From sur.chiranjib at gmail.com Tue Nov 8 04:22:16 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Tue, 8 Nov 2016 01:22:16 -0800 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype In-Reply-To: References: Message-ID: I thought of attaching the CMakeCache.txt file in case if this file can be used to traceback the issue. FYI, I have installed libfreetype6 and libfreetype6-dev in my Ubuntu 16.04. I am missing something which I am not able to figure out. Thanks, Chiranjib On Mon, Nov 7, 2016 at 2:43 AM, Chiranjib Sur wrote: > HI All, > I am trying to build ParaView 5.2 in Ubuntu 16.04 using superbuild. My > compilation crashes with issues related to "freetype" libraries. > I can find that many other users/developers also faced similar issues. > However, I could not find a solution. > > Any help? > > Attached here is the screenshot of the error messages. > > [image: Inline image 1] > > Thanks, > Chiranjib > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 88656 bytes Desc: not available URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /home/csur/Work/paraview-build # It was generated by CMake: /home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Enable shared libraries BUILD_SHARED_LIBS:BOOL=ON //Build testing BUILD_TESTING:BOOL=OFF //Path to a program. BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //The build mode CMAKE_BUILD_TYPE:STRING=Release //The build type for the paraview project. CMAKE_BUILD_TYPE_paraview:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/home/csur/Work/paraview-build/install //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy //Path to a program. CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=paraview-superbuild //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Path to the coverage program that CTest uses for performing coverage // inspection COVERAGE_COMMAND:FILEPATH=/usr/bin/gcov //Extra command line flags to pass to the coverage tool COVERAGE_EXTRA_FLAGS:STRING=-l //How many times to retry timed-out CTest submissions. CTEST_SUBMIT_RETRY_COUNT:STRING=3 //How long to wait between timed-out CTest submissions. CTEST_SUBMIT_RETRY_DELAY:STRING=5 //Path to a program. CVSCOMMAND:FILEPATH=CVSCOMMAND-NOTFOUND //Options passed to the cvs update command. CVS_UPDATE_OPTIONS:STRING=-d -A -P //Maximum time allowed before CTest will kill the test. DART_TESTING_TIMEOUT:STRING=1500 //Request to build project adios ENABLE_adios:BOOL=OFF //Request to build project boost ENABLE_boost:BOOL=OFF //Request to build project catalyst ENABLE_catalyst:BOOL=OFF //Request to build project cgns ENABLE_cgns:BOOL=OFF //Request to build project cosmotools ENABLE_cosmotools:BOOL=OFF //Request to build project cxx11 ENABLE_cxx11:BOOL=OFF //Request to build project egl ENABLE_egl:BOOL=OFF //Request to build project ffmpeg ENABLE_ffmpeg:BOOL=OFF //Request to build project fontconfig ENABLE_fontconfig:BOOL=OFF //Request to build project freetype ENABLE_freetype:BOOL=OFF //Request to build project genericio ENABLE_genericio:BOOL=OFF //Request to build project glu ENABLE_glu:BOOL=OFF //Request to build project hdf5 ENABLE_hdf5:BOOL=OFF //Request to build project ispc ENABLE_ispc:BOOL=OFF //Request to build project libxml2 ENABLE_libxml2:BOOL=OFF //Request to build project llvm ENABLE_llvm:BOOL=OFF //Request to build project matplotlib ENABLE_matplotlib:BOOL=OFF //Request to build project mesa ENABLE_mesa:BOOL=OFF //Request to build project mpi ENABLE_mpi:BOOL=OFF //Request to build project mxml ENABLE_mxml:BOOL=OFF //Request to build project netcdf ENABLE_netcdf:BOOL=OFF //Request to build project numpy ENABLE_numpy:BOOL=OFF //Request to build project osmesa ENABLE_osmesa:BOOL=OFF //Request to build project ospray ENABLE_ospray:BOOL=OFF //Request to build project paraview ENABLE_paraview:BOOL=ON //Request to build project paraviewgettingstartedguide ENABLE_paraviewgettingstartedguide:BOOL=OFF //Request to build project paraviewsdk ENABLE_paraviewsdk:BOOL=OFF //Request to build project paraviewtutorial ENABLE_paraviewtutorial:BOOL=OFF //Request to build project paraviewtutorialdata ENABLE_paraviewtutorialdata:BOOL=OFF //Request to build project paraviewusersguide ENABLE_paraviewusersguide:BOOL=OFF //Request to build project paraviewweb ENABLE_paraviewweb:BOOL=OFF //Request to build project paraviewweblightviz ENABLE_paraviewweblightviz:BOOL=OFF //Request to build project paraviewwebvisualizer ENABLE_paraviewwebvisualizer:BOOL=OFF //Request to build project portfwd ENABLE_portfwd:BOOL=OFF //Request to build project python ENABLE_python:BOOL=ON //Request to build project pythonsetuptools ENABLE_pythonsetuptools:BOOL=OFF //Request to build project qt4 ENABLE_qt4:BOOL=ON //Request to build project qt5 ENABLE_qt5:BOOL=OFF //Request to build project silo ENABLE_silo:BOOL=OFF //Request to build project szip ENABLE_szip:BOOL=OFF //Request to build project tbb ENABLE_tbb:BOOL=OFF //Request to build project visitbridge ENABLE_visitbridge:BOOL=OFF //Request to build project vortexfinder2 ENABLE_vortexfinder2:BOOL=OFF //Request to build project vrpn ENABLE_vrpn:BOOL=OFF //Request to build project xdmf3 ENABLE_xdmf3:BOOL=OFF //Request to build project zlib ENABLE_zlib:BOOL=ON //Path to a program. GITCOMMAND:FILEPATH=/usr/bin/git //Git command line client GIT_EXECUTABLE:FILEPATH=/usr/bin/git //Path to a program. HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND //Command to build the project MAKECOMMAND:STRING=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" //Path to the memory checking command, used for memory error detection. MEMORYCHECK_COMMAND:FILEPATH=MEMORYCHECK_COMMAND-NOTFOUND //File that contains suppressions for the memory checker MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH= //Path to a program. P4COMMAND:FILEPATH=P4COMMAND-NOTFOUND //ParaView's build mode PARAVIEW_BUILD_TYPE:STRING= //Build documentation for the web PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF //The catalyst edition to build PARAVIEW_CATALYST_EDITION:STRING=Essentials //Enable Python support in catalyst PARAVIEW_CATALYST_PYTHON:BOOL=ON //Default to using the system OpenGL PARAVIEW_DEFAULT_SYSTEM_GL:BOOL=OFF //A list of projects for ParaView to depend on PARAVIEW_EXTERNAL_PROJECTS:STRING= //Extra arguments to be passed to ParaView when configuring. PARAVIEW_EXTRA_CMAKE_ARGUMENTS:STRING= //Freeze Python packages and modules into the application PARAVIEW_FREEZE_PYTHON:BOOL=OFF //If set, overrides the generated filename for the package PARAVIEW_PACKAGE_FILE_NAME:STRING= //String to use as a suffix for generated packages PARAVIEW_PACKAGE_SUFFIX:STRING= //Rendering backend to use for ParaView PARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 //The default version of ParaView to use if it can't be auto-determined PARAVIEW_VERSION_DEFAULT:STRING=5.2.0-RC3 PARAVIEW_WEB_TEST_REMOTE:BOOL=OFF //Pass LD_LIBRARY_PATH to build scripts PASS_LD_LIBRARY_PATH_FOR_BUILDS:BOOL=ON //Path to a program. ProcessorCount_cmd_getconf:FILEPATH=/usr/bin/getconf //Path to a program. ProcessorCount_cmd_sysctl:FILEPATH=/sbin/sysctl //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qdbuscpp2xml //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qdbusxml2cpp //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/designer //The location of the Qt docs QT_DOC_DIR:PATH=/usr/share/qt4/doc //The location of the Qt imports QT_IMPORTS_DIR:PATH=QT_IMPORTS_DIR-NOTFOUND //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/linguist //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/lrelease //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/lupdate //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/usr/share/qt4/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/moc //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libphononwidgets.so //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=/usr/include/qt4/phonon //The Qt PHONON library QT_PHONON_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libphonon.so //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libphonon.so //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/usr/lib/x86_64-linux-gnu/qt4/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qcollectiongenerator //Path to a library. QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libqdeclarativeview.so //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/bearer/libqgenericbearer.so //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqgif.so //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/graphicssystems/libqglgraphicssystem.so //Path to a library. QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QICO_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqico.so //Path to a library. QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqjpcodecs.so //Path to a library. QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqjpeg.so //Path to a library. QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqkrcodecs.so //The qmake executable for the Qt installation to use QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake //Path to a library. QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QMNG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/sqldrivers/libqsqlite.so //Path to a library. QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLPSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so //Path to a library. QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqsvg.so //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/usr/include/qt4/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQt3Support.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=QT_QT3SUPPORT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQt3Support.so //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/accessible/libqtaccessiblecompatwidgets.so //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtCLucene.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=QT_QTCLUCENE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/usr/include/qt4/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtCore.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=QT_QTCORE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=/usr/include/qt4/QtDBus //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDBus.so //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDBus.so //Path to a file. QT_QTDECLARATIVE_INCLUDE_DIR:PATH=/usr/include/qt4/QtDeclarative //The Qt QTDECLARATIVE library QT_QTDECLARATIVE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDeclarative.so //Path to a library. QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDeclarative.so //Path to a file. QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/usr/include/qt4/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDesignerComponents.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/usr/include/qt4/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDesigner.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNER_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDesigner.so //Path to a library. QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTGA_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtga.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/usr/include/qt4/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtGui.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=QT_QTGUI_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/usr/include/qt4/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtHelp.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=QT_QTHELP_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtHelp.so //Path to a library. QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so //Path to a file. QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND //The Qt QTMOTIF library QT_QTMOTIF_LIBRARY:STRING= //Path to a library. QT_QTMOTIF_LIBRARY_DEBUG:FILEPATH=QT_QTMOTIF_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMOTIF_LIBRARY_RELEASE:FILEPATH=QT_QTMOTIF_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=QT_QTMULTIMEDIA_INCLUDE_DIR-NOTFOUND //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING= //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/usr/include/qt4/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtNetwork.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=QT_QTNETWORK_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtNetwork.so //Path to a file. QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND //The Qt QTNSPLUGIN library QT_QTNSPLUGIN_LIBRARY:STRING= //Path to a library. QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTOPENGL_INCLUDE_DIR:PATH=/usr/include/qt4/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtOpenGL.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=QT_QTOPENGL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtOpenGL.so //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/graphicssystems/libqtracegraphicssystem.so //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/script/libqtscriptdbus.so //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/usr/include/qt4/QtScriptTools //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtScriptTools.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtScriptTools.so //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=/usr/include/qt4/QtScript //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtScript.so //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtScript.so //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/usr/include/qt4/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtSql.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=QT_QTSQL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=/usr/include/qt4/QtSvg //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtSvg.so //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=QT_QTSVG_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtSvg.so //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/usr/include/qt4/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtTest.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=QT_QTTEST_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/usr/include/qt4/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtUiTools.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTUITOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtUiTools.a //Path to a library. QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqtwcodecs.so //Path to a file. QT_QTWEBKIT_INCLUDE_DIR:PATH=/usr/include/qt4/QtWebKit //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtWebKit.so //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtWebKit.so //Path to a file. QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=/usr/include/qt4/QtXmlPatterns //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/usr/include/qt4/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtXml.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=QT_QTXML_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtXml.so //Path to a library. QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=QT_QWEBVIEW_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_RCC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/rcc //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_RELEASE-NOTFOUND //The location of the Qt translations QT_TRANSLATIONS_DIR:PATH=/usr/share/qt4/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/uic //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to scp command, used by CTest for submitting results to // a Dart server SCPCOMMAND:FILEPATH=/usr/bin/scp //Path to a program. SED_EXECUTABLE:FILEPATH=/bin/sed //Name of the computer/site where compile is being run SITE:STRING=ubuntu //Path to the SLURM sbatch executable SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND //Path to the SLURM srun executable SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND //The package to install by default SUPERBUILD_DEFAULT_INSTALL:STRING=paraview/TGZ //Do not update git repositories during the build SUPERBUILD_OFFLINE_BUILD:BOOL=OFF //Number of jobs to use when compiling subprojects SUPERBUILD_PROJECT_PARALLELISM:STRING=1 //Suppress output for bzip2 SUPPRESS_bzip2_OUTPUT:BOOL=OFF //Suppress output for fontconfig SUPPRESS_fontconfig_OUTPUT:BOOL=OFF //Suppress output for freetype SUPPRESS_freetype_OUTPUT:BOOL=OFF //Suppress output for libxml2 SUPPRESS_libxml2_OUTPUT:BOOL=OFF //Suppress output for paraview SUPPRESS_paraview_OUTPUT:BOOL=OFF //Suppress output for png SUPPRESS_png_OUTPUT:BOOL=OFF //Suppress output for python SUPPRESS_python_OUTPUT:BOOL=OFF //Suppress output for qt4 SUPPRESS_qt4_OUTPUT:BOOL=OFF //Suppress output for zlib SUPPRESS_zlib_OUTPUT:BOOL=OFF //Path to a program. SVNCOMMAND:FILEPATH=SVNCOMMAND-NOTFOUND //Enable the non-free parts of the superbuild USE_NONFREE_COMPONENTS:BOOL=OFF USE_SYSTEM_bzip2:BOOL=OFF USE_SYSTEM_freetype:BOOL=OFF USE_SYSTEM_libxml2:BOOL=OFF USE_SYSTEM_png:BOOL=OFF USE_SYSTEM_python:BOOL=OFF USE_SYSTEM_qt4:BOOL=ON USE_SYSTEM_zlib:BOOL=OFF //The source selection for mesa mesa_SOURCE_SELECTION:STRING=v13.0.0 //Enable the OpenSWR driver mesa_USE_SWR:BOOL=ON //Target ISA for OSPRay (SSE, AVX, AVX2, AVX512, or ALL). ospray_BUILD_ISA:STRING=ALL //Value Computed by CMake paraview-superbuild_BINARY_DIR:STATIC=/home/csur/Work/paraview-build //Value Computed by CMake paraview-superbuild_SOURCE_DIR:STATIC=/home/csur/Software/ParaView-superbuild //If enabled, fetch sources from GIT paraview_FROM_GIT:BOOL=ON //GIT_REPOSITORY for project 'paraview' paraview_GIT_REPOSITORY:STRING=https://gitlab.kitware.com/paraview/paraview.git //GIT_TAG for project 'paraview' paraview_GIT_TAG:STRING=origin/master //Build Qt with OpenSSL support qt4_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt4 when configuring. qt4_EXTRA_CONFIGURATION_OPTIONS:STRING= //Work around a build issue in Qt. Use this if you see linker errors // with QtHelp and QCLucene. qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD:BOOL=OFF //Build with OpenSSL support. Requires system-installed OpenSSL // at runtime. qt5_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt when configuring. qt5_EXTRA_CONFIGURATION_OPTIONS:STRING= //Location for downloaded source tarballs superbuild_download_location:PATH=/home/csur/Work/paraview-build/downloads //Arguments to pass to git clone superbuild_git_clone_arguments:STRING=--progress ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: BUILD_TESTING BUILD_TESTING-MODIFIED:INTERNAL=ON //ADVANCED property for variable: BZRCOMMAND BZRCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-ADVANCED:INTERNAL=1 //STRINGS property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Release;RelWithDebInfo;Debug //STRINGS property for variable: CMAKE_BUILD_TYPE_paraview CMAKE_BUILD_TYPE_paraview-STRINGS:INTERNAL=;Release;RelWithDebInfo;Debug //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/home/csur/Work/paraview-build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=7 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/home/csur/Software/ParaView-superbuild //MODIFIED property for variable: CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX-MODIFIED:INTERNAL=ON //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/share/cmake-3.7 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_COMMAND COVERAGE_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_EXTRA_FLAGS COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVSCOMMAND CVSCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVS_UPDATE_OPTIONS CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: DART_TESTING_TIMEOUT DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1 //Request to build project bzip2 ENABLE_bzip2:INTERNAL=OFF //Request to build project png ENABLE_png:INTERNAL=OFF //MODIFIED property for variable: ENABLE_python ENABLE_python-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_qt4 ENABLE_qt4-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_zlib ENABLE_zlib-MODIFIED:INTERNAL=ON //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v2.7.4()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/usr/bin/qmake][/usr/lib/x86_64-linux-gnu/qt4/bin/moc][/usr/lib/x86_64-linux-gnu/qt4/bin/rcc][/usr/lib/x86_64-linux-gnu/qt4/bin/uic][/usr/include/qt4][/usr/lib/x86_64-linux-gnu][/usr/lib/x86_64-linux-gnu/libQtCore.so][v4.8.7()] //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HAVE_void_ptr_size:INTERNAL=TRUE //ADVANCED property for variable: HGCOMMAND HGCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MAKECOMMAND MAKECOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_COMMAND MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: P4COMMAND P4COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_TYPE PARAVIEW_BUILD_TYPE-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_CATALYST_EDITION PARAVIEW_CATALYST_EDITION-STRINGS:INTERNAL=Essentials;Extras;Rendering-Base //ADVANCED property for variable: PARAVIEW_EXTERNAL_PROJECTS PARAVIEW_EXTERNAL_PROJECTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTRA_CMAKE_ARGUMENTS PARAVIEW_EXTRA_CMAKE_ARGUMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_PACKAGE_SUFFIX PARAVIEW_PACKAGE_SUFFIX-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_RENDERING_BACKEND PARAVIEW_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2 //ADVANCED property for variable: PARAVIEW_VERSION_DEFAULT PARAVIEW_VERSION_DEFAULT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PASS_LD_LIBRARY_PATH_FOR_BUILDS PASS_LD_LIBRARY_PATH_FOR_BUILDS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_getconf ProcessorCount_cmd_getconf-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_sysctl ProcessorCount_cmd_sysctl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_BINARY_DIR:INTERNAL=/usr/lib/x86_64-linux-gnu/qt4/bin //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DESIGNER_EXECUTABLE QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DOC_DIR QT_DOC_DIR-ADVANCED:INTERNAL=1 QT_HEADERS_DIR:INTERNAL=/usr/include/qt4 //ADVANCED property for variable: QT_IMPORTS_DIR QT_IMPORTS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LIBRARY_DIR QT_LIBRARY_DIR-ADVANCED:INTERNAL=1 //Qt library dir QT_LIBRARY_DIR:INTERNAL=/usr/lib/x86_64-linux-gnu //ADVANCED property for variable: QT_LINGUIST_EXECUTABLE QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LRELEASE_EXECUTABLE QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LUPDATE_EXECUTABLE QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MKSPECS_DIR QT_MKSPECS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MOC_EXECUTABLE QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_INCLUDE_DIR QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PLUGINS_DIR QT_PLUGINS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/usr/bin/qmake //ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_INCLUDE_DIR QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_DEBUG QT_QTMOTIF_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_RELEASE QT_QTMOTIF_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_INCLUDE_DIR QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_RCC_EXECUTABLE QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TRANSLATIONS_DIR QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC3_EXECUTABLE QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC_EXECUTABLE QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //Have symbol Q_WS_MAC Q_WS_MAC:INTERNAL= //Have symbol Q_WS_QWS Q_WS_QWS:INTERNAL= //Have symbol Q_WS_WIN Q_WS_WIN:INTERNAL= //Have symbol Q_WS_X11 Q_WS_X11:INTERNAL=1 //ADVANCED property for variable: SCPCOMMAND SCPCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SED_EXECUTABLE SED_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SITE SITE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SBATCH_COMMAND SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SRUN_COMMAND SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1 //STRINGS property for variable: SUPERBUILD_DEFAULT_INSTALL SUPERBUILD_DEFAULT_INSTALL-STRINGS:INTERNAL=paraview/TGZ;catalyst/TGZ //ADVANCED property for variable: SUPERBUILD_PROJECT_PARALLELISM SUPERBUILD_PROJECT_PARALLELISM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_bzip2_OUTPUT SUPPRESS_bzip2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_fontconfig_OUTPUT SUPPRESS_fontconfig_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_freetype_OUTPUT SUPPRESS_freetype_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_libxml2_OUTPUT SUPPRESS_libxml2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_paraview_OUTPUT SUPPRESS_paraview_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_png_OUTPUT SUPPRESS_png_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_python_OUTPUT SUPPRESS_python_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_qt4_OUTPUT SUPPRESS_qt4_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_zlib_OUTPUT SUPPRESS_zlib_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SVNCOMMAND SVNCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: USE_NONFREE_COMPONENTS USE_NONFREE_COMPONENTS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: USE_SYSTEM_qt4 USE_SYSTEM_qt4-MODIFIED:INTERNAL=ON //STRINGS property for variable: mesa_SOURCE_SELECTION mesa_SOURCE_SELECTION-STRINGS:INTERNAL=v12.0.3;v13.0.0 //ADVANCED property for variable: mesa_USE_SWR mesa_USE_SWR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-ADVANCED:INTERNAL=1 //STRINGS property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-STRINGS:INTERNAL=SSE;AVX;AVX2;AVX512;ALL //ADVANCED property for variable: paraview_GIT_REPOSITORY paraview_GIT_REPOSITORY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: paraview_GIT_TAG paraview_GIT_TAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_ENABLE_OPENSSL qt4_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_EXTRA_CONFIGURATION_OPTIONS qt4_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_ENABLE_OPENSSL qt5_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_EXTRA_CONFIGURATION_OPTIONS qt5_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: superbuild_download_location superbuild_download_location-ADVANCED:INTERNAL=1 //ADVANCED property for variable: superbuild_git_clone_arguments superbuild_git_clone_arguments-ADVANCED:INTERNAL=1 superbuild_python_executable:INTERNAL=/home/csur/Work/paraview-build/install/bin/python //CHECK_TYPE_SIZE: sizeof(void*) void_ptr_size:INTERNAL=8 From ben.boeckel at kitware.com Tue Nov 8 07:37:46 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 8 Nov 2016 07:37:46 -0500 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype In-Reply-To: References: Message-ID: <20161108123746.GA19072@megas.kitware.com> On Tue, Nov 08, 2016 at 01:22:16 -0800, Chiranjib Sur wrote: > I thought of attaching the CMakeCache.txt file in case if this file can be > used to traceback the issue. > # This is the CMakeCache file. > //Request to build project freetype > ENABLE_freetype:BOOL=OFF The superbuild should not be using an external freetype at all; instead is it likely using the one VTK ships inside of it. Try setting this and if that fails too, try setting: > USE_SYSTEM_freetype:BOOL=OFF to `ON` to use the system freetype from Ubuntu; otherwise it will be built by the superbuild. --Ben From cory.quammen at kitware.com Tue Nov 8 10:21:48 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Nov 2016 10:21:48 -0500 Subject: [Paraview-developers] ParaView 5.2.0-RC4 tagged In-Reply-To: References: Message-ID: All the binaries for RC4 have been built. Please feel free to merge to ParaView's master branch again. Thanks, Cory On Mon, Nov 7, 2016 at 10:25 AM, Cory Quammen wrote: > Folks, > > v5.2.0-RC4 has just been tagged. Please do not merge anything into > `master` until the dashboards have cycled through and built the > binaries for this version. > > I'll send an email when it is okay to merge to `master` again. > > Note that this is the last scheduled release candidate before the > final 5.2 release this Friday, November 11. > > Thanks, > Cory > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Tue Nov 8 14:33:30 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 8 Nov 2016 14:33:30 -0500 Subject: [Paraview-developers] ParaView 5.2.0-RC4 tagged In-Reply-To: References: Message-ID: Folks, There was a packaging problem with the Windows builds that has been resolved. Please hold off on merging into ParaView master until we have rebuilt the Windows packages. Thanks, Cory On Tue, Nov 8, 2016 at 10:21 AM, Cory Quammen wrote: > All the binaries for RC4 have been built. Please feel free to merge to > ParaView's master branch again. > > Thanks, > Cory > > On Mon, Nov 7, 2016 at 10:25 AM, Cory Quammen wrote: >> Folks, >> >> v5.2.0-RC4 has just been tagged. Please do not merge anything into >> `master` until the dashboards have cycled through and built the >> binaries for this version. >> >> I'll send an email when it is okay to merge to `master` again. >> >> Note that this is the last scheduled release candidate before the >> final 5.2 release this Friday, November 11. >> >> Thanks, >> Cory >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Wed Nov 9 13:48:20 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 9 Nov 2016 13:48:20 -0500 Subject: [Paraview-developers] ParaView 5.2.0-RC4 tagged In-Reply-To: References: Message-ID: Merging to master is now okay again. Thanks for your patience. Cory On Tue, Nov 8, 2016 at 2:33 PM, Cory Quammen wrote: > Folks, > > There was a packaging problem with the Windows builds that has been > resolved. Please hold off on merging into ParaView master until we > have rebuilt the Windows packages. > > Thanks, > Cory > > On Tue, Nov 8, 2016 at 10:21 AM, Cory Quammen wrote: >> All the binaries for RC4 have been built. Please feel free to merge to >> ParaView's master branch again. >> >> Thanks, >> Cory >> >> On Mon, Nov 7, 2016 at 10:25 AM, Cory Quammen wrote: >>> Folks, >>> >>> v5.2.0-RC4 has just been tagged. Please do not merge anything into >>> `master` until the dashboards have cycled through and built the >>> binaries for this version. >>> >>> I'll send an email when it is okay to merge to `master` again. >>> >>> Note that this is the last scheduled release candidate before the >>> final 5.2 release this Friday, November 11. >>> >>> Thanks, >>> Cory >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From sur.chiranjib at gmail.com Thu Nov 10 05:46:33 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Thu, 10 Nov 2016 16:16:33 +0530 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype In-Reply-To: <20161108123746.GA19072@megas.kitware.com> References: <20161108123746.GA19072@megas.kitware.com> Message-ID: Ben, Thanks much. I am able to build ParaView now after setting this switch ENABLE_freetype:BOOL=OFF to ON. However, I am now facing difficulties in building (in Ubuntu) my custom plugin which builds/work fine in RHEL. It's throwing some compilation error which I am debugging currently. One other thing I have observed. After the "make" is executed successfully for the superbuild, the directory structure is not the same that is being produced earlier. Is there a change in structure now? Chiranjib On Tue, Nov 8, 2016 at 6:07 PM, Ben Boeckel wrote: > On Tue, Nov 08, 2016 at 01:22:16 -0800, Chiranjib Sur wrote: > > I thought of attaching the CMakeCache.txt file in case if this file can > be > > used to traceback the issue. > > > # This is the CMakeCache file. > > > //Request to build project freetype > > ENABLE_freetype:BOOL=OFF > > The superbuild should not be using an external freetype at all; instead > is it likely using the one VTK ships inside of it. Try setting this and > if that fails too, try setting: > > > USE_SYSTEM_freetype:BOOL=OFF > > to `ON` to use the system freetype from Ubuntu; otherwise it will be > built by the superbuild. > > --Ben > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Thu Nov 10 09:36:27 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Thu, 10 Nov 2016 09:36:27 -0500 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype In-Reply-To: References: <20161108123746.GA19072@megas.kitware.com> Message-ID: <20161110143627.GA30605@megas.kitware.com> On Thu, Nov 10, 2016 at 16:16:33 +0530, Chiranjib Sur wrote: > One other thing I have observed. After the "make" is executed successfully > for the superbuild, the directory structure is not the same that is being > produced earlier. Is there a change in structure now? Yes, the superbuild now uses a common infrastructure for superbuilds so that we may share it between multiple projects. The new structure is: builddir/ The superbuild's build directory. cpack/ Generated packaging projects (use via `ctest -R cpack-...`). downloads/ Default download directory. install/ Default staging install directory. superbuild/ Location used by the common infra for building $project/ Project directory. src/ Source tree for the project. build/ Build tree for the project. sb-$project-?.cmake Scripts used for the steps of $project. The infrastructure assumes it has full control of the superbuild/ directory, so anything done in there manually is prone to being wiped away by the build system (e.g., custom git commits may be dropped if the superbuild needs to reinitialize the source directory). If you need to use a custom source tree for a project, it is best to point the superbuild at an external source tree (which it will never try to update to any specific hash). This is supported for ParaView out of the box. In master: -Dparaview_SOURCE_SELECTION=source and with slightly older versions: -Dparaview_FROM_GIT=OFF -Dparaview_FROM_SOURCE_DIR=ON other projects require modifications to the versions.cmake file directly. --Ben From chuck.atkins at kitware.com Thu Nov 10 11:45:48 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Thu, 10 Nov 2016 11:45:48 -0500 Subject: [Paraview-developers] ParaView superbuild Installation - Linux issue with "freetype In-Reply-To: References: <20161108123746.GA19072@megas.kitware.com> Message-ID: Hi Chinranjib, If you're wanting to build plugins then you'll also want to make sure you have ENABLE_paraviewsdk=ON set. That should ensure the resulting "make install" will include the necessary headers and CMake files. ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Thu, Nov 10, 2016 at 5:46 AM, Chiranjib Sur wrote: > Ben, > Thanks much. I am able to build ParaView now after setting this switch > ENABLE_freetype:BOOL=OFF to ON. > However, I am now facing difficulties in building (in Ubuntu) my custom > plugin which builds/work fine in RHEL. It's throwing some compilation error > which I am debugging currently. > > One other thing I have observed. After the "make" is executed successfully > for the superbuild, the directory structure is not the same that is being > produced earlier. Is there a change in structure now? > > Chiranjib > > On Tue, Nov 8, 2016 at 6:07 PM, Ben Boeckel > wrote: > >> On Tue, Nov 08, 2016 at 01:22:16 -0800, Chiranjib Sur wrote: >> > I thought of attaching the CMakeCache.txt file in case if this file can >> be >> > used to traceback the issue. >> >> > # This is the CMakeCache file. >> >> > //Request to build project freetype >> > ENABLE_freetype:BOOL=OFF >> >> The superbuild should not be using an external freetype at all; instead >> is it likely using the one VTK ships inside of it. Try setting this and >> if that fails too, try setting: >> >> > USE_SYSTEM_freetype:BOOL=OFF >> >> to `ON` to use the system freetype from Ubuntu; otherwise it will be >> built by the superbuild. >> >> --Ben >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomasblome at startmail.com Thu Nov 10 13:10:25 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Thu, 10 Nov 2016 19:10:25 +0100 Subject: [Paraview-developers] Linker error building Fortran90FullExample In-Reply-To: References: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com> Message-ID: <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> Hi Andy, The linker error concerning the missing main method was due to a wrong solution setup of the Fortran90FullExample in VS. The CMakeLists file provided generates only one single (C++) project in VS, which means all .f90 files will be ignored by the compiler (it's impossible to have a single Fortran/C++ mixed language project in VS). To solve this I had to configure the CMakeLists file to create a library from FECxxAdaptor.cxx and link it with the Fortran90FullExample. Other linker & compiler errors occurred with regards to mpi: 1) the target_link_libraries command? in the CMakeLists file links ${MPI_Fortran_LIBRARIES} to the fortran project, but it forgets to link with msmpifec.lib (see also: http://public.kitware.com/pipermail/cmake/2016-February/062861.html). 2) The specification of an include directory (containing header mpifptr.h) was missing. Another problem arose when it comes to the the by hand name mangling for fortran in FECxxAdaptor.cxx. To get rid of that I introduced function interfaces in the FEFortranAdaptor.f90 file and now it works independently of the Fortran compiler used. Now, there are only five remaining linker errors as shown below: LNK2019: unresolved external symbol COPROCESS referenced in function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? LNK2019: unresolved external symbol COPROCESSORINITIALIZEWITHPYTHON referenced in function MAIN__?? ??? ?FEDriver.obj?? ??? ? LNK2019: unresolved external symbol COPROCESSORFINALIZE referenced in function MAIN__?? ??? ?FEDriver.obj?? ??? ? LNK2019: unresolved external symbol NEEDTOCREATEGRID referenced in function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? LNK2019: unresolved external symbol REQUESTDATADESCRIPTION referenced in function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj??? In the ParaViewCatalystUsersGuide_v2 the missing symbols appear to be declared in CAdaptorAPI.h and CPythonAdaptorAPI.h (but NEEDTOCREATEGRID), but I can't just include them in the Fortran code. Can you tell me how to resolve those missing references? Best, Thomas ? Am Mittwoch, 26. Oktober 2016 18:47 schrieb Andy Bauer : ? > Hi Thomas, > ? > I really don't know about this. Do you get the same behavior if you > don't link with Catalyst? Can you create a simple helloworld.f90 > example that works? > ? > Best, > Andy > ? > On Wed, Oct 26, 2016 at 3:39 AM, wrote: >> Hi Andy, >> >> I have changed both lines from coproc to main, but the error message >> remains the same. >> >> Best, >> Thomas >> ? >> Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer : >> ? >>> Hi Thomas, >>> ? >>> If you change from coproc to main in the "program" and "end >>> program" lines in FEDriver.f90 does that fix the problem? >>> ? >>> I'm working on a fix for this but don't have access to any MSVS >>> compilers. >>> ? >>> Thanks, >>> Andy >>> ? >>> On Sat, Oct 22, 2016 at 1:46 PM, wrote: >>>> Hello, >>>> >>>> I'm trying to compile the Fortran90FullExample using MSVS (Intel >>>> Fortran Compiler 2017 and Visual C++ 2015 compiler). >>>> Doing so I'm getting following linker error: >>>> >>>> Error?? ?LNK2019?? ?unresolved external symbol main referenced in >>>> function "int __cdecl __scrt_common_main_seh(void)" >>>> (?__scrt_common_main_seh@@YAHXZ)?? ?Fortran90FullExample. >>>> >>>> Obviously, the source code doesn't contain a main method at all, >>>> since the entry point is given by the fortran program in file >>>> 'FEDriver.f90'. >>>> Nevertheless, I guess the compiler internally creates a main >>>> method, and the linker cannot resolve the reference due to a name >>>> mangling problem, as there are different compilers involved. But >>>> I'm not quite sure about that, nor how to solve it, at that >>>> matter. >>>> >>>> Can you give me a hint how to solve that problem? >>>> >>>> Kind regards, >>>> Thomas >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Search the list archives at: >>>> http://markmail.org/search/?q=Paraview-developers >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>> ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From thomasblome at startmail.com Fri Nov 11 14:50:39 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Fri, 11 Nov 2016 20:50:39 +0100 Subject: [Paraview-developers] Linker error building Fortran90FullExample In-Reply-To: <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> References: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com> <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> Message-ID: To resolve the references inclusion of header files "CPythonAdaptorAPI.h" and "CAdaptorAPI.h" in FECxxAdaptor.cxx was required, as they declare the missing functions. Afterwards, I provided the corresponding procedure interfaces in the Fortran files and finally got through the static linking stage. Now, when I start the RUN_TESTS project, the Fortran90FullExampleTest fails due to a segmentation fault: 1/1 Test #1: Fortran90FullExampleTest .........***Exception: SegFault? 8.48 sec 1> 1>? 0% tests passed, 1 tests failed out of 1 1> 1>? Label Time Summary: 1>? CATALYST??? =?? 8.48 sec (1 test) 1>? PARAVIEW??? =?? 8.48 sec (1 test) 1> 1>? Total Test time (real) =?? 8.48 sec 1> 1>? The following tests FAILED: 1> ??? ?? 1 - Fortran90FullExampleTest (SEGFAULT) 1>? Errors while running CTest 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: The command "setlocal 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: C:\cmake\bin\ctest.exe --force-new-ctest-process -C Debug 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmErrorLevel 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" exited with code 8. Does anybody know how to solve this? Best, Thomas ? Am Donnerstag, 10. November 2016 19:10 schrieb thomasblome at startmail.com: ? > Hi Andy, > > The linker error concerning the missing main method was due to a > wrong solution setup of the Fortran90FullExample in VS. > The CMakeLists file provided generates only one single (C++) project > in VS, which means all .f90 files will be ignored by the compiler > (it's impossible to have a single Fortran/C++ mixed language project > in VS). > To solve this I had to configure the CMakeLists file to create a > library from FECxxAdaptor.cxx and link it with the > Fortran90FullExample. > > Other linker & compiler errors occurred with regards to mpi: > 1) the target_link_libraries command? in the CMakeLists file links > ${MPI_Fortran_LIBRARIES} to the fortran project, > but it forgets to link with msmpifec.lib (see also: > http://public.kitware.com/pipermail/cmake/2016-February/062861.html). > 2) The specification of an include directory (containing header > mpifptr.h) was missing. > > Another problem arose when it comes to the the by hand name mangling > for fortran in FECxxAdaptor.cxx. > To get rid of that I introduced function interfaces in the > FEFortranAdaptor.f90 file and now it works independently of the > Fortran compiler used. > > Now, there are only five remaining linker errors as shown below: > > LNK2019: unresolved external symbol COPROCESS referenced in function > TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? > LNK2019: unresolved external symbol COPROCESSORINITIALIZEWITHPYTHON > referenced in function MAIN__?? ??? ?FEDriver.obj?? ??? ? > LNK2019: unresolved external symbol COPROCESSORFINALIZE referenced in > function MAIN__?? ??? ?FEDriver.obj?? ??? ? > LNK2019: unresolved external symbol NEEDTOCREATEGRID referenced in > function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? > LNK2019: unresolved external symbol REQUESTDATADESCRIPTION referenced > in function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj??? > > In the ParaViewCatalystUsersGuide_v2 the missing symbols appear to be > declared in CAdaptorAPI.h and CPythonAdaptorAPI.h (but > NEEDTOCREATEGRID), > but I can't just include them in the Fortran code. > > Can you tell me how to resolve those missing references? > > Best, > Thomas > > ? > Am Mittwoch, 26. Oktober 2016 18:47 schrieb Andy Bauer > : > ? >> Hi Thomas, >> ? >> I really don't know about this. Do you get the same behavior if you >> don't link with Catalyst? Can you create a simple helloworld.f90 >> example that works? >> ? >> Best, >> Andy >> ? >> On Wed, Oct 26, 2016 at 3:39 AM, wrote: >>> Hi Andy, >>> >>> I have changed both lines from coproc to main, but the error >>> message remains the same. >>> >>> Best, >>> Thomas >>> ? >>> Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer : >>> ? >>>> Hi Thomas, >>>> ? >>>> If you change from coproc to main in the "program" and "end >>>> program" lines in FEDriver.f90 does that fix the problem? >>>> ? >>>> I'm working on a fix for this but don't have access to any MSVS >>>> compilers. >>>> ? >>>> Thanks, >>>> Andy >>>> ? >>>> On Sat, Oct 22, 2016 at 1:46 PM, >>>> wrote: >>>>> Hello, >>>>> >>>>> I'm trying to compile the Fortran90FullExample using MSVS (Intel >>>>> Fortran Compiler 2017 and Visual C++ 2015 compiler). >>>>> Doing so I'm getting following linker error: >>>>> >>>>> Error?? ?LNK2019?? ?unresolved external symbol main referenced in >>>>> function "int __cdecl __scrt_common_main_seh(void)" >>>>> (?__scrt_common_main_seh@@YAHXZ)?? ?Fortran90FullExample. >>>>> >>>>> Obviously, the source code doesn't contain a main method at all, >>>>> since the entry point is given by the fortran program in file >>>>> 'FEDriver.f90'. >>>>> Nevertheless, I guess the compiler internally creates a main >>>>> method, and the linker cannot resolve the reference due to a name >>>>> mangling problem, as there are different compilers involved. But >>>>> I'm not quite sure about that, nor how to solve it, at that >>>>> matter. >>>>> >>>>> Can you give me a hint how to solve that problem? >>>>> >>>>> Kind regards, >>>>> Thomas >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Search the list archives at: >>>>> http://markmail.org/search/?q=Paraview-developers >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>> ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From andy.bauer at kitware.com Sun Nov 13 08:40:10 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Sun, 13 Nov 2016 08:40:10 -0500 Subject: [Paraview-developers] Linker error building Fortran90FullExample In-Reply-To: References: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com> <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> Message-ID: Hi Thomas, Can you run ctest -V to get verbose output out of the run? That may shed some light on what the issue is. My guess is that it's not finding the coproc.py script. Also, the verbose output for ctest will show you how you can run the test manually which may be useful. Cheers, Andy On Fri, Nov 11, 2016 at 2:50 PM, wrote: > To resolve the references inclusion of header files "CPythonAdaptorAPI.h" > and "CAdaptorAPI.h" in FECxxAdaptor.cxx was required, as they declare the > missing functions. > Afterwards, I provided the corresponding procedure interfaces in the > Fortran files and finally got through the static linking stage. > > Now, when I start the RUN_TESTS project, the Fortran90FullExampleTest > fails due to a segmentation fault: > > 1/1 Test #1: Fortran90FullExampleTest .........***Exception: SegFault > 8.48 sec > 1> > 1> 0% tests passed, 1 tests failed out of 1 > 1> > 1> Label Time Summary: > 1> CATALYST = 8.48 sec (1 test) > 1> PARAVIEW = 8.48 sec (1 test) > 1> > 1> Total Test time (real) = 8.48 sec > 1> > 1> The following tests FAILED: > 1> 1 - Fortran90FullExampleTest (SEGFAULT) > 1> Errors while running CTest > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: The command > "setlocal > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: > C:\cmake\bin\ctest.exe --force-new-ctest-process -C Debug > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if > %errorlevel% neq 0 goto :cmEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & > call :cmErrorLevel %errorlevel% & goto :cmDone > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: > :cmErrorLevel > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1 > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if > %errorlevel% neq 0 goto :VCEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" > exited with code 8. > > Does anybody know how to solve this? > > Best, > Thomas > > > Am Donnerstag, 10. November 2016 19:10 schrieb thomasblome at startmail.com: > > > Hi Andy, > > The linker error concerning the missing main method was due to a wrong > solution setup of the Fortran90FullExample in VS. > The CMakeLists file provided generates only one single (C++) project in > VS, which means all .f90 files will be ignored by the compiler (it's > impossible to have a single Fortran/C++ mixed language project in VS). > To solve this I had to configure the CMakeLists file to create a library > from FECxxAdaptor.cxx and link it with the Fortran90FullExample. > > Other linker & compiler errors occurred with regards to mpi: > 1) the target_link_libraries command in the CMakeLists file links > ${MPI_Fortran_LIBRARIES} to the fortran project, > but it forgets to link with msmpifec.lib (see also: > http://public.kitware.com/pipermail/cmake/2016-February/062861.html). > 2) The specification of an include directory (containing header mpifptr.h) > was missing. > > Another problem arose when it comes to the the by hand name mangling for > fortran in FECxxAdaptor.cxx. > To get rid of that I introduced function interfaces in the > FEFortranAdaptor.f90 file and now it works independently of the Fortran > compiler used. > > Now, there are only five remaining linker errors as shown below: > > LNK2019: unresolved external symbol COPROCESS referenced in function > TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > LNK2019: unresolved external symbol COPROCESSORINITIALIZEWITHPYTHON > referenced in function MAIN__ FEDriver.obj > LNK2019: unresolved external symbol COPROCESSORFINALIZE referenced in > function MAIN__ FEDriver.obj > LNK2019: unresolved external symbol NEEDTOCREATEGRID referenced in > function TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > LNK2019: unresolved external symbol REQUESTDATADESCRIPTION referenced in > function TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > > In the ParaViewCatalystUsersGuide_v2 the missing symbols appear to be > declared in CAdaptorAPI.h and CPythonAdaptorAPI.h (but NEEDTOCREATEGRID), > but I can't just include them in the Fortran code. > > Can you tell me how to resolve those missing references? > > Best, > Thomas > > > Am Mittwoch, 26. Oktober 2016 18:47 schrieb Andy Bauer < > andy.bauer at kitware.com>: > > > Hi Thomas, > > I really don't know about this. Do you get the same behavior if you don't > link with Catalyst? Can you create a simple helloworld.f90 example that > works? > > Best, > Andy > > On Wed, Oct 26, 2016 at 3:39 AM, wrote: > > Hi Andy, > > I have changed both lines from coproc to main, but the error message > remains the same. > > Best, > Thomas > > Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer < > andy.bauer at kitware.com>: > > > Hi Thomas, > > If you change from coproc to main in the "program" and "end program" lines > in FEDriver.f90 does that fix the problem? > > I'm working on a fix for this but don't have access to any MSVS compilers. > > Thanks, > Andy > > On Sat, Oct 22, 2016 at 1:46 PM, wrote: > > Hello, > > I'm trying to compile the Fortran90FullExample using MSVS (Intel Fortran > Compiler 2017 and Visual C++ 2015 compiler). > Doing so I'm getting following linker error: > > Error LNK2019 unresolved external symbol main referenced in function > "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ) > Fortran90FullExample. > > Obviously, the source code doesn't contain a main method at all, since the > entry point is given by the fortran program in file 'FEDriver.f90'. > Nevertheless, I guess the compiler internally creates a main method, and > the linker cannot resolve the reference due to a name mangling problem, as > there are different compilers involved. But I'm not quite sure about that, > nor how to solve it, at that matter. > > Can you give me a hint how to solve that problem? > > Kind regards, > Thomas > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Sun Nov 13 10:15:58 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Sun, 13 Nov 2016 10:15:58 -0500 Subject: [Paraview-developers] Understanding Paview server client model Message-ID: Hi, while using paraview in server-client model we still need to have OpenGL on client side which means paraview still renders something on client side. Can someone guide me that which type of processing is done on client and which on server paraview-developers at paraview.org. I looked on internet but couldn't find anything related. -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Sun Nov 13 10:27:24 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Sun, 13 Nov 2016 10:27:24 -0500 Subject: [Paraview-developers] Data Processing in CPUs and GPUs Message-ID: Hi, To my knowledge even when using Paraview with GPUs it still uses CPUs to do some kind of processing. Can someone explain it to me that what part of processing is done on CPUs and how data is fed to GPUs. And moreover when we use MPI with Paraview, does it is used in CPUs context. I mean the processing which is being done on CPUs will now be done in parallel. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Mon Nov 14 10:02:00 2016 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 14 Nov 2016 10:02:00 -0500 Subject: [Paraview-developers] Data Processing in CPUs and GPUs In-Reply-To: References: Message-ID: On Sun, Nov 13, 2016 at 10:27 AM, Khayam Gondal wrote: > Hi, > To my knowledge even when using Paraview with GPUs it still uses CPUs to > do some kind of processing. Can someone explain it to me that what part of > processing is done on CPUs and how data is fed to GPUs. > Paraview does only rendering on the GPUs. There are filters that can do processing on the GPUs or on multiple cores: take a look at http://m.vtk.org/index.php/Main_Page > And moreover when we use MPI with Paraview, does it is used in CPUs > context. I mean the processing which is being done on CPUs will now be done > in parallel. > > Indeed. Data is partitioned for the MPI nodes, each node processes and renders its own data. The rendered image is composited and sent to the client. The ParaView Tutorial has a description of the ParaView architecture. http://www.paraview.org/Wiki/images/f/f7/ParaViewTutorial51.pdf Dan > > > Regards > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From will.schroeder at kitware.com Mon Nov 14 10:10:31 2016 From: will.schroeder at kitware.com (Will Schroeder) Date: Mon, 14 Nov 2016 10:10:31 -0500 Subject: [Paraview-developers] Data Processing in CPUs and GPUs In-Reply-To: References: Message-ID: A added note to Dan's response: this situation is changing rapidly in both VTK and ParaView. We'll be bringing VTK-m online soon. We expect that many key algorithms will be augmented, replaced, etc with VTK-m. Also there are several algorithms in VTK using the vtkSMPTools framework for threaded multiprocessing. E.g. vtkFlyingEdges2D/3D provides very fast and scalable isocontouring. Best, W On Mon, Nov 14, 2016 at 10:02 AM, Dan Lipsa wrote: > > > On Sun, Nov 13, 2016 at 10:27 AM, Khayam Gondal > wrote: > >> Hi, >> To my knowledge even when using Paraview with GPUs it still uses CPUs to >> do some kind of processing. Can someone explain it to me that what part of >> processing is done on CPUs and how data is fed to GPUs. >> > > > Paraview does only rendering on the GPUs. There are filters that can do > processing on the GPUs or on multiple cores: take a look at > http://m.vtk.org/index.php/Main_Page > > > >> And moreover when we use MPI with Paraview, does it is used in CPUs >> context. I mean the processing which is being done on CPUs will now be done >> in parallel. >> >> Indeed. Data is partitioned for the MPI nodes, each node processes and > renders its own data. The rendered image is composited and sent to the > client. > > The ParaView Tutorial has a description of the ParaView architecture. > http://www.paraview.org/Wiki/images/f/f7/ParaViewTutorial51.pdf > > Dan > > > >> >> >> Regards >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- William J. Schroeder, PhD Kitware, Inc. - Building the World's Technical Computing Software 28 Corporate Drive Clifton Park, NY 12065 will.schroeder at kitware.com http://www.kitware.com (518) 881-4902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Nov 14 16:01:48 2016 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 14 Nov 2016 17:01:48 -0400 Subject: [Paraview-developers] Understanding Paview server client model In-Reply-To: References: Message-ID: Hello, When you are using ParaView in client-server mode, OpenGL is needed on the client to perform either: - local rendering of the geometry processed on the server - this is the case if geometry to display is below the "remote rendering" threshold defined in *Edit/Settings/Render View/Remote Render Threshold*. In this case the geometry obtained at the end of the processing pipeline (ie in output of the ParaView sources/filters) is gathered (in case of a parallel server) and send back to the client for OpenGL rendering. This allows a more interactive visualization in case the data is small enough to be handled by the client. - display the picture of the remote rendered images - this happens when geometry size is bigger than the previously mentioned threshold. In this case, the interactions (camera position etc.) are transferred to the server node(s), then OpenGL rendering is performed on each node of the server and finally if server is parallel (more than 1 processor), the final image is obtain by compositing of depth and color images of all processors and finally gathered before being sent to the client for display. Hope it is clear. Best, *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-11-13 11:15 GMT-04:00 Khayam Gondal : > Hi, while using paraview in server-client model we still need to have > OpenGL on client side which means paraview still renders something on > client side. > > Can someone guide me that which type of processing is done on client and > which on server paraview-developers at paraview.org. I looked on internet > but couldn't find anything related. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Mon Nov 14 23:45:54 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Mon, 14 Nov 2016 23:45:54 -0500 Subject: [Paraview-developers] Paraview server in MultiGPU environment Message-ID: Hi. I have two NVIDIA K40m GPUs installed on server (48 CPU cores). I have compiled and installed Paraview server with MPI support and using NVIDIA Drivers. I use following command to start pvserver mpirun -bynode -np 24 bin/pvserver --disable-xdisplay-test --egl-device-index=1 : -np 24 bin/pvserver --disable-xdisplay-test --egl-device-index=0 But I don't now how to check that pvserver is actually using *both *of the GPUs not just one.. Actually If I change the --egl-device-index value to a random number like 8 or 9, server still starts up and client got connected to it. *Output of nvidia-smi* khayam at node-0:~$ nvidia-smi Mon Nov 14 23:41:08 2016 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 367.57 Driver Version: 367.57 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 Tesla K40m Off | 0000:02:00.0 Off | 0 | | N/A 19C P0 63W / 235W | 0MiB / 11439MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 1 Tesla K40m Off | 0000:82:00.0 Off | 0 | | N/A 20C P0 65W / 235W | 0MiB / 11439MiB | 100% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | No running processes found | *Snapshot of Paraview About (*It is showing K40m as remote renderer but is it using both GPUs or just one?) *[image: Inline image 1]* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 123.PNG Type: image/png Size: 212417 bytes Desc: not available URL: From dan.lipsa at kitware.com Tue Nov 15 10:22:50 2016 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Tue, 15 Nov 2016 10:22:50 -0500 Subject: [Paraview-developers] Paraview server in MultiGPU environment In-Reply-To: References: Message-ID: On Mon, Nov 14, 2016 at 11:45 PM, Khayam Gondal wrote: > Hi. > I have two NVIDIA K40m GPUs installed on server (48 CPU cores). I have > compiled and installed Paraview server with MPI support and using NVIDIA > Drivers. > > I use following command to start pvserver > > mpirun -bynode -np 24 bin/pvserver --disable-xdisplay-test > --egl-device-index=1 : -np 24 bin/pvserver --disable-xdisplay-test > --egl-device-index=0 > > I think the connection information reported is only for node 0. You can try changing the source code vtkEGLRenderWindow::SetDeviceAsDisplay and printing the device index from there. You should get a printout with the device index for every node. Maybe we should have a way to report the opengl info for evey node, including the device index. > But I don't now how to check that pvserver is actually using *both *of > the GPUs not just one.. Actually If I change the --egl-device-index value > to a random number like 8 or 9, server still starts up and client got > connected to it. > This is because if the device index is bigger than the number of devices it uses device 0. Dan > > *Output of nvidia-smi* > > khayam at node-0:~$ nvidia-smi > Mon Nov 14 23:41:08 2016 > +----------------------------------------------------------- > ------------------+ > | NVIDIA-SMI 367.57 Driver Version: 367.57 > | > |-------------------------------+----------------------+---- > ------------------+ > | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. > ECC | > | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute > M. | > |===============================+======================+==== > ==================| > | 0 Tesla K40m Off | 0000:02:00.0 Off | > 0 | > | N/A 19C P0 63W / 235W | 0MiB / 11439MiB | 0% > Default | > +-------------------------------+----------------------+---- > ------------------+ > | 1 Tesla K40m Off | 0000:82:00.0 Off | > 0 | > | N/A 20C P0 65W / 235W | 0MiB / 11439MiB | 100% > Default | > +-------------------------------+----------------------+---- > ------------------+ > > +----------------------------------------------------------- > ------------------+ > | Processes: GPU > Memory | > | GPU PID Type Process name Usage > | > |=========================================================== > ==================| > | No running processes found > | > > *Snapshot of Paraview About (*It is showing K40m as remote renderer but > is it using both GPUs or just one?) > > > *[image: Inline image 1]* > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 123.PNG Type: image/png Size: 212417 bytes Desc: not available URL: From cory.quammen at kitware.com Tue Nov 15 14:39:24 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 15 Nov 2016 14:39:24 -0500 Subject: [Paraview-developers] ANN: ParaView 5.2.0 now available for download Message-ID: We are pleased to announce that ParaView 5.2.0 is now available for download [1]. Release notes for ParaView 5.2.0 are on the Kitware blog [2]. For updates on features coming in future releases, please follow the Kitware Blog [3]. You can also let us know what you would like to see in ParaView [4]. - The ParaView Team [1] http://www.paraview.org/download [2] https://blog.kitware.com/paraview-5-2-0-release-notes/ [3] https://blog.kitware.com/tag/ParaView/ [4] http://paraview.uservoice.com From ben.boeckel at kitware.com Wed Nov 16 11:50:00 2016 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 16 Nov 2016 11:50:00 -0500 Subject: [Paraview-developers] New buildbot machines Message-ID: <20161116165000.GB17252@megas.kitware.com> Hi all, We have new ParaView dashboard machines and here's the breakdown: tylo: Windows 7 machine which has taken over nemesis' msvc2015 ParaView build vall: Linux machine which has taken over blights' non-osmesa builds Both have nVidia cards and are using their drivers. There may be tests which are failing and need excluded since the test exclusion lists have been cleared for both machines. They are also testing Python3 and Qt5 so that we can ship support in 5.3 for them. In addition, the 32bit builds from miranda have been retired per the previous announcement about 32bit support going away in 5.3 and above (and no one spoke up about it). Thanks, --Ben From mathieu.westphal at kitware.com Thu Nov 17 04:37:11 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Thu, 17 Nov 2016 10:37:11 +0100 Subject: [Paraview-developers] In Parallel, how to check if data is distributed across nodes. In-Reply-To: References: Message-ID: Hi All Trying again here with this question. How can a filter check if an input data is distributed accross nodes in Parallel ? I tried to check for CAN_HANDLE_PIECE_REQUEST in my filter RequestInformation, but without success (with ParaView). Regards, Mathieu Westphal On Thu, Sep 1, 2016 at 9:59 AM, Mathieu Westphal < mathieu.westphal at kitware.com> wrote: > Hello > > I would like to know if there is way to to check if the input of the > filter is distributed accross nodes > > In my case I have two filter, a typical pipeline looks like this > > - Input > |- Filter 1 > |- Filter2 > |- Filter 2 > > Input is not parallel aware, so its output will be replicated across > nodes, while filter 1 is, so Filter 1 output can be ditributed across nodes > in parallel. > > How could filter2 know if its input is distributed or not ? > I tried to check for CAN_HANDLE_PIECE_REQUEST but without success (with > ParaView). > > Thanks a lot > > Mathieu Westphal > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Nov 17 10:03:37 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 17 Nov 2016 10:03:37 -0500 Subject: [Paraview-developers] [vtk-developers] In Parallel, how to check if data is distributed across nodes. In-Reply-To: References: Message-ID: A filter can't, without explicitly communicating among ranks to know the number of cells/points on each rank. On Thu, Nov 17, 2016 at 4:37 AM, Mathieu Westphal wrote: > Hi All > > Trying again here with this question. > > How can a filter check if an input data is distributed accross nodes in > Parallel ? > I tried to check for CAN_HANDLE_PIECE_REQUEST in my filter > RequestInformation, but without success (with ParaView). > > Regards, > > Mathieu Westphal > > On Thu, Sep 1, 2016 at 9:59 AM, Mathieu Westphal > wrote: >> >> Hello >> >> I would like to know if there is way to to check if the input of the >> filter is distributed accross nodes >> >> In my case I have two filter, a typical pipeline looks like this >> >> - Input >> |- Filter 1 >> |- Filter2 >> |- Filter 2 >> >> Input is not parallel aware, so its output will be replicated across >> nodes, while filter 1 is, so Filter 1 output can be ditributed across nodes >> in parallel. >> >> How could filter2 know if its input is distributed or not ? >> I tried to check for CAN_HANDLE_PIECE_REQUEST but without success (with >> ParaView). >> >> Thanks a lot >> >> Mathieu Westphal > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q=vtk-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/vtk-developers > > From cornelis.bockemuehl at gmail.com Fri Nov 18 04:20:09 2016 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Fri, 18 Nov 2016 10:20:09 +0100 Subject: [Paraview-developers] Filtered choice of attributes Message-ID: With this in the server manager xml it is possible to have the user select one of the available attributes in the input data: Whatever... I have now a case where it would be desirable to constrain the selection to some of the attributes only, like with a filter function (best part of the C++ code of the plugin) that selects only some of the attributes based on their name. Is there any way how to achieve this? Thanks for any helpful hints! -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Fri Nov 18 10:07:47 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Fri, 18 Nov 2016 10:07:47 -0500 Subject: [Paraview-developers] EGL 1.4 error one 1 GPU Message-ID: I have Paraview server setup with two K40m GPUs. Output of nvidia-smi as following. [image: Inline image 1] I am using latest 1.5 EGL installed. Everything works fine with i start server on GPU 1 with this command. *bin/pvserver --disable-xdisplay-test --egl-device-index=1* But when I start server with *--egl-device-index=0*. It shows following error [image: Inline image 2] Can anyone guide me whats issue here ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 61417 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 23877 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Nov 18 10:23:17 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 18 Nov 2016 10:23:17 -0500 Subject: [Paraview-developers] Filtered choice of attributes In-Reply-To: References: Message-ID: There isn't a prebuilt way, but you can subclass vtkSMArrayListDomain and override vtkSMArrayListDomain::IsFilteredArray() to filter out arrays you don't want and use that domain for your property. On Fri, Nov 18, 2016 at 4:20 AM, Cornelis Bockem?hl < cornelis.bockemuehl at gmail.com> wrote: > With this in the server manager xml it is possible to have the user select > one of the available attributes in the input data: > > label="Select an attribute" > name="MyTonnage" > number_of_elements="1" > panel_visibility="default"> > > > name="Input" /> > > > > Whatever... > > > > I have now a case where it would be desirable to constrain the selection > to some of the attributes only, like with a filter function (best part of > the C++ code of the plugin) that selects only some of the attributes based > on their name. > > Is there any way how to achieve this? > > Thanks for any helpful hints! > > -- > Cornelis Bockem?hl > Basel, Schweiz > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cornelis.bockemuehl at gmail.com Fri Nov 18 10:26:26 2016 From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=) Date: Fri, 18 Nov 2016 16:26:26 +0100 Subject: [Paraview-developers] Filtered choice of attributes In-Reply-To: References: Message-ID: Thanks for this! And not the least also for the quick reaction you are showing to so many questions here!! But how do I integrate such a subclass into Paraview so that it replaces the original class: Do I have to recompile Paraview for this (ok, can be done - did it already...) or is there a way to "insert" this code like with the plugins? Kind regards, Cornelis 2016-11-18 16:23 GMT+01:00 Utkarsh Ayachit : > There isn't a prebuilt way, but you can subclass vtkSMArrayListDomain and > override vtkSMArrayListDomain::IsFilteredArray() to filter out arrays you > don't want and use that domain for your property. > > On Fri, Nov 18, 2016 at 4:20 AM, Cornelis Bockem?hl < > cornelis.bockemuehl at gmail.com> wrote: > >> With this in the server manager xml it is possible to have the user >> select one of the available attributes in the input data: >> >> > label="Select an attribute" >> name="MyTonnage" >> number_of_elements="1" >> panel_visibility="default"> >> >> >> > name="Input" /> >> >> >> >> Whatever... >> >> >> >> I have now a case where it would be desirable to constrain the selection >> to some of the attributes only, like with a filter function (best part of >> the C++ code of the plugin) that selects only some of the attributes based >> on their name. >> >> Is there any way how to achieve this? >> >> Thanks for any helpful hints! >> >> -- >> Cornelis Bockem?hl >> Basel, Schweiz >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -- Cornelis Bockem?hl Basel, Schweiz -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Fri Nov 18 10:29:25 2016 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Fri, 18 Nov 2016 10:29:25 -0500 Subject: [Paraview-developers] EGL 1.4 error one 1 GPU In-Reply-To: References: Message-ID: Khayam, Can you comment out lines 326, 327 and 329. The new lines will look like this: // if (this->DeviceIndex > 0) // { this->SetDeviceAsDisplay(this->DeviceIndex); // } Does this work for both devices? On Fri, Nov 18, 2016 at 10:07 AM, Khayam Gondal wrote: > I have Paraview server setup with two K40m GPUs. Output of nvidia-smi as > following. > [image: Inline image 1] > > I am using latest 1.5 EGL installed. > > Everything works fine with i start server on GPU 1 with this command. *bin/pvserver > --disable-xdisplay-test --egl-device-index=1* > But when I start server with *--egl-device-index=0*. It shows following > error > [image: Inline image 2] > > Can anyone guide me whats issue here ? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 23877 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 61417 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Nov 18 10:37:17 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 18 Nov 2016 10:37:17 -0500 Subject: [Paraview-developers] Filtered choice of attributes In-Reply-To: References: Message-ID: Cornelis, Glad to help :). To answer you latest question, you can add the new class in the "SERVER_MANAGER_SOURCES" in the add_paraview_plugin() call. e.g. ADD_PARAVIEW_PLUGIN( ... SERVER_MANAGER_XML foo.xml SERVER_MANAGER_SOURCES vtkSMMyNewDomain.cxx ) A few things to remember: 1. Ensure your domain class name begins with "vtkSM" 2. In XML, use the name of the domain without the "vtkSM" prefix e.g. "" Utkarsh On Fri, Nov 18, 2016 at 10:26 AM, Cornelis Bockem?hl wrote: > Thanks for this! And not the least also for the quick reaction you are > showing to so many questions here!! > > But how do I integrate such a subclass into Paraview so that it replaces the > original class: Do I have to recompile Paraview for this (ok, can be done - > did it already...) or is there a way to "insert" this code like with the > plugins? > > Kind regards, Cornelis > > > 2016-11-18 16:23 GMT+01:00 Utkarsh Ayachit : >> >> There isn't a prebuilt way, but you can subclass vtkSMArrayListDomain and >> override vtkSMArrayListDomain::IsFilteredArray() to filter out arrays you >> don't want and use that domain for your property. >> >> On Fri, Nov 18, 2016 at 4:20 AM, Cornelis Bockem?hl >> wrote: >>> >>> With this in the server manager xml it is possible to have the user >>> select one of the available attributes in the input data: >>> >>> >> label="Select an attribute" >>> name="MyTonnage" >>> number_of_elements="1" >>> panel_visibility="default"> >>> >>> >>> >> name="Input" /> >>> >>> >>> >>> Whatever... >>> >>> >>> >>> I have now a case where it would be desirable to constrain the selection >>> to some of the attributes only, like with a filter function (best part of >>> the C++ code of the plugin) that selects only some of the attributes based >>> on their name. >>> >>> Is there any way how to achieve this? >>> >>> Thanks for any helpful hints! >>> >>> -- >>> Cornelis Bockem?hl >>> Basel, Schweiz >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> > > > > -- > Cornelis Bockem?hl > Basel, Schweiz From khayam.gondal at gmail.com Fri Nov 18 22:30:23 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Fri, 18 Nov 2016 22:30:23 -0500 Subject: [Paraview-developers] EGL 1.4 error one 1 GPU In-Reply-To: References: Message-ID: Thanks Dan, It solved the problem. On Fri, Nov 18, 2016 at 10:29 AM, Dan Lipsa wrote: > Khayam, > Can you comment out lines 326, 327 and 329. The new lines will look like > this: > // if (this->DeviceIndex > 0) > // { > this->SetDeviceAsDisplay(this->DeviceIndex); > // } > > Does this work for both devices? > > On Fri, Nov 18, 2016 at 10:07 AM, Khayam Gondal > wrote: > >> I have Paraview server setup with two K40m GPUs. Output of nvidia-smi as >> following. >> [image: Inline image 1] >> >> I am using latest 1.5 EGL installed. >> >> Everything works fine with i start server on GPU 1 with this command. *bin/pvserver >> --disable-xdisplay-test --egl-device-index=1* >> But when I start server with *--egl-device-index=0*. It shows following >> error >> [image: Inline image 2] >> >> Can anyone guide me whats issue here ? >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 23877 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 61417 bytes Desc: not available URL: From thomasblome at startmail.com Sat Nov 19 10:09:29 2016 From: thomasblome at startmail.com (thomasblome at startmail.com) Date: Sat, 19 Nov 2016 16:09:29 +0100 Subject: [Paraview-developers] Linker error building Fortran90FullExample In-Reply-To: References: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com> <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> Message-ID: <0410d0f9fb3c652bb70a612fa5ce682e.startmail@www.startmail.com> Hi Andy, I ran ctest from the windows cmd, but couldn't make sense of the output. Anyhow, I guess the segmentation fault was due to a wrong declaration of the rank 3 Fortran array of type complex in the procedure interface I provided for the C++ function addfield(). I changed it to be type(c_ptr) as the function expects a double pointer. Afterwards the test ran successfully. Nevertheless, it remains a mystery to me how the reference to the rank 3 array is properly handled in addfield(), as Fortran and C++ use different memory layouts for multidimensional arrays; I guess it's still not correct, even though there is no segmentation fault shown. I set the input of EnableLiveVisualization() in coproc.py to True and tried to visualize the simulation, but its duration is too short - the test finishes already after a few seconds. Only once I could sneak a peak to the cube in Paraview, but I got following error message (in Paraview) right before the simulation stopped: ERROR: In C:\Kitware\ParaView-v5.1.2\VTK\Parallel\Core\vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (000001E68C21B360): Could not receive tag. 1 Best, Thomas ? Am Sonntag, 13. November 2016 14:40 schrieb Andy Bauer : ? > Hi Thomas, > ? > Can you run ctest -V to get verbose output out of the run? That may > shed some light on what the issue is. My guess is that it's not > finding the coproc.py script. Also, the verbose output for ctest will > show you how you can run the test manually which may be useful. > ? > Cheers, > Andy > ? > On Fri, Nov 11, 2016 at 2:50 PM, wrote: >> To resolve the references inclusion of header files >> "CPythonAdaptorAPI.h" and "CAdaptorAPI.h" in FECxxAdaptor.cxx was >> required, as they declare the missing functions. >> Afterwards, I provided the corresponding procedure interfaces in the >> Fortran files and finally got through the static linking stage. >> >> Now, when I start the RUN_TESTS project, the >> Fortran90FullExampleTest fails due to a segmentation fault: >> >> 1/1 Test #1: Fortran90FullExampleTest .........***Exception: >> SegFault? 8.48 sec >> 1> >> 1>? 0% tests passed, 1 tests failed out of 1 >> 1> >> 1>? Label Time Summary: >> 1>? CATALYST??? =?? 8.48 sec (1 test) >> 1>? PARAVIEW??? =?? 8.48 sec (1 test) >> 1> >> 1>? Total Test time (real) =?? 8.48 sec >> 1> >> 1>? The following tests FAILED: >> 1> ??? ?? 1 - Fortran90FullExampleTest (SEGFAULT) >> 1>? Errors while running CTest >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: The command "setlocal >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: C:\cmake\bin\ctest.exe --force-new-ctest-process -C >> Debug >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: if %errorlevel% neq 0 goto :cmEnd >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: :cmEnd >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto >> :cmDone >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: :cmErrorLevel >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: exit /b %1 >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: :cmDone >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: if %errorlevel% neq 0 goto :VCEnd >> 1>C:\Program Files >> (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(133,5): >> error MSB3073: :VCEnd" exited with code 8. >> >> Does anybody know how to solve this? >> >> Best, >> Thomas >> ? >> Am Donnerstag, 10. November 2016 19:10 schrieb >> thomasblome at startmail.com: >> ? >>> Hi Andy, >>> >>> The linker error concerning the missing main method was due to a >>> wrong solution setup of the Fortran90FullExample in VS. >>> The CMakeLists file provided generates only one single (C++) >>> project in VS, which means all .f90 files will be ignored by the >>> compiler (it's impossible to have a single Fortran/C++ mixed >>> language project in VS). >>> To solve this I had to configure the CMakeLists file to create a >>> library from FECxxAdaptor.cxx and link it with the >>> Fortran90FullExample. >>> >>> Other linker & compiler errors occurred with regards to mpi: >>> 1) the target_link_libraries command? in the CMakeLists file links >>> ${MPI_Fortran_LIBRARIES} to the fortran project, >>> but it forgets to link with msmpifec.lib (see also: >>> http://public.kitware.com/pipermail/cmake/2016-February/062861.html). >>> 2) The specification of an include directory (containing header >>> mpifptr.h) was missing. >>> >>> Another problem arose when it comes to the the by hand name >>> mangling for fortran in FECxxAdaptor.cxx. >>> To get rid of that I introduced function interfaces in the >>> FEFortranAdaptor.f90 file and now it works independently of the >>> Fortran compiler used. >>> >>> Now, there are only five remaining linker errors as shown below: >>> >>> LNK2019: unresolved external symbol COPROCESS referenced in >>> function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? >>> LNK2019: unresolved external symbol COPROCESSORINITIALIZEWITHPYTHON >>> referenced in function MAIN__?? ??? ?FEDriver.obj?? ??? ? >>> LNK2019: unresolved external symbol COPROCESSORFINALIZE referenced >>> in function MAIN__?? ??? ?FEDriver.obj?? ??? ? >>> LNK2019: unresolved external symbol NEEDTOCREATEGRID referenced in >>> function TCP_mp_TESTCOPROCESSOR?? ??? ?FEFortranAdaptor.obj?? ??? ? >>> LNK2019: unresolved external symbol REQUESTDATADESCRIPTION >>> referenced in function TCP_mp_TESTCOPROCESSOR?? ??? >>> ?FEFortranAdaptor.obj??? >>> >>> In the ParaViewCatalystUsersGuide_v2 the missing symbols appear to >>> be declared in CAdaptorAPI.h and CPythonAdaptorAPI.h (but >>> NEEDTOCREATEGRID), >>> but I can't just include them in the Fortran code. >>> >>> Can you tell me how to resolve those missing references? >>> >>> Best, >>> Thomas >>> >>> ? >>> Am Mittwoch, 26. Oktober 2016 18:47 schrieb Andy Bauer : >>> ? >>>> Hi Thomas, >>>> ? >>>> I really don't know about this. Do you get the same behavior if >>>> you don't link with Catalyst? Can you create a simple >>>> helloworld.f90 example that works? >>>> ? >>>> Best, >>>> Andy >>>> ? >>>> On Wed, Oct 26, 2016 at 3:39 AM, >>>> wrote: >>>>> Hi Andy, >>>>> >>>>> I have changed both lines from coproc to main, but the error >>>>> message remains the same. >>>>> >>>>> Best, >>>>> Thomas >>>>> ? >>>>> Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer : >>>>> ? >>>>>> Hi Thomas, >>>>>> ? >>>>>> If you change from coproc to main in the "program" and "end >>>>>> program" lines in FEDriver.f90 does that fix the problem? >>>>>> ? >>>>>> I'm working on a fix for this but don't have access to any MSVS >>>>>> compilers. >>>>>> ? >>>>>> Thanks, >>>>>> Andy >>>>>> ? >>>>>> On Sat, Oct 22, 2016 at 1:46 PM, >>>>>> wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I'm trying to compile the Fortran90FullExample using MSVS >>>>>>> (Intel Fortran Compiler 2017 and Visual C++ 2015 compiler). >>>>>>> Doing so I'm getting following linker error: >>>>>>> >>>>>>> Error?? ?LNK2019?? ?unresolved external symbol main referenced >>>>>>> in function "int __cdecl __scrt_common_main_seh(void)" >>>>>>> (?__scrt_common_main_seh@@YAHXZ)?? ?Fortran90FullExample. >>>>>>> >>>>>>> Obviously, the source code doesn't contain a main method at >>>>>>> all, since the entry point is given by the fortran program in >>>>>>> file 'FEDriver.f90'. >>>>>>> Nevertheless, I guess the compiler internally creates a main >>>>>>> method, and the linker cannot resolve the reference due to a >>>>>>> name mangling problem, as there are different compilers >>>>>>> involved. But I'm not quite sure about that, nor how to solve >>>>>>> it, at that matter. >>>>>>> >>>>>>> Can you give me a hint how to solve that problem? >>>>>>> >>>>>>> Kind regards, >>>>>>> Thomas >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Search the list archives at: >>>>>>> http://markmail.org/search/?q=Paraview-developers >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers >>>>>>> ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7F53DEC77F67D0E0.asc Type: application/pgp-keys Size: 3082 bytes Desc: OpenPGP public keys URL: From gregory.zaccaro at gmail.com Sat Nov 19 19:44:22 2016 From: gregory.zaccaro at gmail.com (=?UTF-8?Q?Gr=C3=A9gory_Zaccaro?=) Date: Sat, 19 Nov 2016 19:44:22 -0500 Subject: [Paraview-developers] Linker error with custom plugin Message-ID: Hello, I have troubles to compile a custom plugin which instantiate another custom plugin. Let's say I want to build a custom plugin A which uses another custom plugin B. Right now, I get linker errors when compiling plugin A. I built Paraview from sources with "BUILD_SHARED_LIBS = ON". The Cmake file of the plugin A looks like this : PROJECT(FilterA) INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) FIND_PACKAGE(ParaView REQUIRED) INCLUDE(${PARAVIEW_USE_FILE}) INCLUDE(ParaViewBranding) INCLUDE(ParaViewPlugins) ADD_PARAVIEW_PLUGIN(FilterA "1.0" SERVER_MANAGER_XML vtkFilterA.xml SERVER_MANAGER_SOURCES vtkFilterA.cxx) #FIND_LIBRARY(FilterB NAMES FilterB NO_MODULE) #TARGET_LINK_LIBRARIES(FilterA LINK_PRIVATE FilterB) The Cmake file of the plugin B looks like this : PROJECT(FilterB) INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) ADD_PARAVIEW_PLUGIN(FilterB "1.0" SERVER_MANAGER_XML vtkFilterB.xml SERVER_MANAGER_SOURCES vtkFilterB.cxx) In Visual Studio, I can see FilterB.lib in the list of the additionnal dependencies but I still get the linkage errors. I managed to solve the problem by manually add FilterB.obj to the additionnal dependencies of plugin A. But I didn't figured out how can I set Cmake to link the two plugins. Any help would be appreciated ! Kind regards, Gregory -------------- next part -------------- An HTML attachment was scrubbed... URL: From zig.shagit at ya.ru Mon Nov 21 04:12:46 2016 From: zig.shagit at ya.ru (=?utf-8?B?0KjQsNCz0LjRgiDQl9C40LPQsNC90YjQuNC9?=) Date: Mon, 21 Nov 2016 12:12:46 +0300 Subject: [Paraview-developers] Paraview translation Message-ID: <439401479719566@web17g.yandex.ru> Hello! I'm working on translation Paraview to Russian language and my current problem is to translate widgets and parameters that generated from XML which lays in ParaViewCore\ServerManager\SMApplication\Resources. Some parameters I can change through PyQt, but not all (for example, Paraview Settings Widget couldn't be change on boot up, 'cause is not initialized) and I know that some properties have "label" parameter, but not all. My question is "How I can labels and widgets from XML?" Shagit Ziganshin From M.Deij at marin.nl Mon Nov 21 09:40:10 2016 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Mon, 21 Nov 2016 14:40:10 +0000 Subject: [Paraview-developers] vtkReflectionFilter with multiple vector fields Message-ID: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> Hi, 8 months ago I pushed what I thought was a fix for a problem where data read from the CGNS reader was not properly mirrored by, e.g., the vtkReflectionFilter. The data from the CGNS files we use contains multiple vector fields (velocity, shear stress, you name it). What I did was to set the vtkDataSetAttributes::VECTORS attribute on all vector fields in the dataset (thinking that with that attribute set, the vtkReflectionFilter would work properly). Indeed, my (it turns out incomplete) tests showed that it did, I was happy, and my fix was merged. Unfortunately, the users find problems: http://public.kitware.com/pipermail/paraview/2016-October/038152.html Origin of the problem: my ?fix??. It turns out that if you call dsa->SetVectors(arr) on multiple arrays, only the last array on which it was called remains in the list of data arrays. The previous array for which this attribute was set is removed from the dataset attributes object. So, my question is: how to do this properly? Looking at the code of the vtkReflectionFilter I see that it gets ?the vectors? from the dataset. Unfortunately, in our case there is no concept of ?the vectors?. There are multiple vector fields that ALL NEED TO GET MIRRORED by the reflection filter. Any insight here is very welcome :-) Best wishes, Menno Deij ? van Rijswijk dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | Maritime Simulation & Software Group MARIN | T +31 317 49 35 06 | M.Deij at marin.nl | www.marin.nl [LinkedIn] [YouTube] [Twitter] [Facebook] MARIN news: 24th HISWA Symposium on Yacht design and Construction great success -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image878467.PNG Type: image/png Size: 293 bytes Desc: image878467.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagead8ca6.PNG Type: image/png Size: 331 bytes Desc: imagead8ca6.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagea1e578.PNG Type: image/png Size: 333 bytes Desc: imagea1e578.PNG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagee388fb.PNG Type: image/png Size: 253 bytes Desc: imagee388fb.PNG URL: From jfavre at cscs.ch Mon Nov 21 11:00:23 2016 From: jfavre at cscs.ch (Favre Jean) Date: Mon, 21 Nov 2016 16:00:23 +0000 Subject: [Paraview-developers] general error loading plugins on Cray Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> Cray developers out there? with the newer Cray environments, I cannot seem to load plugins anymore. My own plugins, or any other plugins automatically compiled by ParaView. I have tried 5.1, and 5.2, parallel, or serial versions, and all I ever get is the message: ERROR: In .../ParaView-v5.1.0/ParaViewCore/ClientServerCore/Core/vtkPVPluginLoader.cxx, line 404 vtkPVPluginLoader (0x1652de0): General error I have always had great success in the past with all versions of ParaView, and I can only think of some new Cray-environment related thing. By the way, I am using EGL now, but that really should be independent. Any ideas? ----------------- Jean -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Mon Nov 21 13:56:29 2016 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Mon, 21 Nov 2016 14:56:29 -0400 Subject: [Paraview-developers] vtkReflectionFilter with multiple vector fields In-Reply-To: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> References: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> Message-ID: Hi, Bad news is that you just can't. There is this concept of "Active Vectors", "Active Scalars" etc. on VTK datasetattributes and only one array can be marked with those tags. Then some filters only performs on those attributes, while some other allow at least the user to specify which array(s) to process - this is not the case here. If you want to perform reflection on all 3-components arrays, you will have to create a un filter (that will basically perform what the current one does plus perform the reflections on every arrays that have 3-components). Best, Joachim *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-11-21 10:40 GMT-04:00 Deij-van Rijswijk, Menno : > Hi, > > > > 8 months ago I pushed what I thought was a fix for a problem where data > read from the CGNS reader was not properly mirrored by, e.g., the > vtkReflectionFilter. The data from the CGNS files we use contains multiple > vector fields (velocity, shear stress, you name it). > > > > What I did was to set the vtkDataSetAttributes::VECTORS attribute on all > vector fields in the dataset (thinking that with that attribute set, the > vtkReflectionFilter would work properly). Indeed, my (it turns out > incomplete) tests showed that it did, I was happy, and my fix was merged. > > > > Unfortunately, the users find problems: http://public.kitware.com/ > pipermail/paraview/2016-October/038152.html > > Origin of the problem: my ?fix??. It turns out that if you call > dsa->SetVectors(arr) on multiple arrays, only the last array on which it > was called remains in the list of data arrays. The previous array for which > this attribute was set is removed from the dataset attributes object. > > > > So, my question is: how to do this properly? Looking at the code of the > vtkReflectionFilter I see that it gets ?the vectors? from the dataset. > Unfortunately, in our case there is no concept of ?the vectors?. There are > multiple vector fields that ALL NEED TO GET MIRRORED by the reflection > filter. > > > > Any insight here is very welcome :-) > > > > Best wishes, > > > > > > Menno Deij ? van Rijswijk > > > > dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | Maritime > Simulation & Software Group > MARIN | T +31 317 49 35 06 | M.Deij at marin.nl | www.marin.nl > > [image: LinkedIn] [image: > YouTube] [image: Twitter] > [image: Facebook] > > MARIN news: 24th HISWA Symposium on Yacht design and Construction great > success > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagea1e578.PNG Type: image/png Size: 333 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image878467.PNG Type: image/png Size: 293 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagee388fb.PNG Type: image/png Size: 253 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagead8ca6.PNG Type: image/png Size: 331 bytes Desc: not available URL: From dan.lipsa at kitware.com Mon Nov 21 16:54:02 2016 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Mon, 21 Nov 2016 16:54:02 -0500 Subject: [Paraview-developers] EGL 1.4 error one 1 GPU In-Reply-To: References: Message-ID: Great, Thanks for reporting and testing. This is the merge request: https://gitlab.kitware.com/vtk/vtk/merge_requests/2185 On Fri, Nov 18, 2016 at 10:30 PM, Khayam Gondal wrote: > Thanks Dan, It solved the problem. > > On Fri, Nov 18, 2016 at 10:29 AM, Dan Lipsa wrote: > >> Khayam, >> Can you comment out lines 326, 327 and 329. The new lines will look like >> this: >> // if (this->DeviceIndex > 0) >> // { >> this->SetDeviceAsDisplay(this->DeviceIndex); >> // } >> >> Does this work for both devices? >> >> On Fri, Nov 18, 2016 at 10:07 AM, Khayam Gondal >> wrote: >> >>> I have Paraview server setup with two K40m GPUs. Output of nvidia-smi as >>> following. >>> [image: Inline image 1] >>> >>> I am using latest 1.5 EGL installed. >>> >>> Everything works fine with i start server on GPU 1 with this command. *bin/pvserver >>> --disable-xdisplay-test --egl-device-index=1* >>> But when I start server with *--egl-device-index=0*. It shows following >>> error >>> [image: Inline image 2] >>> >>> Can anyone guide me whats issue here ? >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: http://markmail.org/search/?q= >>> Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 61417 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 23877 bytes Desc: not available URL: From Gerald.Lodron at joanneum.at Tue Nov 22 03:10:06 2016 From: Gerald.Lodron at joanneum.at (Lodron, Gerald) Date: Tue, 22 Nov 2016 08:10:06 +0000 Subject: [Paraview-developers] Migration from Paraview 4.4 to 5.2 Message-ID: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> Hi I currently updated my paraview and saw that my custom filter object panels which are inherited from pqObjectPanel and pqNamedObjectPanel seems to be deprecated.. I googled but could not find a migration guide. Can you give me a hint where to look? thanks ------------------------------------------------------------------------------------ Gerald Lodron ? Researcher of Machine Vision Applications Group DIGITAL - Institute for Information and Communication Technologies ? JOANNEUM RESEARCH Forschungsgesellschaft mbH Steyrergasse 17, 8010 Graz, AUSTRIA ? phone:?? +43-316-876-1751??? general fax: +43-316-876-1751 web: http://www.joanneum.at/digital e-mail: gerald.lodron at joanneum.at From sur.chiranjib at gmail.com Tue Nov 22 04:15:31 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Tue, 22 Nov 2016 14:45:31 +0530 Subject: [Paraview-developers] Migration from Paraview 4.4 to 5.2 In-Reply-To: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> References: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> Message-ID: HI Gerald, There have been major API changes in ParaView 5.2. May be the following wiki page will give you an idea about how to proceed. Like you, many of us are going through the changes in the code we have built over the years. I believe, with the changes, ParaView customised extensions will become feature rich and easy maintainable/extendable. http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/MajorAPIChanges.html Thanks, Chiranjib On Tue, Nov 22, 2016 at 1:40 PM, Lodron, Gerald wrote: > Hi > > I currently updated my paraview and saw that my custom filter object > panels which are inherited from pqObjectPanel and pqNamedObjectPanel seems > to be deprecated.. I googled but could not find a migration guide. Can you > give me a hint where to look? > > thanks > ------------------------------------------------------------ > ------------------------ > Gerald Lodron > > Researcher of Machine Vision Applications Group > DIGITAL - Institute for Information and Communication Technologies > > JOANNEUM RESEARCH Forschungsgesellschaft mbH > Steyrergasse 17, 8010 Graz, AUSTRIA > > phone: +43-316-876-1751 > general fax: +43-316-876-1751 > web: http://www.joanneum.at/digital > e-mail: gerald.lodron at joanneum.at > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfavre at cscs.ch Tue Nov 22 07:36:30 2016 From: jfavre at cscs.ch (Favre Jean) Date: Tue, 22 Nov 2016 12:36:30 +0000 Subject: [Paraview-developers] general error loading plugins on Cray In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> I'll respond to my own post. Thanks to a great tip from fellow John Biddiscombe, we figured out that the DynamicLoader::OpenLibrary() was wrongly compiled to be { return 0; } because of an #if defined() statement checking for CRAYXT_COMPUTE_LINUX_TARGET Depending on whether your compile with the Cray wrapper, or with g++, you'll get a different behavior; the Cray wrapper automatically sets a -DCRAYXT_COMPUTE_LINUX_TARGET Well, compiling with shared libs, I really should be able to open the shared libs objects. I have modified the source code of VTK/Utilities/KWSys/vtksys/DynamicLoader.cxx to default to the last case called " // 6. Implementation for default UNIX machines." I am now up and running with PV5.2 on the Cray XC, running EGL. ----------------- Jean/CSCS -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Nov 22 08:17:18 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 22 Nov 2016 08:17:18 -0500 Subject: [Paraview-developers] [Paraview] Migration from Paraview 4.4 to 5.2 In-Reply-To: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> References: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> Message-ID: Gerald, The pqObjectPanel/pqNamedObjectPanel have been long deprecated -- ~4.0. This page covers the new design: http://www.paraview.org/Wiki/ParaView/Properties_Panel This covers the changes to the plugins: http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel Utkarsh On Tue, Nov 22, 2016 at 3:10 AM, Lodron, Gerald wrote: > Hi > > I currently updated my paraview and saw that my custom filter object panels which are inherited from pqObjectPanel and pqNamedObjectPanel seems to be deprecated.. I googled but could not find a migration guide. Can you give me a hint where to look? > > thanks > ------------------------------------------------------------------------------------ > Gerald Lodron > > Researcher of Machine Vision Applications Group > DIGITAL - Institute for Information and Communication Technologies > > JOANNEUM RESEARCH Forschungsgesellschaft mbH > Steyrergasse 17, 8010 Graz, AUSTRIA > > phone: +43-316-876-1751 > general fax: +43-316-876-1751 > web: http://www.joanneum.at/digital > e-mail: gerald.lodron at joanneum.at > > _______________________________________________ > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Nov 22 08:20:41 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 22 Nov 2016 08:20:41 -0500 Subject: [Paraview-developers] vtkReflectionFilter with multiple vector fields In-Reply-To: References: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> Message-ID: > Then some filters only performs on those attributes, while some other allow at least the user to specify which array(s) to process - this is not the case here. > If you want to perform reflection on all 3-components arrays, you will have to create a un filter (that will basically perform what the current one does plus perform the reflections on every arrays that have 3-components). I wonder if this should indeed be added a new option to vtkReflectionFilter itself. It's not uncommon to have more than 1 vector fields in a dataset. Utkarsh From M.Deij at marin.nl Tue Nov 22 08:42:35 2016 From: M.Deij at marin.nl (Deij-van Rijswijk, Menno) Date: Tue, 22 Nov 2016 13:42:35 +0000 Subject: [Paraview-developers] vtkReflectionFilter with multiple vector fields In-Reply-To: References: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> Message-ID: > you will have to create a un filter What is an ?un filter? ? I have never heard of this term. Thanks and best wishes, Menno Deij ? van Rijswijk From: Joachim Pouderoux [mailto:joachim.pouderoux at kitware.com] Sent: Monday, November 21, 2016 7:56 PM To: Deij-van Rijswijk, Menno Cc: paraview-developers at paraview.org Subject: Re: [Paraview-developers] vtkReflectionFilter with multiple vector fields Hi, Bad news is that you just can't. There is this concept of "Active Vectors", "Active Scalars" etc. on VTK datasetattributes and only one array can be marked with those tags. Then some filters only performs on those attributes, while some other allow at least the user to specify which array(s) to process - this is not the case here. If you want to perform reflection on all 3-components arrays, you will have to create a un filter (that will basically perform what the current one does plus perform the reflections on every arrays that have 3-components). Best, Joachim Joachim Pouderoux, PhD Technical Expert - Scientific Computing Team Kitware SAS 2016-11-21 10:40 GMT-04:00 Deij-van Rijswijk, Menno >: Hi, 8 months ago I pushed what I thought was a fix for a problem where data read from the CGNS reader was not properly mirrored by, e.g., the vtkReflectionFilter. The data from the CGNS files we use contains multiple vector fields (velocity, shear stress, you name it). What I did was to set the vtkDataSetAttributes::VECTORS attribute on all vector fields in the dataset (thinking that with that attribute set, the vtkReflectionFilter would work properly). Indeed, my (it turns out incomplete) tests showed that it did, I was happy, and my fix was merged. Unfortunately, the users find problems: http://public.kitware.com/pipermail/paraview/2016-October/038152.html Origin of the problem: my ?fix??. It turns out that if you call dsa->SetVectors(arr) on multiple arrays, only the last array on which it was called remains in the list of data arrays. The previous array for which this attribute was set is removed from the dataset attributes object. So, my question is: how to do this properly? Looking at the code of the vtkReflectionFilter I see that it gets ?the vectors? from the dataset. Unfortunately, in our case there is no concept of ?the vectors?. There are multiple vector fields that ALL NEED TO GET MIRRORED by the reflection filter. Any insight here is very welcome :-) Best wishes, Menno Deij ? van Rijswijk dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | Maritime Simulation & Software Group MARIN | T +31 317 49 35 06 | M.Deij at marin.nl | www.marin.nl [LinkedIn] [YouTube] [Twitter] [Facebook] MARIN news: 24th HISWA Symposium on Yacht design and Construction great success _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 293 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 331 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 333 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 253 bytes Desc: image004.png URL: From Gerald.Lodron at joanneum.at Tue Nov 22 09:02:50 2016 From: Gerald.Lodron at joanneum.at (Lodron, Gerald) Date: Tue, 22 Nov 2016 14:02:50 +0000 Subject: [Paraview-developers] [Paraview] Migration from Paraview 4.4 to 5.2 In-Reply-To: References: <0da0698187434febb207fbc6a460d89b@RZJMBX2.jr1.local> Message-ID: thanks -----Urspr?ngliche Nachricht----- Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Gesendet: Dienstag, 22. November 2016 14:17 An: Lodron, Gerald Cc: Paraview Developer (Paraview-developers at paraview.org); Paraview User (paraview at paraview.org) Betreff: Re: [Paraview] Migration from Paraview 4.4 to 5.2 Gerald, The pqObjectPanel/pqNamedObjectPanel have been long deprecated -- ~4.0. This page covers the new design: http://www.paraview.org/Wiki/ParaView/Properties_Panel This covers the changes to the plugins: http://www.paraview.org/Wiki/Plugin_HowTo#Adding_Customizations_for_Properties_Panel Utkarsh On Tue, Nov 22, 2016 at 3:10 AM, Lodron, Gerald wrote: > Hi > > I currently updated my paraview and saw that my custom filter object panels which are inherited from pqObjectPanel and pqNamedObjectPanel seems to be deprecated.. I googled but could not find a migration guide. Can you give me a hint where to look? > > thanks > ---------------------------------------------------------------------- > -------------- > Gerald Lodron > > Researcher of Machine Vision Applications Group DIGITAL - Institute > for Information and Communication Technologies > > JOANNEUM RESEARCH Forschungsgesellschaft mbH Steyrergasse 17, 8010 > Graz, AUSTRIA > > phone: +43-316-876-1751 > general fax: +43-316-876-1751 > web: http://www.joanneum.at/digital > e-mail: gerald.lodron at joanneum.at > > _______________________________________________ > 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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From andy.bauer at kitware.com Tue Nov 22 09:22:57 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 22 Nov 2016 09:22:57 -0500 Subject: [Paraview-developers] general error loading plugins on Cray In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> Message-ID: Hi Jean, Thanks for the investigation and fix. Do you mind sharing your changes to DynamicLoader.cxx? A VTK gitlab merge request or even just the file itself would be great. I'd like to make sure that this fix gets into VTK and PV. Thanks, Andy On Tue, Nov 22, 2016 at 7:36 AM, Favre Jean wrote: > > I'll respond to my own post. Thanks to a great tip from fellow John > Biddiscombe, we figured out that the DynamicLoader::OpenLibrary() was > wrongly compiled to be > { > return 0; > } > > because of an #if defined() statement checking for > CRAYXT_COMPUTE_LINUX_TARGET > > Depending on whether your compile with the Cray wrapper, or with g++, > you'll get a different behavior; the Cray wrapper automatically sets a > -DCRAYXT_COMPUTE_LINUX_TARGET > > Well, compiling with shared libs, I really should be able to open the > shared libs objects. I have modified the source code of > VTK/Utilities/KWSys/vtksys/DynamicLoader.cxx to default to the last case > called " // 6. Implementation for default UNIX machines." > > I am now up and running with PV5.2 on the Cray XC, running EGL. > > ----------------- > Jean/CSCS > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Nov 22 10:30:02 2016 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 22 Nov 2016 10:30:02 -0500 Subject: [Paraview-developers] general error loading plugins on Cray In-Reply-To: References: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> Message-ID: I suspect those changes are lingering from the days of yore when Cray didn't support shared libraries. On Tue, Nov 22, 2016 at 9:22 AM, Andy Bauer wrote: > Hi Jean, > > Thanks for the investigation and fix. Do you mind sharing your changes to > DynamicLoader.cxx? A VTK gitlab merge request or even just the file itself > would be great. I'd like to make sure that this fix gets into VTK and PV. > > Thanks, > Andy > > On Tue, Nov 22, 2016 at 7:36 AM, Favre Jean wrote: > >> >> I'll respond to my own post. Thanks to a great tip from fellow John >> Biddiscombe, we figured out that the DynamicLoader::OpenLibrary() was >> wrongly compiled to be >> { >> return 0; >> } >> >> because of an #if defined() statement checking for >> CRAYXT_COMPUTE_LINUX_TARGET >> >> Depending on whether your compile with the Cray wrapper, or with g++, >> you'll get a different behavior; the Cray wrapper automatically sets a >> -DCRAYXT_COMPUTE_LINUX_TARGET >> >> Well, compiling with shared libs, I really should be able to open the >> shared libs objects. I have modified the source code of >> VTK/Utilities/KWSys/vtksys/DynamicLoader.cxx to default to the last case >> called " // 6. Implementation for default UNIX machines." >> >> I am now up and running with PV5.2 on the Cray XC, running EGL. >> >> ----------------- >> Jean/CSCS >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck.atkins at kitware.com Wed Nov 23 13:43:57 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Wed, 23 Nov 2016 13:43:57 -0500 Subject: [Paraview-developers] general error loading plugins on Cray In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> References: <0EB9B6375711A04B820E6B6F5CCA9F6843739950@MBX211.d.ethz.ch> <0EB9B6375711A04B820E6B6F5CCA9F6843739E50@MBX211.d.ethz.ch> Message-ID: > Depending on whether your compile with the Cray wrapper, or with g++, > you'll get a different behavior; the Cray wrapper automatically sets a > -DCRAYXT_COMPUTE_LINUX_TARGET > Ugh, this is leftover from an older time. Well, compiling with shared libs, I really should be able to open the > shared libs objects. I have modified the source code of > VTK/Utilities/KWSys/vtksys/DynamicLoader.cxx to default to the last case > called " // 6. Implementation for default UNIX machines." > I reworked a lot of the Cray toolchain support in newer CMake versions so CMake knows how to interpret and introspec the Cray wrappers (See Modules/Compiler/CrayPrgEnv*). Using a newer CMake (>= 3.6) then CMake should be correctly determining whether or not shared libraries are supported. Using that, we should be able to use the global property "TARGET_SUPPORTS_SHARED_LIBS" to set a #define in the kwsys configured header file. This, I believe, would be a better way to handle it rather than searching for various #ifdefs in the c++ code, since CMake already knows way more about differemt platforms and compilers that this dynamic loader source file does. I'll submit the patch to kwsys and give you a like to the review so you can test it if you'd like. > I am now up and running with PV5.2 on the Cray XC, running EGL. > Woo hoo! For what it's worth, we also run on a lot of CPU-only Crays using OSMesa and OpenSWR, both old and new Crays (i.e. CLE5 and CLE6). - Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 23 20:36:57 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 24 Nov 2016 01:36:57 +0000 Subject: [Paraview-developers] Superbuild failure Message-ID: Sorry for being dense, but I am failing trying to get superbuild to work. I am failing with ParaView trying to find python2.7 on the system. I am enabling Python as follows, but believe I am doing nothing else: ENABLE_python:BOOL=ON. Here is what I get: [100%] Built target paraview Install the project... -- Install configuration: "Release" -- Configuring done -- Generating done -- Build files have been written to: /projects/viz/paraview/ParaView/5.2.0-sb-mesa/Linux-chama-x86_64/Build/cpack/paraview/TGZ/install Install the project... -- Install configuration: "Release" CMake Error at cmake_install.cmake:45 (message): Failed to install pvdataserver: /usr/bin/env: python2.7: No such file or directory gmake[1]: *** [install] Error 1 CMake Error at superbuild/cmake_install.cmake:55 (message): Failed to install the paraview/TGZ package. Call Stack (most recent call first): cmake_install.cmake:37 (include) Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Thu Nov 24 02:32:30 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Wed, 23 Nov 2016 23:32:30 -0800 Subject: [Paraview-developers] ParaView 5.2 & GL_EXT_gpu_shader4 support - revisited Message-ID: Hi, I am trying to use ParaView5.2 in Ubuntu16.04 (VMWare guest). I have build it successfully from superbuild (CMakeCache attached), however, I get the runtime error vtkShaderProgram (0x2fc83b0): 0:39(12): error: extension `GL_EXT_gpu_shader4' unsupported in fragment shader I see that there is a thread in the same but could not find any solution : http://vtk.1045678.n5.nabble.com/GL-EXT-gpu-shader4-unsupported-help-td5736435.html Even the blog mentioned is leading to a dead page https://www.kitware.com/blog/home/post/999 Here are some of my system info csur at ubuntu:~/Work/paraview-build-system-qt4$ glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: VMware, Inc. (0x15ad) Device: SVGA3D; build: RELEASE; LLVM; (0x405) Version: 11.2.0 Accelerated: no Video memory: 1MB Unified memory: no Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 2.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; OpenGL version string: 2.1 Mesa 11.2.0 OpenGL shading language version string: 1.20 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.2.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 ---- csur at ubuntu:~/Work/paraview-build-system-qt4$ /usr/lib/nux/unity_support_test -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; OpenGL version string: 2.1 Mesa 11.2.0 Not software rendered: yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: yes Any help? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /home/csur/Work/paraview-build # It was generated by CMake: /home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Enable shared libraries BUILD_SHARED_LIBS:BOOL=ON //Build testing BUILD_TESTING:BOOL=OFF //Path to a program. BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //The build mode CMAKE_BUILD_TYPE:STRING=Release //The build type for the paraview project. CMAKE_BUILD_TYPE_paraview:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/home/csur/Work/paraview-build/install //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/make //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy //Path to a program. CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=paraview-superbuild //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Path to the coverage program that CTest uses for performing coverage // inspection COVERAGE_COMMAND:FILEPATH=/usr/bin/gcov //Extra command line flags to pass to the coverage tool COVERAGE_EXTRA_FLAGS:STRING=-l //How many times to retry timed-out CTest submissions. CTEST_SUBMIT_RETRY_COUNT:STRING=3 //How long to wait between timed-out CTest submissions. CTEST_SUBMIT_RETRY_DELAY:STRING=5 //Path to a program. CVSCOMMAND:FILEPATH=CVSCOMMAND-NOTFOUND //Options passed to the cvs update command. CVS_UPDATE_OPTIONS:STRING=-d -A -P //Maximum time allowed before CTest will kill the test. DART_TESTING_TIMEOUT:STRING=1500 //Request to build project adios ENABLE_adios:BOOL=OFF //Request to build project boost ENABLE_boost:BOOL=OFF //Request to build project catalyst ENABLE_catalyst:BOOL=OFF //Request to build project cgns ENABLE_cgns:BOOL=OFF //Request to build project cosmotools ENABLE_cosmotools:BOOL=OFF //Request to build project cxx11 ENABLE_cxx11:BOOL=OFF //Request to build project egl ENABLE_egl:BOOL=OFF //Request to build project ffmpeg ENABLE_ffmpeg:BOOL=OFF //Request to build project freetype ENABLE_freetype:BOOL=ON //Request to build project genericio ENABLE_genericio:BOOL=OFF //Request to build project glu ENABLE_glu:BOOL=OFF //Request to build project hdf5 ENABLE_hdf5:BOOL=OFF //Request to build project ispc ENABLE_ispc:BOOL=OFF //Request to build project llvm ENABLE_llvm:BOOL=OFF //Request to build project matplotlib ENABLE_matplotlib:BOOL=OFF //Request to build project mesa ENABLE_mesa:BOOL=OFF //Request to build project mpi ENABLE_mpi:BOOL=OFF //Request to build project mxml ENABLE_mxml:BOOL=OFF //Request to build project netcdf ENABLE_netcdf:BOOL=OFF //Request to build project numpy ENABLE_numpy:BOOL=OFF //Request to build project osmesa ENABLE_osmesa:BOOL=OFF //Request to build project ospray ENABLE_ospray:BOOL=OFF //Request to build project paraview ENABLE_paraview:BOOL=ON //Request to build project paraviewgettingstartedguide ENABLE_paraviewgettingstartedguide:BOOL=OFF //Request to build project paraviewsdk ENABLE_paraviewsdk:BOOL=ON //Request to build project paraviewtutorial ENABLE_paraviewtutorial:BOOL=OFF //Request to build project paraviewtutorialdata ENABLE_paraviewtutorialdata:BOOL=OFF //Request to build project paraviewusersguide ENABLE_paraviewusersguide:BOOL=OFF //Request to build project paraviewweb ENABLE_paraviewweb:BOOL=OFF //Request to build project paraviewweblightviz ENABLE_paraviewweblightviz:BOOL=OFF //Request to build project paraviewwebvisualizer ENABLE_paraviewwebvisualizer:BOOL=OFF //Request to build project portfwd ENABLE_portfwd:BOOL=OFF //Request to build project python ENABLE_python:BOOL=ON //Request to build project pythonsetuptools ENABLE_pythonsetuptools:BOOL=OFF //Request to build project qt4 ENABLE_qt4:BOOL=ON //Request to build project qt5 ENABLE_qt5:BOOL=OFF //Request to build project silo ENABLE_silo:BOOL=OFF //Request to build project szip ENABLE_szip:BOOL=OFF //Request to build project tbb ENABLE_tbb:BOOL=OFF //Request to build project visitbridge ENABLE_visitbridge:BOOL=OFF //Request to build project vortexfinder2 ENABLE_vortexfinder2:BOOL=OFF //Request to build project vrpn ENABLE_vrpn:BOOL=OFF //Request to build project xdmf3 ENABLE_xdmf3:BOOL=OFF //Request to build project zlib ENABLE_zlib:BOOL=ON //Path to a program. GITCOMMAND:FILEPATH=/usr/bin/git //Git command line client GIT_EXECUTABLE:FILEPATH=/usr/bin/git //Path to a program. HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND //Command to build the project MAKECOMMAND:STRING=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" //Path to the memory checking command, used for memory error detection. MEMORYCHECK_COMMAND:FILEPATH=MEMORYCHECK_COMMAND-NOTFOUND //File that contains suppressions for the memory checker MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH= //Path to a program. P4COMMAND:FILEPATH=P4COMMAND-NOTFOUND //If set, overrides the generated filename for the package PARAVIEWSDK_PACKAGE_FILE_NAME:STRING= //ParaView's build mode PARAVIEW_BUILD_TYPE:STRING= //Build documentation for the web PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF //The catalyst edition to build PARAVIEW_CATALYST_EDITION:STRING=Essentials //Enable Python support in catalyst PARAVIEW_CATALYST_PYTHON:BOOL=ON //Default to using the system OpenGL PARAVIEW_DEFAULT_SYSTEM_GL:BOOL=OFF //A list of projects for ParaView to depend on PARAVIEW_EXTERNAL_PROJECTS:STRING= //Extra arguments to be passed to ParaView when configuring. PARAVIEW_EXTRA_CMAKE_ARGUMENTS:STRING= //Freeze Python packages and modules into the application PARAVIEW_FREEZE_PYTHON:BOOL=OFF //If set, overrides the generated filename for the package PARAVIEW_PACKAGE_FILE_NAME:STRING= //String to use as a suffix for generated packages PARAVIEW_PACKAGE_SUFFIX:STRING= //Rendering backend to use for ParaView PARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 //The default version of ParaView to use if it can't be auto-determined PARAVIEW_VERSION_DEFAULT:STRING=5.2.0-RC3 PARAVIEW_WEB_TEST_REMOTE:BOOL=OFF //Pass LD_LIBRARY_PATH to build scripts PASS_LD_LIBRARY_PATH_FOR_BUILDS:BOOL=ON //Path to a program. ProcessorCount_cmd_getconf:FILEPATH=/usr/bin/getconf //Path to a program. ProcessorCount_cmd_sysctl:FILEPATH=/sbin/sysctl //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qdbuscpp2xml //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qdbusxml2cpp //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/designer //The location of the Qt docs QT_DOC_DIR:PATH=/usr/share/qt4/doc //The location of the Qt imports QT_IMPORTS_DIR:PATH=QT_IMPORTS_DIR-NOTFOUND //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/linguist //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/lrelease //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/lupdate //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/usr/share/qt4/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/moc //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libphononwidgets.so //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=/usr/include/qt4/phonon //The Qt PHONON library QT_PHONON_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libphonon.so //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libphonon.so //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/usr/lib/x86_64-linux-gnu/qt4/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/qcollectiongenerator //Path to a library. QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libqdeclarativeview.so //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/bearer/libqgenericbearer.so //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqgif.so //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/graphicssystems/libqglgraphicssystem.so //Path to a library. QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QICO_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqico.so //Path to a library. QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqjpcodecs.so //Path to a library. QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqjpeg.so //Path to a library. QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqkrcodecs.so //The qmake executable for the Qt installation to use QT_QMAKE_EXECUTABLE:FILEPATH=/usr/bin/qmake //Path to a library. QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QMNG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/sqldrivers/libqsqlite.so //Path to a library. QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLPSQL_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/iconengines/libqsvgicon.so //Path to a library. QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqsvg.so //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/usr/include/qt4/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQt3Support.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=QT_QT3SUPPORT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQt3Support.so //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/accessible/libqtaccessiblecompatwidgets.so //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtCLucene.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=QT_QTCLUCENE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/usr/include/qt4/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtCore.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=QT_QTCORE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=/usr/include/qt4/QtDBus //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDBus.so //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDBus.so //Path to a file. QT_QTDECLARATIVE_INCLUDE_DIR:PATH=/usr/include/qt4/QtDeclarative //The Qt QTDECLARATIVE library QT_QTDECLARATIVE_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDeclarative.so //Path to a library. QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDeclarative.so //Path to a file. QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/usr/include/qt4/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDesignerComponents.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/usr/include/qt4/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtDesigner.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNER_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtDesigner.so //Path to a library. QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTGA_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtga.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/usr/include/qt4/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtGui.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=QT_QTGUI_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/usr/include/qt4/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtHelp.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=QT_QTHELP_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtHelp.so //Path to a library. QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqtiff.so //Path to a file. QT_QTMOTIF_INCLUDE_DIR:PATH=QT_QTMOTIF_INCLUDE_DIR-NOTFOUND //The Qt QTMOTIF library QT_QTMOTIF_LIBRARY:STRING= //Path to a library. QT_QTMOTIF_LIBRARY_DEBUG:FILEPATH=QT_QTMOTIF_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMOTIF_LIBRARY_RELEASE:FILEPATH=QT_QTMOTIF_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=QT_QTMULTIMEDIA_INCLUDE_DIR-NOTFOUND //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING= //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/usr/include/qt4/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtNetwork.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=QT_QTNETWORK_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtNetwork.so //Path to a file. QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND //The Qt QTNSPLUGIN library QT_QTNSPLUGIN_LIBRARY:STRING= //Path to a library. QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTOPENGL_INCLUDE_DIR:PATH=/usr/include/qt4/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtOpenGL.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=QT_QTOPENGL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtOpenGL.so //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/graphicssystems/libqtracegraphicssystem.so //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/script/libqtscriptdbus.so //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/usr/include/qt4/QtScriptTools //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtScriptTools.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtScriptTools.so //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=/usr/include/qt4/QtScript //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtScript.so //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtScript.so //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/usr/include/qt4/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtSql.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=QT_QTSQL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=/usr/include/qt4/QtSvg //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtSvg.so //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=QT_QTSVG_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtSvg.so //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/usr/include/qt4/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtTest.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=QT_QTTEST_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/usr/include/qt4/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtUiTools.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTUITOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtUiTools.a //Path to a library. QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/plugins/codecs/libqtwcodecs.so //Path to a file. QT_QTWEBKIT_INCLUDE_DIR:PATH=/usr/include/qt4/QtWebKit //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtWebKit.so //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtWebKit.so //Path to a file. QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=/usr/include/qt4/QtXmlPatterns //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtXmlPatterns.so //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/usr/include/qt4/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=/usr/lib/x86_64-linux-gnu/libQtXml.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=QT_QTXML_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libQtXml.so //Path to a library. QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=QT_QWEBVIEW_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_RCC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/rcc //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_RELEASE-NOTFOUND //The location of the Qt translations QT_TRANSLATIONS_DIR:PATH=/usr/share/qt4/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/usr/lib/x86_64-linux-gnu/qt4/bin/uic //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-NOTFOUND //Path to scp command, used by CTest for submitting results to // a Dart server SCPCOMMAND:FILEPATH=/usr/bin/scp //Path to a program. SED_EXECUTABLE:FILEPATH=/bin/sed //Name of the computer/site where compile is being run SITE:STRING=ubuntu //Path to the SLURM sbatch executable SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND //Path to the SLURM srun executable SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND //The package to install by default SUPERBUILD_DEFAULT_INSTALL:STRING=paraview/TGZ //Do not update git repositories during the build SUPERBUILD_OFFLINE_BUILD:BOOL=OFF //Number of jobs to use when compiling subprojects SUPERBUILD_PROJECT_PARALLELISM:STRING=1 //Suppress output for bzip2 SUPPRESS_bzip2_OUTPUT:BOOL=OFF //Suppress output for fontconfig SUPPRESS_fontconfig_OUTPUT:BOOL=OFF //Suppress output for freetype SUPPRESS_freetype_OUTPUT:BOOL=OFF //Suppress output for libxml2 SUPPRESS_libxml2_OUTPUT:BOOL=OFF //Suppress output for paraview SUPPRESS_paraview_OUTPUT:BOOL=OFF //Suppress output for png SUPPRESS_png_OUTPUT:BOOL=OFF //Suppress output for python SUPPRESS_python_OUTPUT:BOOL=OFF //Suppress output for qt4 SUPPRESS_qt4_OUTPUT:BOOL=OFF //Suppress output for zlib SUPPRESS_zlib_OUTPUT:BOOL=OFF //Path to a program. SVNCOMMAND:FILEPATH=SVNCOMMAND-NOTFOUND //Enable the non-free parts of the superbuild USE_NONFREE_COMPONENTS:BOOL=OFF USE_SYSTEM_bzip2:BOOL=OFF USE_SYSTEM_freetype:BOOL=OFF USE_SYSTEM_libxml2:BOOL=OFF USE_SYSTEM_png:BOOL=OFF USE_SYSTEM_python:BOOL=OFF USE_SYSTEM_qt4:BOOL=OFF USE_SYSTEM_zlib:BOOL=OFF //The source selection for mesa mesa_SOURCE_SELECTION:STRING=v13.0.0 //Enable the OpenSWR driver mesa_USE_SWR:BOOL=ON //Target ISA for OSPRay (SSE, AVX, AVX2, AVX512, or ALL). ospray_BUILD_ISA:STRING=ALL //Value Computed by CMake paraview-superbuild_BINARY_DIR:STATIC=/home/csur/Work/paraview-build //Value Computed by CMake paraview-superbuild_SOURCE_DIR:STATIC=/home/csur/Software/ParaView-superbuild //If enabled, fetch sources from GIT paraview_FROM_GIT:BOOL=ON //GIT_REPOSITORY for project 'paraview' paraview_GIT_REPOSITORY:STRING=https://gitlab.kitware.com/paraview/paraview.git //GIT_TAG for project 'paraview' paraview_GIT_TAG:STRING=origin/master //Build Qt with OpenSSL support qt4_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt4 when configuring. qt4_EXTRA_CONFIGURATION_OPTIONS:STRING= //Work around a build issue in Qt. Use this if you see linker errors // with QtHelp and QCLucene. qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD:BOOL=OFF //Build with OpenSSL support. Requires system-installed OpenSSL // at runtime. qt5_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt when configuring. qt5_EXTRA_CONFIGURATION_OPTIONS:STRING= //Location for downloaded source tarballs superbuild_download_location:PATH=/home/csur/Work/paraview-build/downloads //Arguments to pass to git clone superbuild_git_clone_arguments:STRING=--progress ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: BUILD_TESTING BUILD_TESTING-MODIFIED:INTERNAL=ON //ADVANCED property for variable: BZRCOMMAND BZRCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-ADVANCED:INTERNAL=1 //STRINGS property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Release;RelWithDebInfo;Debug //STRINGS property for variable: CMAKE_BUILD_TYPE_paraview CMAKE_BUILD_TYPE_paraview-STRINGS:INTERNAL=;Release;RelWithDebInfo;Debug //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/home/csur/Work/paraview-build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=7 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/home/csur/Software/ParaView-superbuild //MODIFIED property for variable: CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX-MODIFIED:INTERNAL=ON //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=1 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/home/csur/lib/cmake/cmake-3.7.0-rc2-Linux-x86_64/share/cmake-3.7 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_COMMAND COVERAGE_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_EXTRA_FLAGS COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVSCOMMAND CVSCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVS_UPDATE_OPTIONS CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: DART_TESTING_TIMEOUT DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1 //Request to build project bzip2 ENABLE_bzip2:INTERNAL=OFF //Request to build project fontconfig ENABLE_fontconfig:INTERNAL=OFF //Request to build project libxml2 ENABLE_libxml2:INTERNAL=OFF //MODIFIED property for variable: ENABLE_paraviewsdk ENABLE_paraviewsdk-MODIFIED:INTERNAL=ON //Request to build project png ENABLE_png:INTERNAL=OFF //MODIFIED property for variable: ENABLE_python ENABLE_python-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_qt4 ENABLE_qt4-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_zlib ENABLE_zlib-MODIFIED:INTERNAL=ON //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/bin/git][v2.7.4()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/usr/bin/qmake][/usr/lib/x86_64-linux-gnu/qt4/bin/moc][/usr/lib/x86_64-linux-gnu/qt4/bin/rcc][/usr/lib/x86_64-linux-gnu/qt4/bin/uic][/usr/include/qt4][/usr/lib/x86_64-linux-gnu][/usr/lib/x86_64-linux-gnu/libQtCore.so][v4.8.7()] //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HAVE_void_ptr_size:INTERNAL=TRUE //ADVANCED property for variable: HGCOMMAND HGCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MAKECOMMAND MAKECOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_COMMAND MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: P4COMMAND P4COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_TYPE PARAVIEW_BUILD_TYPE-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_CATALYST_EDITION PARAVIEW_CATALYST_EDITION-STRINGS:INTERNAL=Essentials;Extras;Rendering-Base //ADVANCED property for variable: PARAVIEW_EXTERNAL_PROJECTS PARAVIEW_EXTERNAL_PROJECTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTRA_CMAKE_ARGUMENTS PARAVIEW_EXTRA_CMAKE_ARGUMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_PACKAGE_SUFFIX PARAVIEW_PACKAGE_SUFFIX-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_RENDERING_BACKEND PARAVIEW_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2 //ADVANCED property for variable: PARAVIEW_VERSION_DEFAULT PARAVIEW_VERSION_DEFAULT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PASS_LD_LIBRARY_PATH_FOR_BUILDS PASS_LD_LIBRARY_PATH_FOR_BUILDS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_getconf ProcessorCount_cmd_getconf-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_sysctl ProcessorCount_cmd_sysctl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_BINARY_DIR:INTERNAL=/usr/lib/x86_64-linux-gnu/qt4/bin //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DESIGNER_EXECUTABLE QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DOC_DIR QT_DOC_DIR-ADVANCED:INTERNAL=1 QT_HEADERS_DIR:INTERNAL=/usr/include/qt4 //ADVANCED property for variable: QT_IMPORTS_DIR QT_IMPORTS_DIR-ADVANCED:INTERNAL=1 //Qt library dir QT_LIBRARY_DIR:INTERNAL=/usr/lib/x86_64-linux-gnu //ADVANCED property for variable: QT_LINGUIST_EXECUTABLE QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LRELEASE_EXECUTABLE QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LUPDATE_EXECUTABLE QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MKSPECS_DIR QT_MKSPECS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MOC_EXECUTABLE QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_INCLUDE_DIR QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PLUGINS_DIR QT_PLUGINS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/usr/bin/qmake //ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_INCLUDE_DIR QT_QTMOTIF_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY QT_QTMOTIF_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_DEBUG QT_QTMOTIF_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMOTIF_LIBRARY_RELEASE QT_QTMOTIF_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_INCLUDE_DIR QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_RCC_EXECUTABLE QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TRANSLATIONS_DIR QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC3_EXECUTABLE QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC_EXECUTABLE QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //Have symbol Q_WS_MAC Q_WS_MAC:INTERNAL= //Have symbol Q_WS_QWS Q_WS_QWS:INTERNAL= //Have symbol Q_WS_WIN Q_WS_WIN:INTERNAL= //Have symbol Q_WS_X11 Q_WS_X11:INTERNAL=1 //ADVANCED property for variable: SCPCOMMAND SCPCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SED_EXECUTABLE SED_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SITE SITE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SBATCH_COMMAND SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SRUN_COMMAND SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1 //STRINGS property for variable: SUPERBUILD_DEFAULT_INSTALL SUPERBUILD_DEFAULT_INSTALL-STRINGS:INTERNAL=paraview/TGZ;catalyst/TGZ //ADVANCED property for variable: SUPERBUILD_PROJECT_PARALLELISM SUPERBUILD_PROJECT_PARALLELISM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_bzip2_OUTPUT SUPPRESS_bzip2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_fontconfig_OUTPUT SUPPRESS_fontconfig_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_freetype_OUTPUT SUPPRESS_freetype_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_libxml2_OUTPUT SUPPRESS_libxml2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_paraview_OUTPUT SUPPRESS_paraview_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_png_OUTPUT SUPPRESS_png_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_python_OUTPUT SUPPRESS_python_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_qt4_OUTPUT SUPPRESS_qt4_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_zlib_OUTPUT SUPPRESS_zlib_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SVNCOMMAND SVNCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: USE_NONFREE_COMPONENTS USE_NONFREE_COMPONENTS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: USE_SYSTEM_qt4 USE_SYSTEM_qt4-MODIFIED:INTERNAL=ON //STRINGS property for variable: mesa_SOURCE_SELECTION mesa_SOURCE_SELECTION-STRINGS:INTERNAL=v12.0.3;v13.0.0 //ADVANCED property for variable: mesa_USE_SWR mesa_USE_SWR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-ADVANCED:INTERNAL=1 //STRINGS property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-STRINGS:INTERNAL=SSE;AVX;AVX2;AVX512;ALL //ADVANCED property for variable: paraview_GIT_REPOSITORY paraview_GIT_REPOSITORY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: paraview_GIT_TAG paraview_GIT_TAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_ENABLE_OPENSSL qt4_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_EXTRA_CONFIGURATION_OPTIONS qt4_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_ENABLE_OPENSSL qt5_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_EXTRA_CONFIGURATION_OPTIONS qt5_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: superbuild_download_location superbuild_download_location-ADVANCED:INTERNAL=1 //ADVANCED property for variable: superbuild_git_clone_arguments superbuild_git_clone_arguments-ADVANCED:INTERNAL=1 superbuild_python_executable:INTERNAL=/home/csur/Work/paraview-build/install/bin/python //CHECK_TYPE_SIZE: sizeof(void*) void_ptr_size:INTERNAL=8 From ken.martin at kitware.com Thu Nov 24 07:52:58 2016 From: ken.martin at kitware.com (Ken Martin) Date: Thu, 24 Nov 2016 07:52:58 -0500 Subject: [Paraview-developers] ParaView 5.2 & GL_EXT_gpu_shader4 support - revisited In-Reply-To: References: Message-ID: Mesa 11.2 with llvmpipe or openswr as the driver should work fine (along with nvidia drivers etc). It looks like your mesa build (or environment) is picking another driver and is using OpenGL ES as opposed to regular OpenGL. The OpenGL version string should report 3.2 or later. On Thu, Nov 24, 2016 at 2:32 AM, Chiranjib Sur wrote: > Hi, > I am trying to use ParaView5.2 in Ubuntu16.04 (VMWare guest). I have build > it successfully from superbuild (CMakeCache attached), however, I get the > runtime error > > vtkShaderProgram (0x2fc83b0): 0:39(12): error: extension > `GL_EXT_gpu_shader4' unsupported in fragment shader > > I see that there is a thread in the same but could not find any solution : > > http://vtk.1045678.n5.nabble.com/GL-EXT-gpu-shader4- > unsupported-help-td5736435.html > > Even the blog mentioned is leading to a dead page > https://www.kitware.com/blog/home/post/999 > > Here are some of my system info > > csur at ubuntu:~/Work/paraview-build-system-qt4$ glxinfo -B > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > Extended renderer info (GLX_MESA_query_renderer): > Vendor: VMware, Inc. (0x15ad) > Device: SVGA3D; build: RELEASE; LLVM; (0x405) > Version: 11.2.0 > Accelerated: no > Video memory: 1MB > Unified memory: no > Preferred profile: compat (0x2) > Max core profile version: 0.0 > Max compat profile version: 2.1 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 2.0 > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; > OpenGL version string: 2.1 Mesa 11.2.0 > OpenGL shading language version string: 1.20 > > OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.2.0 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 > > > ---- > > csur at ubuntu:~/Work/paraview-build-system-qt4$ /usr/lib/nux/unity_support_test > -p > OpenGL vendor string: VMware, Inc. > OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; > OpenGL version string: 2.1 Mesa 11.2.0 > > Not software rendered: yes > Not blacklisted: yes > GLX fbconfig: yes > GLX texture from pixmap: yes > GL npot or rect textures: yes > GL vertex program: yes > GL fragment program: yes > GL vertex buffer object: yes > GL framebuffer object: yes > GL version is 1.4+: yes > > Unity 3D supported: yes > > Any help? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dlawrie at ara.co.uk Thu Nov 24 09:12:38 2016 From: dlawrie at ara.co.uk (David Lawrie) Date: Thu, 24 Nov 2016 14:12:38 +0000 Subject: [Paraview-developers] Panel widget combo box not reading enumerationdomain xml Message-ID: Hi, I am trying to work out how to create custom panels using the panel_widget entry in PropertyGroups. I have created a simple panel using QT designer and an associated class (subclassing pqPropertyGroupWidget). I use addPropertyLink to link the ui to the paraview filter and then set up the servermanager xml. This mostly seems to work, the initial values in the ui and the filter are as set in the xml and correctly update when I change them in the ui. However, one of the widget in the panel is a combo-box which I specify the entries of in the xml, this remains blank. Below is a shortened example of the servermanager xml I am using and the addPropertyLink code I have used. Any hints as to where I am going wrong, or what I might have missed out would be gratefully received. ... ... smproperty = smgroup->GetProperty("LinkSetMode"); if (smproperty != nullptr){ this->addPropertyLink(this->Internals->ComboMode, "currentIndex", SIGNAL(activated(int)), smproperty); } ********************************************************************** Please consider the environment. Only print this email if absolutely necessary. This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ********************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From joachim.pouderoux at kitware.com Thu Nov 24 10:51:08 2016 From: joachim.pouderoux at kitware.com (Joachim Pouderoux) Date: Thu, 24 Nov 2016 11:51:08 -0400 Subject: [Paraview-developers] vtkReflectionFilter with multiple vector fields In-Reply-To: References: <39a771cd64b3448587c15564c0ed5a47@MAR190n2.marin.local> Message-ID: Sorry, it was a typo I mean a *new* filter. But as proposed by Utkarsh, you could modify the existing filer and share the changes through a Merge Request. Best, *Joachim Pouderoux*, PhD *Technical Expert - Scientific Computing Team* *Kitware SAS * 2016-11-22 9:42 GMT-04:00 Deij-van Rijswijk, Menno : > > you will have to create a un filter > > > > What is an ?un filter? ? I have never heard of this term. > > > > Thanks and best wishes, > > > > > > Menno Deij ? van Rijswijk > > > > > > *From:* Joachim Pouderoux [mailto:joachim.pouderoux at kitware.com] > *Sent:* Monday, November 21, 2016 7:56 PM > *To:* Deij-van Rijswijk, Menno > *Cc:* paraview-developers at paraview.org > *Subject:* Re: [Paraview-developers] vtkReflectionFilter with multiple > vector fields > > > > Hi, > > Bad news is that you just can't. There is this concept of "Active > Vectors", "Active Scalars" etc. on VTK datasetattributes and only one array > can be marked with those tags. > > Then some filters only performs on those attributes, while some other > allow at least the user to specify which array(s) to process - this is not > the case here. > > If you want to perform reflection on all 3-components arrays, you will > have to create a un filter (that will basically perform what the current > one does plus perform the reflections on every arrays that have > 3-components). > > Best, > > Joachim > > > *Joachim Pouderoux*, PhD > > *Technical Expert - Scientific Computing Team* > *Kitware SAS * > > > > 2016-11-21 10:40 GMT-04:00 Deij-van Rijswijk, Menno : > > Hi, > > > > 8 months ago I pushed what I thought was a fix for a problem where data > read from the CGNS reader was not properly mirrored by, e.g., the > vtkReflectionFilter. The data from the CGNS files we use contains multiple > vector fields (velocity, shear stress, you name it). > > > > What I did was to set the vtkDataSetAttributes::VECTORS attribute on all > vector fields in the dataset (thinking that with that attribute set, the > vtkReflectionFilter would work properly). Indeed, my (it turns out > incomplete) tests showed that it did, I was happy, and my fix was merged. > > > > Unfortunately, the users find problems: http://public.kitware.com/ > pipermail/paraview/2016-October/038152.html > > Origin of the problem: my ?fix??. It turns out that if you call > dsa->SetVectors(arr) on multiple arrays, only the last array on which it > was called remains in the list of data arrays. The previous array for which > this attribute was set is removed from the dataset attributes object. > > > > So, my question is: how to do this properly? Looking at the code of the > vtkReflectionFilter I see that it gets ?the vectors? from the dataset. > Unfortunately, in our case there is no concept of ?the vectors?. There are > multiple vector fields that ALL NEED TO GET MIRRORED by the reflection > filter. > > > > Any insight here is very welcome :-) > > > > Best wishes, > > > > > > Menno Deij ? van Rijswijk > > > > > *dr. ir. Menno A. Deij-van Rijswijk | Researcher / Software Engineer | > Maritime Simulation & Software Group* > *MARIN* | T +31 317 49 35 06 | M.Deij at marin.nl | www.marin.nl > > [image: LinkedIn] [image: > YouTube] [image: Twitter] > [image: Facebook] > > MARIN news: 24th HISWA Symposium on Yacht design and Construction great > success > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 293 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 331 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 253 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 333 bytes Desc: not available URL: From mathieu.westphal at kitware.com Fri Nov 25 03:39:08 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Fri, 25 Nov 2016 09:39:08 +0100 Subject: [Paraview-developers] ParaView Release OSX Compilation Message-ID: Hi Who is responsible for compiling the osx version of ParaView release ? Thanks, Mathieu Westphal -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sat Nov 26 21:14:00 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 26 Nov 2016 21:14:00 -0500 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: Mathieu, The Mac OS X release is built by the paraview-superbuild buildbot on bigmac. I kicked off the builds for this release. What's up? Thanks, Cory On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal wrote: > Hi > > Who is responsible for compiling the osx version of ParaView release ? > > Thanks, > > Mathieu Westphal > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From khayam.gondal at gmail.com Sun Nov 27 10:30:34 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Sun, 27 Nov 2016 10:30:34 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data Message-ID: Hi, I have paraview in server-client mode installed. Client is successfully connected to server. But when I try to load data into paraview from GUI, it crashes and on server side shows following errors. Client connected. ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 However same data files work fine on my local system. Any idea whats wrong here? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Nov 27 16:06:41 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 27 Nov 2016 16:06:41 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: Did you build ParaView or are you using a binary release? Could you run the client through a debugger and provide a stack trace where it crashes? That would help get an idea of what might be going on. Thanks, Cory On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal wrote: > Hi, > I have paraview in server-client mode installed. Client is successfully > connected to server. But when I try to load data into paraview from GUI, it > crashes and on server side shows following errors. > > Client connected. > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809 > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > > However same data files work fine on my local system. Any idea whats wrong > here? > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From khayam.gondal at gmail.com Sun Nov 27 16:25:17 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Sun, 27 Nov 2016 16:25:17 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build binary on windows7. Can you tell me how can i start client with debugger? Actually everything i was working fine until I recently rebuild the server and this problem popped up. On Nov 27, 2016 16:06, "Cory Quammen" wrote: > Did you build ParaView or are you using a binary release? > > Could you run the client through a debugger and provide a stack trace > where it crashes? That would help get an idea of what might be going > on. > > Thanks, > Cory > > On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal > wrote: > > Hi, > > I have paraview in server-client mode installed. Client is successfully > > connected to server. But when I try to load data into paraview from GUI, > it > > crashes and on server side shows following errors. > > > > Client connected. > > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line > 809 > > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 > > > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. > > > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. > > > > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > > > > However same data files work fine on my local system. Any idea whats > wrong > > here? > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sun Nov 27 16:37:02 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Sun, 27 Nov 2016 16:37:02 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: Sounds like a mismatch between the code from which the client and server were built. You need to compile the server code with the same code with which the client was built. If your binary is version 5.2.0, then on the server side make sure you are using the 5.2.0 source code, either downloaded from [1] or check out the v5.2.0 tag in the git repository. If you are building from the git repository, make sure you run 'git submodule update' after checking out the v5.2.0 tag and before you compile - that is a common source of problems with client/server communication. HTH, Cory [1] http://www.paraview.org/download/ On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal wrote: > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build binary > on windows7. > Can you tell me how can i start client with debugger? > Actually everything i was working fine until I recently rebuild the server > and this problem popped up. > > > On Nov 27, 2016 16:06, "Cory Quammen" wrote: >> >> Did you build ParaView or are you using a binary release? >> >> Could you run the client through a debugger and provide a stack trace >> where it crashes? That would help get an idea of what might be going >> on. >> >> Thanks, >> Cory >> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal >> wrote: >> > Hi, >> > I have paraview in server-client mode installed. Client is successfully >> > connected to server. But when I try to load data into paraview from GUI, >> > it >> > crashes and on server side shows following errors. >> > >> > Client connected. >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line >> > 809 >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > >> > However same data files work fine on my local system. Any idea whats >> > wrong >> > here? >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. From khayam.gondal at gmail.com Sun Nov 27 17:02:06 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Sun, 27 Nov 2016 17:02:06 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. I downgraded server to RC3 and its working fine now. Thanks On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen wrote: > Sounds like a mismatch between the code from which the client and > server were built. You need to compile the server code with the same > code with which the client was built. If your binary is version 5.2.0, > then on the server side make sure you are using the 5.2.0 source code, > either downloaded from [1] or check out the v5.2.0 tag in the git > repository. If you are building from the git repository, make sure you > run 'git submodule update' after checking out the v5.2.0 tag and > before you compile - that is a common source of problems with > client/server communication. > > HTH, > Cory > > [1] http://www.paraview.org/download/ > > On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal > wrote: > > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build > binary > > on windows7. > > Can you tell me how can i start client with debugger? > > Actually everything i was working fine until I recently rebuild the > server > > and this problem popped up. > > > > > > On Nov 27, 2016 16:06, "Cory Quammen" wrote: > >> > >> Did you build ParaView or are you using a binary release? > >> > >> Could you run the client through a debugger and provide a stack trace > >> where it crashes? That would help get an idea of what might be going > >> on. > >> > >> Thanks, > >> Cory > >> > >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal < > khayam.gondal at gmail.com> > >> wrote: > >> > Hi, > >> > I have paraview in server-client mode installed. Client is > successfully > >> > connected to server. But when I try to load data into paraview from > GUI, > >> > it > >> > crashes and on server side shows following errors. > >> > > >> > Client connected. > >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line > >> > 809 > >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken > pipe. > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken > pipe. > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > > >> > However same data files work fine on my local system. Any idea whats > >> > wrong > >> > here? > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.westphal at kitware.com Mon Nov 28 02:57:22 2016 From: mathieu.westphal at kitware.com (Mathieu Westphal) Date: Mon, 28 Nov 2016 08:57:22 +0100 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: Couldn't we add a version check during client connection ? On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: > That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. > I downgraded server to RC3 and its working fine now. Thanks > > On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen > wrote: > >> Sounds like a mismatch between the code from which the client and >> server were built. You need to compile the server code with the same >> code with which the client was built. If your binary is version 5.2.0, >> then on the server side make sure you are using the 5.2.0 source code, >> either downloaded from [1] or check out the v5.2.0 tag in the git >> repository. If you are building from the git repository, make sure you >> run 'git submodule update' after checking out the v5.2.0 tag and >> before you compile - that is a common source of problems with >> client/server communication. >> >> HTH, >> Cory >> >> [1] http://www.paraview.org/download/ >> >> On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal >> wrote: >> > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build >> binary >> > on windows7. >> > Can you tell me how can i start client with debugger? >> > Actually everything i was working fine until I recently rebuild the >> server >> > and this problem popped up. >> > >> > >> > On Nov 27, 2016 16:06, "Cory Quammen" wrote: >> >> >> >> Did you build ParaView or are you using a binary release? >> >> >> >> Could you run the client through a debugger and provide a stack trace >> >> where it crashes? That would help get an idea of what might be going >> >> on. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal < >> khayam.gondal at gmail.com> >> >> wrote: >> >> > Hi, >> >> > I have paraview in server-client mode installed. Client is >> successfully >> >> > connected to server. But when I try to load data into paraview from >> GUI, >> >> > it >> >> > crashes and on server side shows following errors. >> >> > >> >> > Client connected. >> >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >> line >> >> > 809 >> >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >> pipe. >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >> pipe. >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > >> >> > However same data files work fine on my local system. Any idea whats >> >> > wrong >> >> > here? >> >> > >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Search the list archives at: >> >> > http://markmail.org/search/?q=Paraview-developers >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> Staff R&D Engineer >> >> Kitware, Inc. >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bastien.jacquet at kitware.com Mon Nov 28 05:33:55 2016 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Mon, 28 Nov 2016 11:33:55 +0100 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: Hello Cory, It was actually a request from me. A customer wants his pv plugin distributed as a binary, compatible with Paraview official binary. Their main OS is OS X. Can you point me to the right path to do so ? Thanks, Bastien Bastien Jacquet, PhD Technical Leader - Computer Vision Team Kitware SAS 26 rue Louis Gu?rin - 69100 Villeurbanne - France F: +33 (0)4.37.45.04.15 On Sun, Nov 27, 2016 at 3:14 AM, Cory Quammen wrote: > Mathieu, > > The Mac OS X release is built by the paraview-superbuild buildbot on > bigmac. I kicked off the builds for this release. What's up? > > Thanks, > Cory > > On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal > wrote: > > Hi > > > > Who is responsible for compiling the osx version of ParaView release ? > > > > Thanks, > > > > Mathieu Westphal > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Mon Nov 28 08:53:30 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Mon, 28 Nov 2016 08:53:30 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: I think it do a version check for 5.X releases but not for RC releases. On Nov 28, 2016 2:57 AM, "Mathieu Westphal" wrote: > Couldn't we add a version check during client connection ? > > On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: > >> That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. >> I downgraded server to RC3 and its working fine now. Thanks >> >> On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen >> wrote: >> >>> Sounds like a mismatch between the code from which the client and >>> server were built. You need to compile the server code with the same >>> code with which the client was built. If your binary is version 5.2.0, >>> then on the server side make sure you are using the 5.2.0 source code, >>> either downloaded from [1] or check out the v5.2.0 tag in the git >>> repository. If you are building from the git repository, make sure you >>> run 'git submodule update' after checking out the v5.2.0 tag and >>> before you compile - that is a common source of problems with >>> client/server communication. >>> >>> HTH, >>> Cory >>> >>> [1] http://www.paraview.org/download/ >>> >>> On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal >>> wrote: >>> > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build >>> binary >>> > on windows7. >>> > Can you tell me how can i start client with debugger? >>> > Actually everything i was working fine until I recently rebuild the >>> server >>> > and this problem popped up. >>> > >>> > >>> > On Nov 27, 2016 16:06, "Cory Quammen" >>> wrote: >>> >> >>> >> Did you build ParaView or are you using a binary release? >>> >> >>> >> Could you run the client through a debugger and provide a stack trace >>> >> where it crashes? That would help get an idea of what might be going >>> >> on. >>> >> >>> >> Thanks, >>> >> Cory >>> >> >>> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal < >>> khayam.gondal at gmail.com> >>> >> wrote: >>> >> > Hi, >>> >> > I have paraview in server-client mode installed. Client is >>> successfully >>> >> > connected to server. But when I try to load data into paraview from >>> GUI, >>> >> > it >>> >> > crashes and on server side shows following errors. >>> >> > >>> >> > Client connected. >>> >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >>> line >>> >> > 809 >>> >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >>> >> > >>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>> pipe. >>> >> > >>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>> pipe. >>> >> > >>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>> >> > >>> >> > However same data files work fine on my local system. Any idea whats >>> >> > wrong >>> >> > here? >>> >> > >>> >> > >>> >> > _______________________________________________ >>> >> > Powered by www.kitware.com >>> >> > >>> >> > Visit other Kitware open-source projects at >>> >> > http://www.kitware.com/opensource/opensource.html >>> >> > >>> >> > Search the list archives at: >>> >> > http://markmail.org/search/?q=Paraview-developers >>> >> > >>> >> > Follow this link to subscribe/unsubscribe: >>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> > >>> >> >>> >> >>> >> >>> >> -- >>> >> Cory Quammen >>> >> Staff R&D Engineer >>> >> Kitware, Inc. >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Nov 28 10:19:25 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 28 Nov 2016 10:19:25 -0500 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: Bastien and Mathieu, The best thing would be to build against the ParaView SDK. I don't think this is available in the Mac builds, though, and I'm not sure it is available for other OS's either. Utkarsh, am I wrong about this? I don't see anything in the ParaView.app that looks like an SDK. In some cases we have shipped these kinds of plugins with the ParaView binaries and leave them unloaded by default. See the GeodesicMeasurement plugin, for instance. If the plugin is proprietary, that won't work, though. Otherwise, to be compatible with the official 5.2 binary, you would need to have a 5.2 build of ParaView on bigmac, which is the buildbot that produces the binaries, and build your plugin against that. Checkout the v5.2.0 tag in the superbuild and set the build options to those used for the official binary which are listed in one of the buildbot superbuilds, e.g., https://buildbot.kitware.com/builders/paraview-bigmac-osx-shared-release%2Bopengl2%2Bosx10.8%2Bqt4%2Bsuperbuild/builds/186 It may be more practical to build a custom ParaView binary on a Mac you have on hand along with the plugin and distribute those to your customer, especially if the plugin will be changing in the future. Hope that helps, Cory On Mon, Nov 28, 2016 at 5:33 AM, Bastien Jacquet wrote: > Hello Cory, > > It was actually a request from me. A customer wants his pv plugin > distributed as a binary, compatible with Paraview official binary. Their > main OS is OS X. > Can you point me to the right path to do so ? > > Thanks, > Bastien > > Bastien Jacquet, PhD > Technical Leader - Computer Vision Team > Kitware SAS > 26 rue Louis Gu?rin - 69100 Villeurbanne - France > F: +33 (0)4.37.45.04.15 > > On Sun, Nov 27, 2016 at 3:14 AM, Cory Quammen > wrote: >> >> Mathieu, >> >> The Mac OS X release is built by the paraview-superbuild buildbot on >> bigmac. I kicked off the builds for this release. What's up? >> >> Thanks, >> Cory >> >> On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal >> wrote: >> > Hi >> > >> > Who is responsible for compiling the osx version of ParaView release ? >> > >> > Thanks, >> > >> > Mathieu Westphal >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From cory.quammen at kitware.com Mon Nov 28 13:03:32 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 28 Nov 2016 13:03:32 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: On Mon, Nov 28, 2016 at 8:53 AM, Khayam Gondal wrote: > I think it do a version check for 5.X releases but not for RC releases. Yes, the handshake between client and server just checks that the string "." is the same on the client and server. There typically shouldn't be protocol changes between release candidates, so this level of version checking should normally be reasonable. Ideally, we would like a 5.2.0 client to be able to connect to a 5.2.1 server and vice versa, so connections between different RCs should be possible, too. Obviously, that didn't happen in this release candidate phase. Between RC3 and RC4 there were some options added to the NetCDF reader. Changing proxy properties changes the client/server protocol and makes them incompatible, IIUC. - Cory > On Nov 28, 2016 2:57 AM, "Mathieu Westphal" > wrote: >> >> Couldn't we add a version check during client connection ? >> >> On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: >>> >>> That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. >>> I downgraded server to RC3 and its working fine now. Thanks >>> >>> On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen >>> wrote: >>>> >>>> Sounds like a mismatch between the code from which the client and >>>> server were built. You need to compile the server code with the same >>>> code with which the client was built. If your binary is version 5.2.0, >>>> then on the server side make sure you are using the 5.2.0 source code, >>>> either downloaded from [1] or check out the v5.2.0 tag in the git >>>> repository. If you are building from the git repository, make sure you >>>> run 'git submodule update' after checking out the v5.2.0 tag and >>>> before you compile - that is a common source of problems with >>>> client/server communication. >>>> >>>> HTH, >>>> Cory >>>> >>>> [1] http://www.paraview.org/download/ >>>> >>>> On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal >>>> wrote: >>>> > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build >>>> > binary >>>> > on windows7. >>>> > Can you tell me how can i start client with debugger? >>>> > Actually everything i was working fine until I recently rebuild the >>>> > server >>>> > and this problem popped up. >>>> > >>>> > >>>> > On Nov 27, 2016 16:06, "Cory Quammen" >>>> > wrote: >>>> >> >>>> >> Did you build ParaView or are you using a binary release? >>>> >> >>>> >> Could you run the client through a debugger and provide a stack trace >>>> >> where it crashes? That would help get an idea of what might be going >>>> >> on. >>>> >> >>>> >> Thanks, >>>> >> Cory >>>> >> >>>> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal >>>> >> >>>> >> wrote: >>>> >> > Hi, >>>> >> > I have paraview in server-client mode installed. Client is >>>> >> > successfully >>>> >> > connected to server. But when I try to load data into paraview from >>>> >> > GUI, >>>> >> > it >>>> >> > crashes and on server side shows following errors. >>>> >> > >>>> >> > Client connected. >>>> >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >>>> >> > line >>>> >> > 809 >>>> >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>>> >> > pipe. >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>>> >> > pipe. >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > >>>> >> > However same data files work fine on my local system. Any idea >>>> >> > whats >>>> >> > wrong >>>> >> > here? >>>> >> > >>>> >> > >>>> >> > _______________________________________________ >>>> >> > Powered by www.kitware.com >>>> >> > >>>> >> > Visit other Kitware open-source projects at >>>> >> > http://www.kitware.com/opensource/opensource.html >>>> >> > >>>> >> > Search the list archives at: >>>> >> > http://markmail.org/search/?q=Paraview-developers >>>> >> > >>>> >> > Follow this link to subscribe/unsubscribe: >>>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >> > >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Cory Quammen >>>> >> Staff R&D Engineer >>>> >> Kitware, Inc. >>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: >>> http://markmail.org/search/?q=Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Mon Nov 28 13:31:33 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 28 Nov 2016 18:31:33 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Paraview client crashes while loading data In-Reply-To: References: Message-ID: <7318fd853b194a3cacce5acfd917f8b7@ES01AMSNLNT.srn.sandia.gov> This has given me issues in the past also. We need to have better reporting if possible. I wrote it up here: https://gitlab.kitware.com/paraview/paraview/issues/17052 Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Mathieu Westphal Sent: Monday, November 28, 2016 12:57 AM To: Khayam Gondal Cc: ParaView Developers Subject: [EXTERNAL] Re: [Paraview-developers] Paraview client crashes while loading data Couldn't we add a version check during client connection ? On 27 Nov 2016 11:02 pm, "Khayam Gondal" > wrote: That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. I downgraded server to RC3 and its working fine now. Thanks On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen > wrote: Sounds like a mismatch between the code from which the client and server were built. You need to compile the server code with the same code with which the client was built. If your binary is version 5.2.0, then on the server side make sure you are using the 5.2.0 source code, either downloaded from [1] or check out the v5.2.0 tag in the git repository. If you are building from the git repository, make sure you run 'git submodule update' after checking out the v5.2.0 tag and before you compile - that is a common source of problems with client/server communication. HTH, Cory [1] http://www.paraview.org/download/ On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal > wrote: > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build binary > on windows7. > Can you tell me how can i start client with debugger? > Actually everything i was working fine until I recently rebuild the server > and this problem popped up. > > > On Nov 27, 2016 16:06, "Cory Quammen" > wrote: >> >> Did you build ParaView or are you using a binary release? >> >> Could you run the client through a debugger and provide a stack trace >> where it crashes? That would help get an idea of what might be going >> on. >> >> Thanks, >> Cory >> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal > >> wrote: >> > Hi, >> > I have paraview in server-client mode installed. Client is successfully >> > connected to server. But when I try to load data into paraview from GUI, >> > it >> > crashes and on server side shows following errors. >> > >> > Client connected. >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line >> > 809 >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken pipe. >> > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> > >> > However same data files work fine on my local system. Any idea whats >> > wrong >> > here? >> > >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Search the list archives at: >> > http://markmail.org/search/?q=Paraview-developers >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Nov 28 13:17:59 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 28 Nov 2016 13:17:59 -0500 Subject: [Paraview-developers] Linker error with custom plugin In-Reply-To: References: Message-ID: Gregory, I assume you are getting linker errors when the code #FIND_LIBRARY(FilterB NAMES FilterB NO_MODULE) #TARGET_LINK_LIBRARIES(FilterA LINK_PRIVATE FilterB) is uncommented. Is that correct? Are your two plugins in two different CMake projects, or are they in one project? My suggestion would be to have them in one project with a top-level CMakeLists.txt file that adds the B filter subdirectory before the A filter subdirectory, then uncommenting those lines above. HTH, Cory On Sat, Nov 19, 2016 at 7:44 PM, Gr?gory Zaccaro wrote: > Hello, > > I have troubles to compile a custom plugin which instantiate another custom > plugin. > Let's say I want to build a custom plugin A which uses another custom plugin > B. Right now, I get linker errors when compiling plugin A. I built Paraview > from sources with "BUILD_SHARED_LIBS = ON". > > > The Cmake file of the plugin A looks like this : > > PROJECT(FilterA) > > INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) > FIND_PACKAGE(ParaView REQUIRED) > INCLUDE(${PARAVIEW_USE_FILE}) > > INCLUDE(ParaViewBranding) > INCLUDE(ParaViewPlugins) > > ADD_PARAVIEW_PLUGIN(FilterA "1.0" > SERVER_MANAGER_XML vtkFilterA.xml > SERVER_MANAGER_SOURCES vtkFilterA.cxx) > > #FIND_LIBRARY(FilterB NAMES FilterB NO_MODULE) > #TARGET_LINK_LIBRARIES(FilterA LINK_PRIVATE FilterB) > > > The Cmake file of the plugin B looks like this : > > PROJECT(FilterB) > INCLUDE_DIRECTORIES(${VTK_INCLUDE_DIRS}) > ADD_PARAVIEW_PLUGIN(FilterB "1.0" > SERVER_MANAGER_XML vtkFilterB.xml > SERVER_MANAGER_SOURCES vtkFilterB.cxx) > > > In Visual Studio, I can see FilterB.lib in the list of the additionnal > dependencies but I still get the linkage errors. > > I managed to solve the problem by manually add FilterB.obj to the > additionnal dependencies of plugin A. But I didn't figured out how can I set > Cmake to link the two plugins. > > Any help would be appreciated ! > > Kind regards, > Gregory > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From andy.bauer at kitware.com Mon Nov 28 14:08:54 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Mon, 28 Nov 2016 14:08:54 -0500 Subject: [Paraview-developers] Superbuild failure In-Reply-To: References: Message-ID: Hi Alan, Could you share your CMakeCache.txt from your main build directory and the one from your superbuild/paraview/build subdirectory? I'm assuming you aren't using the system Python and if that's the case I'm thinking that the build failed during trying to build Python and then moved on to building ParaView but couldn't find your Python executable. I could easily be wrong (theoretically PV shouldn't even try to build if the Python build failed) on this but this is my main suspicion on the build. Best, Andy On Wed, Nov 23, 2016 at 8:36 PM, Scott, W Alan wrote: > Sorry for being dense, but I am failing trying to get superbuild to work. > I am failing with ParaView trying to find python2.7 on the system. I am > enabling Python as follows, but believe I am doing nothing else: > ENABLE_python:BOOL=ON. Here is what I get: > > > > [100%] Built target paraview > > Install the project... > > -- Install configuration: "Release" > > -- Configuring done > > -- Generating done > > -- Build files have been written to: /projects/viz/paraview/ > ParaView/5.2.0-sb-mesa/Linux-chama-x86_64/Build/cpack/paraview/TGZ/install > > Install the project... > > -- Install configuration: "Release" > > CMake Error at cmake_install.cmake:45 (message): > > Failed to install pvdataserver: > > > > /usr/bin/env: python2.7: No such file or directory > > > > > > > > gmake[1]: *** [install] Error 1 > > CMake Error at superbuild/cmake_install.cmake:55 (message): > > Failed to install the paraview/TGZ package. > > Call Stack (most recent call first): > > cmake_install.cmake:37 (include) > > > > > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Mon Nov 28 12:31:46 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Mon, 28 Nov 2016 12:31:46 -0500 Subject: [Paraview-developers] Paraview client crashes while loading data In-Reply-To: References: Message-ID: BTW. I am gonna report this as a bug. On Mon, Nov 28, 2016 at 8:53 AM, Khayam Gondal wrote: > I think it do a version check for 5.X releases but not for RC releases. > > On Nov 28, 2016 2:57 AM, "Mathieu Westphal" > wrote: > >> Couldn't we add a version check during client connection ? >> >> On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: >> >>> That indeed was the problem. Client was 5.2.0 RC3 whereas server was >>> RC4. I downgraded server to RC3 and its working fine now. Thanks >>> >>> On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen >>> wrote: >>> >>>> Sounds like a mismatch between the code from which the client and >>>> server were built. You need to compile the server code with the same >>>> code with which the client was built. If your binary is version 5.2.0, >>>> then on the server side make sure you are using the 5.2.0 source code, >>>> either downloaded from [1] or check out the v5.2.0 tag in the git >>>> repository. If you are building from the git repository, make sure you >>>> run 'git submodule update' after checking out the v5.2.0 tag and >>>> before you compile - that is a common source of problems with >>>> client/server communication. >>>> >>>> HTH, >>>> Cory >>>> >>>> [1] http://www.paraview.org/download/ >>>> >>>> On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal >>>> wrote: >>>> > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build >>>> binary >>>> > on windows7. >>>> > Can you tell me how can i start client with debugger? >>>> > Actually everything i was working fine until I recently rebuild the >>>> server >>>> > and this problem popped up. >>>> > >>>> > >>>> > On Nov 27, 2016 16:06, "Cory Quammen" >>>> wrote: >>>> >> >>>> >> Did you build ParaView or are you using a binary release? >>>> >> >>>> >> Could you run the client through a debugger and provide a stack trace >>>> >> where it crashes? That would help get an idea of what might be going >>>> >> on. >>>> >> >>>> >> Thanks, >>>> >> Cory >>>> >> >>>> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal < >>>> khayam.gondal at gmail.com> >>>> >> wrote: >>>> >> > Hi, >>>> >> > I have paraview in server-client mode installed. Client is >>>> successfully >>>> >> > connected to server. But when I try to load data into paraview >>>> from GUI, >>>> >> > it >>>> >> > crashes and on server side shows following errors. >>>> >> > >>>> >> > Client connected. >>>> >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, >>>> line >>>> >> > 809 >>>> >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>>> pipe. >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >>>> pipe. >>>> >> > >>>> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >>>> >> > >>>> >> > However same data files work fine on my local system. Any idea >>>> whats >>>> >> > wrong >>>> >> > here? >>>> >> > >>>> >> > >>>> >> > _______________________________________________ >>>> >> > Powered by www.kitware.com >>>> >> > >>>> >> > Visit other Kitware open-source projects at >>>> >> > http://www.kitware.com/opensource/opensource.html >>>> >> > >>>> >> > Search the list archives at: >>>> >> > http://markmail.org/search/?q=Paraview-developers >>>> >> > >>>> >> > Follow this link to subscribe/unsubscribe: >>>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>>> >> > >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Cory Quammen >>>> >> Staff R&D Engineer >>>> >> Kitware, Inc. >>>> >>>> >>>> >>>> -- >>>> Cory Quammen >>>> Staff R&D Engineer >>>> Kitware, Inc. >>>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Search the list archives at: http://markmail.org/search/?q= >>> Paraview-developers >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview-developers >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Nov 28 14:47:35 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 28 Nov 2016 14:47:35 -0500 Subject: [Paraview-developers] Superbuild failure In-Reply-To: References: Message-ID: Andy, Just FYI, I also followed up with Alan off list. My guess is that some Python script with the line "#! /usr/bin/env python2.7 is being called, but Allen's system does not have a python2.7 binary installed. There is such a call in the twisted test_dist.py file under paraview/VTK/ThirdParty/Twisted/twisted/python/test/test_dist.py that could be the offender, but I'm not entirely sure it is being called during the installation step. Thanks, Cory On Mon, Nov 28, 2016 at 2:08 PM, Andy Bauer wrote: > Hi Alan, > > Could you share your CMakeCache.txt from your main build directory and the > one from your superbuild/paraview/build subdirectory? I'm assuming you > aren't using the system Python and if that's the case I'm thinking that the > build failed during trying to build Python and then moved on to building > ParaView but couldn't find your Python executable. I could easily be wrong > (theoretically PV shouldn't even try to build if the Python build failed) on > this but this is my main suspicion on the build. > > Best, > Andy > > On Wed, Nov 23, 2016 at 8:36 PM, Scott, W Alan wrote: >> >> Sorry for being dense, but I am failing trying to get superbuild to work. >> I am failing with ParaView trying to find python2.7 on the system. I am >> enabling Python as follows, but believe I am doing nothing else: >> ENABLE_python:BOOL=ON. Here is what I get: >> >> >> >> [100%] Built target paraview >> >> Install the project... >> >> -- Install configuration: "Release" >> >> -- Configuring done >> >> -- Generating done >> >> -- Build files have been written to: >> /projects/viz/paraview/ParaView/5.2.0-sb-mesa/Linux-chama-x86_64/Build/cpack/paraview/TGZ/install >> >> Install the project... >> >> -- Install configuration: "Release" >> >> CMake Error at cmake_install.cmake:45 (message): >> >> Failed to install pvdataserver: >> >> >> >> /usr/bin/env: python2.7: No such file or directory >> >> >> >> >> >> >> >> gmake[1]: *** [install] Error 1 >> >> CMake Error at superbuild/cmake_install.cmake:55 (message): >> >> Failed to install the paraview/TGZ package. >> >> Call Stack (most recent call first): >> >> cmake_install.cmake:37 (include) >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0822 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From wascott at sandia.gov Mon Nov 28 14:48:56 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Mon, 28 Nov 2016 19:48:56 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild failure In-Reply-To: References: Message-ID: Sorry guys, still digging out from a wonderful weekend. Will get to this later this afternoon. Alan -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Monday, November 28, 2016 12:48 PM To: Andy Bauer Cc: Scott, W Alan ; paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] Superbuild failure Andy, Just FYI, I also followed up with Alan off list. My guess is that some Python script with the line "#! /usr/bin/env python2.7 is being called, but Allen's system does not have a python2.7 binary installed. There is such a call in the twisted test_dist.py file under paraview/VTK/ThirdParty/Twisted/twisted/python/test/test_dist.py that could be the offender, but I'm not entirely sure it is being called during the installation step. Thanks, Cory On Mon, Nov 28, 2016 at 2:08 PM, Andy Bauer wrote: > Hi Alan, > > Could you share your CMakeCache.txt from your main build directory and > the one from your superbuild/paraview/build subdirectory? I'm assuming > you aren't using the system Python and if that's the case I'm thinking > that the build failed during trying to build Python and then moved on > to building ParaView but couldn't find your Python executable. I could > easily be wrong (theoretically PV shouldn't even try to build if the > Python build failed) on this but this is my main suspicion on the build. > > Best, > Andy > > On Wed, Nov 23, 2016 at 8:36 PM, Scott, W Alan wrote: >> >> Sorry for being dense, but I am failing trying to get superbuild to work. >> I am failing with ParaView trying to find python2.7 on the system. I >> am enabling Python as follows, but believe I am doing nothing else: >> ENABLE_python:BOOL=ON. Here is what I get: >> >> >> >> [100%] Built target paraview >> >> Install the project... >> >> -- Install configuration: "Release" >> >> -- Configuring done >> >> -- Generating done >> >> -- Build files have been written to: >> /projects/viz/paraview/ParaView/5.2.0-sb-mesa/Linux-chama-x86_64/Buil >> d/cpack/paraview/TGZ/install >> >> Install the project... >> >> -- Install configuration: "Release" >> >> CMake Error at cmake_install.cmake:45 (message): >> >> Failed to install pvdataserver: >> >> >> >> /usr/bin/env: python2.7: No such file or directory >> >> >> >> >> >> >> >> gmake[1]: *** [install] Error 1 >> >> CMake Error at superbuild/cmake_install.cmake:55 (message): >> >> Failed to install the paraview/TGZ package. >> >> Call Stack (most recent call first): >> >> cmake_install.cmake:37 (include) >> >> >> >> >> >> >> >> Thanks, >> >> >> >> Alan >> >> >> >> -------------------------------------------------------- >> >> W. Alan Scott >> >> ParaView Support Manager >> >> >> >> SAIC >> >> Sandia National Laboratories, MS 0822 >> >> Org 9326 - Building 880 A1-K >> >> (505) 284-0932 FAX (505) 284-5619 >> >> --------------------------------------------------------- >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From chuck.atkins at kitware.com Tue Nov 29 12:16:29 2016 From: chuck.atkins at kitware.com (Chuck Atkins) Date: Tue, 29 Nov 2016 12:16:29 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Superbuild failure In-Reply-To: References: Message-ID: It looks like a bug with superbuild/cmake/scripts/fixup_bundle.unix.py . In particular, it should be using the superbuild's python. We should be able to fix it by pushing the staging install/bin into the front of the path before executing the script. In particular, some path manipulation in superbuild/cmake/scripts/fixup_python.unix.cmake around line 41 ---------- Chuck Atkins Staff R&D Engineer, Scientific Computing Kitware, Inc. On Mon, Nov 28, 2016 at 2:48 PM, Scott, W Alan wrote: > Sorry guys, still digging out from a wonderful weekend. Will get to this > later this afternoon. > > Alan > > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: Monday, November 28, 2016 12:48 PM > To: Andy Bauer > Cc: Scott, W Alan ; paraview-developers at paraview.org > Subject: [EXTERNAL] Re: [Paraview-developers] Superbuild failure > > Andy, > > Just FYI, I also followed up with Alan off list. My guess is that some > Python script with the line > > "#! /usr/bin/env python2.7 > > is being called, but Allen's system does not have a python2.7 binary > installed. There is such a call in the twisted test_dist.py file under > paraview/VTK/ThirdParty/Twisted/twisted/python/test/test_dist.py that > could be the offender, but I'm not entirely sure it is being called during > the installation step. > > Thanks, > Cory > > On Mon, Nov 28, 2016 at 2:08 PM, Andy Bauer > wrote: > > Hi Alan, > > > > Could you share your CMakeCache.txt from your main build directory and > > the one from your superbuild/paraview/build subdirectory? I'm assuming > > you aren't using the system Python and if that's the case I'm thinking > > that the build failed during trying to build Python and then moved on > > to building ParaView but couldn't find your Python executable. I could > > easily be wrong (theoretically PV shouldn't even try to build if the > > Python build failed) on this but this is my main suspicion on the build. > > > > Best, > > Andy > > > > On Wed, Nov 23, 2016 at 8:36 PM, Scott, W Alan > wrote: > >> > >> Sorry for being dense, but I am failing trying to get superbuild to > work. > >> I am failing with ParaView trying to find python2.7 on the system. I > >> am enabling Python as follows, but believe I am doing nothing else: > >> ENABLE_python:BOOL=ON. Here is what I get: > >> > >> > >> > >> [100%] Built target paraview > >> > >> Install the project... > >> > >> -- Install configuration: "Release" > >> > >> -- Configuring done > >> > >> -- Generating done > >> > >> -- Build files have been written to: > >> /projects/viz/paraview/ParaView/5.2.0-sb-mesa/Linux-chama-x86_64/Buil > >> d/cpack/paraview/TGZ/install > >> > >> Install the project... > >> > >> -- Install configuration: "Release" > >> > >> CMake Error at cmake_install.cmake:45 (message): > >> > >> Failed to install pvdataserver: > >> > >> > >> > >> /usr/bin/env: python2.7: No such file or directory > >> > >> > >> > >> > >> > >> > >> > >> gmake[1]: *** [install] Error 1 > >> > >> CMake Error at superbuild/cmake_install.cmake:55 (message): > >> > >> Failed to install the paraview/TGZ package. > >> > >> Call Stack (most recent call first): > >> > >> cmake_install.cmake:37 (include) > >> > >> > >> > >> > >> > >> > >> > >> Thanks, > >> > >> > >> > >> Alan > >> > >> > >> > >> -------------------------------------------------------- > >> > >> W. Alan Scott > >> > >> ParaView Support Manager > >> > >> > >> > >> SAIC > >> > >> Sandia National Laboratories, MS 0822 > >> > >> Org 9326 - Building 880 A1-K > >> > >> (505) 284-0932 FAX (505) 284-5619 > >> > >> --------------------------------------------------------- > >> > >> > >> > >> > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Search the list archives at: > > http://markmail.org/search/?q=Paraview-developers > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Tue Nov 29 12:43:24 2016 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 29 Nov 2016 12:43:24 -0500 Subject: [Paraview-developers] Linker error building Fortran90FullExample In-Reply-To: <0410d0f9fb3c652bb70a612fa5ce682e.startmail@www.startmail.com> References: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com> <149dbde7d22543cfc63066dbcd02e71f.startmail@www.startmail.com> <0410d0f9fb3c652bb70a612fa5ce682e.startmail@www.startmail.com> Message-ID: Hi Thomas, Would you want to add a MR for your changes on gitlab? Yes, Fortran and C/C++ loop through memory in multidimensional arrays differently but in the end it's a flat memory layout so it can be managed. I'm not sure what the error you're seeing is from. If you add a bug report for that on gitlab I may be able to get to that as well. Thanks, Andy On Sat, Nov 19, 2016 at 10:09 AM, wrote: > Hi Andy, > > I ran ctest from the windows cmd, but couldn't make sense of the output. > Anyhow, I guess the segmentation fault was due to a wrong declaration of > the rank 3 Fortran array of type complex in the procedure interface I > provided for the C++ function addfield(). I changed it to be type(c_ptr) as > the function expects a double pointer. Afterwards the test ran > successfully. > > Nevertheless, it remains a mystery to me how the reference to the rank 3 > array is properly handled in addfield(), as Fortran and C++ use different > memory layouts for multidimensional arrays; I guess it's still not correct, > even though there is no segmentation fault shown. > > I set the input of EnableLiveVisualization() in coproc.py to True and > tried to visualize the simulation, but its duration is too short - the test > finishes already after a few seconds. Only once I could sneak a peak to the > cube in Paraview, but I got following error message (in Paraview) right > before the simulation stopped: > > ERROR: In C:\Kitware\ParaView-v5.1.2\VTK\Parallel\Core\vtkSocketCommunicator.cxx, > line 809 > vtkSocketCommunicator (000001E68C21B360): Could not receive tag. 1 > > Best, > Thomas > > > > Am Sonntag, 13. November 2016 14:40 schrieb Andy Bauer < > andy.bauer at kitware.com>: > > > Hi Thomas, > > Can you run ctest -V to get verbose output out of the run? That may shed > some light on what the issue is. My guess is that it's not finding the > coproc.py script. Also, the verbose output for ctest will show you how you > can run the test manually which may be useful. > > Cheers, > Andy > > On Fri, Nov 11, 2016 at 2:50 PM, wrote: > > To resolve the references inclusion of header files "CPythonAdaptorAPI.h" > and "CAdaptorAPI.h" in FECxxAdaptor.cxx was required, as they declare the > missing functions. > Afterwards, I provided the corresponding procedure interfaces in the > Fortran files and finally got through the static linking stage. > > Now, when I start the RUN_TESTS project, the Fortran90FullExampleTest > fails due to a segmentation fault: > > 1/1 Test #1: Fortran90FullExampleTest .........***Exception: SegFault > 8.48 sec > 1> > 1> 0% tests passed, 1 tests failed out of 1 > 1> > 1> Label Time Summary: > 1> CATALYST = 8.48 sec (1 test) > 1> PARAVIEW = 8.48 sec (1 test) > 1> > 1> Total Test time (real) = 8.48 sec > 1> > 1> The following tests FAILED: > 1> 1 - Fortran90FullExampleTest (SEGFAULT) > 1> Errors while running CTest > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: The command > "setlocal > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: > C:\cmake\bin\ctest.exe --force-new-ctest-process -C Debug > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if > %errorlevel% neq 0 goto :cmEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: endlocal & > call :cmErrorLevel %errorlevel% & goto :cmDone > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: > :cmErrorLevel > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: exit /b %1 > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :cmDone > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: if > %errorlevel% neq 0 goto :VCEnd > 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V140\Microsoft.CppCommon.targets(133,5): error MSB3073: :VCEnd" > exited with code 8. > > Does anybody know how to solve this? > > Best, > Thomas > > Am Donnerstag, 10. November 2016 19:10 schrieb thomasblome at startmail.com: > > > Hi Andy, > > The linker error concerning the missing main method was due to a wrong > solution setup of the Fortran90FullExample in VS. > The CMakeLists file provided generates only one single (C++) project in > VS, which means all .f90 files will be ignored by the compiler (it's > impossible to have a single Fortran/C++ mixed language project in VS). > To solve this I had to configure the CMakeLists file to create a library > from FECxxAdaptor.cxx and link it with the Fortran90FullExample. > > Other linker & compiler errors occurred with regards to mpi: > 1) the target_link_libraries command in the CMakeLists file links > ${MPI_Fortran_LIBRARIES} to the fortran project, > but it forgets to link with msmpifec.lib (see also: > http://public.kitware.com/pipermail/cmake/2016-February/062861.html). > 2) The specification of an include directory (containing header mpifptr.h) > was missing. > > Another problem arose when it comes to the the by hand name mangling for > fortran in FECxxAdaptor.cxx. > To get rid of that I introduced function interfaces in the > FEFortranAdaptor.f90 file and now it works independently of the Fortran > compiler used. > > Now, there are only five remaining linker errors as shown below: > > LNK2019: unresolved external symbol COPROCESS referenced in function > TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > LNK2019: unresolved external symbol COPROCESSORINITIALIZEWITHPYTHON > referenced in function MAIN__ FEDriver.obj > LNK2019: unresolved external symbol COPROCESSORFINALIZE referenced in > function MAIN__ FEDriver.obj > LNK2019: unresolved external symbol NEEDTOCREATEGRID referenced in > function TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > LNK2019: unresolved external symbol REQUESTDATADESCRIPTION referenced in > function TCP_mp_TESTCOPROCESSOR FEFortranAdaptor.obj > > In the ParaViewCatalystUsersGuide_v2 the missing symbols appear to be > declared in CAdaptorAPI.h and CPythonAdaptorAPI.h (but NEEDTOCREATEGRID), > but I can't just include them in the Fortran code. > > Can you tell me how to resolve those missing references? > > Best, > Thomas > > > Am Mittwoch, 26. Oktober 2016 18:47 schrieb Andy Bauer < > andy.bauer at kitware.com>: > > > Hi Thomas, > > I really don't know about this. Do you get the same behavior if you don't > link with Catalyst? Can you create a simple helloworld.f90 example that > works? > > Best, > Andy > > On Wed, Oct 26, 2016 at 3:39 AM, wrote: > > Hi Andy, > > I have changed both lines from coproc to main, but the error message > remains the same. > > Best, > Thomas > > Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer < > andy.bauer at kitware.com>: > > > Hi Thomas, > > If you change from coproc to main in the "program" and "end program" lines > in FEDriver.f90 does that fix the problem? > > I'm working on a fix for this but don't have access to any MSVS compilers. > > Thanks, > Andy > > On Sat, Oct 22, 2016 at 1:46 PM, wrote: > > Hello, > > I'm trying to compile the Fortran90FullExample using MSVS (Intel Fortran > Compiler 2017 and Visual C++ 2015 compiler). > Doing so I'm getting following linker error: > > Error LNK2019 unresolved external symbol main referenced in function > "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ) > Fortran90FullExample. > > Obviously, the source code doesn't contain a main method at all, since the > entry point is given by the fortran program in file 'FEDriver.f90'. > Nevertheless, I guess the compiler internally creates a main method, and > the linker cannot resolve the reference due to a name mangling problem, as > there are different compilers involved. But I'm not quite sure about that, > nor how to solve it, at that matter. > > Can you give me a hint how to solve that problem? > > Kind regards, > Thomas > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Tue Nov 29 13:37:35 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Tue, 29 Nov 2016 13:37:35 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Paraview client crashes while loading data In-Reply-To: <7318fd853b194a3cacce5acfd917f8b7@ES01AMSNLNT.srn.sandia.gov> References: <7318fd853b194a3cacce5acfd917f8b7@ES01AMSNLNT.srn.sandia.gov> Message-ID: I think its also an issue with pvserver, version I used was version 5.2.0-40-g1e720c3. It might be an experimental build. When I downgraded server version 5.2.0-RC3, it started working fine with Both clients RC3 7RC4. However I still reported it here. https://gitlab.kitware.com/paraview/paraview/issues/17053 On Mon, Nov 28, 2016 at 1:31 PM, Scott, W Alan wrote: > This has given me issues in the past also. We need to have better > reporting if possible. I wrote it up here: > > > > https://gitlab.kitware.com/paraview/paraview/issues/17052 > > > > Alan > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *Mathieu Westphal > *Sent:* Monday, November 28, 2016 12:57 AM > *To:* Khayam Gondal > *Cc:* ParaView Developers > *Subject:* [EXTERNAL] Re: [Paraview-developers] Paraview client crashes > while loading data > > > > Couldn't we add a version check during client connection ? > > > > On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: > > That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. > I downgraded server to RC3 and its working fine now. Thanks > > > > On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen > wrote: > > Sounds like a mismatch between the code from which the client and > server were built. You need to compile the server code with the same > code with which the client was built. If your binary is version 5.2.0, > then on the server side make sure you are using the 5.2.0 source code, > either downloaded from [1] or check out the v5.2.0 tag in the git > repository. If you are building from the git repository, make sure you > run 'git submodule update' after checking out the v5.2.0 tag and > before you compile - that is a common source of problems with > client/server communication. > > HTH, > Cory > > [1] http://www.paraview.org/download/ > > > On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal > wrote: > > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build > binary > > on windows7. > > Can you tell me how can i start client with debugger? > > Actually everything i was working fine until I recently rebuild the > server > > and this problem popped up. > > > > > > On Nov 27, 2016 16:06, "Cory Quammen" wrote: > >> > >> Did you build ParaView or are you using a binary release? > >> > >> Could you run the client through a debugger and provide a stack trace > >> where it crashes? That would help get an idea of what might be going > >> on. > >> > >> Thanks, > >> Cory > >> > >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal < > khayam.gondal at gmail.com> > >> wrote: > >> > Hi, > >> > I have paraview in server-client mode installed. Client is > successfully > >> > connected to server. But when I try to load data into paraview from > GUI, > >> > it > >> > crashes and on server side shows following errors. > >> > > >> > Client connected. > >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line > >> > 809 > >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken > pipe. > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken > pipe. > >> > > >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 > >> > > >> > However same data files work fine on my local system. Any idea whats > >> > wrong > >> > here? > >> > > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khayam.gondal at gmail.com Tue Nov 29 14:00:03 2016 From: khayam.gondal at gmail.com (Khayam Gondal) Date: Tue, 29 Nov 2016 14:00:03 -0500 Subject: [Paraview-developers] Benchmarking Paraview Message-ID: I have to benchmark paraview performance with different configurations such as with single vs multi GPU, with or without MPI support. I want to get results like GPU render time. Parallel IO timings. Server-Client communication latency. But i am kind of stuck here. I don't know if paraview have some benchmarking tools. Or whats is the best way to do such benchmarks? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Nov 29 14:05:58 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 29 Nov 2016 14:05:58 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: Paraview client crashes while loading data In-Reply-To: References: <7318fd853b194a3cacce5acfd917f8b7@ES01AMSNLNT.srn.sandia.gov> Message-ID: Okay. But in the end the client and server code versions should be the same, particularly in a production environment. I suggest building v5.2.0 as your server and using the v5.2.0 client. We can look into providing more informative messages when this isn't the case. Cory On Tue, Nov 29, 2016 at 1:37 PM, Khayam Gondal wrote: > I think its also an issue with pvserver, version I used was version > 5.2.0-40-g1e720c3. It might be an experimental build. When I downgraded > server version 5.2.0-RC3, it started working fine with Both clients RC3 > 7RC4. However I still reported it here. > https://gitlab.kitware.com/paraview/paraview/issues/17053 > > > > On Mon, Nov 28, 2016 at 1:31 PM, Scott, W Alan wrote: >> >> This has given me issues in the past also. We need to have better >> reporting if possible. I wrote it up here: >> >> >> >> https://gitlab.kitware.com/paraview/paraview/issues/17052 >> >> >> >> Alan >> >> >> >> From: Paraview-developers >> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Mathieu >> Westphal >> Sent: Monday, November 28, 2016 12:57 AM >> To: Khayam Gondal >> Cc: ParaView Developers >> Subject: [EXTERNAL] Re: [Paraview-developers] Paraview client crashes >> while loading data >> >> >> >> Couldn't we add a version check during client connection ? >> >> >> >> On 27 Nov 2016 11:02 pm, "Khayam Gondal" wrote: >> >> That indeed was the problem. Client was 5.2.0 RC3 whereas server was RC4. >> I downgraded server to RC3 and its working fine now. Thanks >> >> >> >> On Sun, Nov 27, 2016 at 4:37 PM, Cory Quammen >> wrote: >> >> Sounds like a mismatch between the code from which the client and >> server were built. You need to compile the server code with the same >> code with which the client was built. If your binary is version 5.2.0, >> then on the server side make sure you are using the 5.2.0 source code, >> either downloaded from [1] or check out the v5.2.0 tag in the git >> repository. If you are building from the git repository, make sure you >> run 'git submodule update' after checking out the v5.2.0 tag and >> before you compile - that is a common source of problems with >> client/server communication. >> >> HTH, >> Cory >> >> [1] http://www.paraview.org/download/ >> >> >> On Sun, Nov 27, 2016 at 4:25 PM, Khayam Gondal >> wrote: >> > I built the server. Its on ubuntu with 2K40 GPUs. Client is pre build >> > binary >> > on windows7. >> > Can you tell me how can i start client with debugger? >> > Actually everything i was working fine until I recently rebuild the >> > server >> > and this problem popped up. >> > >> > >> > On Nov 27, 2016 16:06, "Cory Quammen" wrote: >> >> >> >> Did you build ParaView or are you using a binary release? >> >> >> >> Could you run the client through a debugger and provide a stack trace >> >> where it crashes? That would help get an idea of what might be going >> >> on. >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Sun, Nov 27, 2016 at 10:30 AM, Khayam Gondal >> >> >> >> wrote: >> >> > Hi, >> >> > I have paraview in server-client mode installed. Client is >> >> > successfully >> >> > connected to server. But when I try to load data into paraview from >> >> > GUI, >> >> > it >> >> > crashes and on server side shows following errors. >> >> > >> >> > Client connected. >> >> > ERROR: In /ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line >> >> > 809 >> >> > vtkSocketCommunicator (0x1f634f0): Could not receive tag. 1 >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >> >> > pipe. >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > vtkClientSocket (0x1f95d50): Socket error in call to send. Broken >> >> > pipe. >> >> > >> >> > ERROR: In /ParaView/VTK/Common/System/vtkSocket.cxx, line 572 >> >> > >> >> > However same data files work fine on my local system. Any idea whats >> >> > wrong >> >> > here? >> >> > >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Search the list archives at: >> >> > http://markmail.org/search/?q=Paraview-developers >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> Staff R&D Engineer >> >> Kitware, Inc. >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: >> http://markmail.org/search/?q=Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Search the list archives at: > http://markmail.org/search/?q=Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > -- Cory Quammen Staff R&D Engineer Kitware, Inc. From gualambo at gmail.com Tue Nov 29 15:06:10 2016 From: gualambo at gmail.com (Franz Wilder) Date: Tue, 29 Nov 2016 15:06:10 -0500 Subject: [Paraview-developers] Elmer in Paraview Message-ID: Hi, my name is Franz. I would like to know if there is any way to get the surface number of the solid, just like the Elmer software does. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Nov 29 15:32:46 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 29 Nov 2016 20:32:46 +0000 Subject: [Paraview-developers] [EXTERNAL] Benchmarking Paraview In-Reply-To: References: Message-ID: <54e8216ad37a46388eb49348e08c2ef9@ES01AMSNLNT.srn.sandia.gov> Only benchmarking tool I can think of is the Timer Log within ParaView. Tools/ Timer Log. Alan From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Khayam Gondal Sent: Tuesday, November 29, 2016 12:00 PM To: ParaView Developers List Subject: [EXTERNAL] [Paraview-developers] Benchmarking Paraview I have to benchmark paraview performance with different configurations such as with single vs multi GPU, with or without MPI support. I want to get results like GPU render time. Parallel IO timings. Server-Client communication latency. But i am kind of stuck here. I don't know if paraview have some benchmarking tools. Or whats is the best way to do such benchmarks? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Nov 29 15:36:12 2016 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 29 Nov 2016 15:36:12 -0500 Subject: [Paraview-developers] [EXTERNAL] Benchmarking Paraview In-Reply-To: <54e8216ad37a46388eb49348e08c2ef9@ES01AMSNLNT.srn.sandia.gov> References: <54e8216ad37a46388eb49348e08c2ef9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Here is an email from Chuck from a while back, it might be useful You should be able to run the many spheres benchmark script that ships with ParaView. You can run it with pvbatch: [chuck at hal9000]$ pvbatch ${ParaView_DIR}/lib/paraview-5 .1/site-packages/paraview/benchmark/manyspheres.py --help usage: manyspheres.py [-h] [-o OUTPUT_BASENAME] [-s SPHERES] [-n SPHERES_IN_SCENE] [-r RESOLUTION] [-v VIEW_SIZE] [-f FRAMES] [-c] [-y] Benchmark ParaView geometry rendering optional arguments: -h, --help show this help message and exit -o OUTPUT_BASENAME, --output-basename OUTPUT_BASENAME Basename to use for generated output files -s SPHERES, --spheres SPHERES The total number of spheres to render -n SPHERES_IN_SCENE, --spheres-in-scene SPHERES_IN_SCENE The number of spheres in the entire scene, including those not rendered. -r RESOLUTION, --resolution RESOLUTION Theta and Phi resolution to use for the spheres -v VIEW_SIZE, --view-size VIEW_SIZE View size used to render -f FRAMES, --frames FRAMES Number of frames -c, --color Enable color renderings -y, --OSPRay Use OSPRAY to render The benchmark will generate several spheres in the shape of a cube and sp[in the camera around them. When running in parallel, each rank will be processing a subset of the spheres. A good value to use for "resolution" is 726 since that gives you ~ 1M triangles per sphere. When benching the performance of a system, I generally find it easiest to keep the resolution filed while varying the number of spheres. For example, say you wanted to do a test run of 2048 spheres across 128 ranks (each rank renders 16 spheres) with ~ 1M triangles per sphere in a 1920x1080 view for 100 frames. You would use: mpirun -n 128 pvbatch ${ParaView_DIR}/lib/paraview-5 .1/site-packages/paraview/benchmark/manyspheres.py -s 2048 -r 726 -v 1920,1080 -f 100 This will output per-frame statistics across ranks as well as a final summary of: Frames / Sec, Points / Frame, Polys / Frame, and MiPolys / Sec. On Tue, Nov 29, 2016 at 3:32 PM, Scott, W Alan wrote: > Only benchmarking tool I can think of is the Timer Log within ParaView. > Tools/ Timer Log. > > > > Alan > > > > *From:* Paraview-developers [mailto:paraview-developers- > bounces at paraview.org] *On Behalf Of *Khayam Gondal > *Sent:* Tuesday, November 29, 2016 12:00 PM > *To:* ParaView Developers List > *Subject:* [EXTERNAL] [Paraview-developers] Benchmarking Paraview > > > > I have to benchmark paraview performance with different configurations > such as with single vs multi GPU, with or without MPI support. I want to > get results like GPU render time. Parallel IO timings. Server-Client > communication latency. > > > > But i am kind of stuck here. I don't know if paraview have some > benchmarking tools. Or whats is the best way to do such benchmarks? > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Tue Nov 29 15:38:48 2016 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 29 Nov 2016 15:38:48 -0500 Subject: [Paraview-developers] [EXTERNAL] Benchmarking Paraview In-Reply-To: References: <54e8216ad37a46388eb49348e08c2ef9@ES01AMSNLNT.srn.sandia.gov> Message-ID: Failed to reply all earlier. Sorry Khayam since this is the third time you see this: Look at the paraview.benchmarks module from python. What Ken referred to is part of it. The module itself has everything you need to record and analyze the time taken by everything within arbitrary pipelines and runs of ParaView. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Nov 29, 2016 at 3:36 PM, Ken Martin wrote: > Here is an email from Chuck from a while back, it might be useful > > You should be able to run the many spheres benchmark script that ships > with ParaView. You can run it with pvbatch: > > [chuck at hal9000]$ pvbatch ${ParaView_DIR}/lib/paraview-5 > .1/site-packages/paraview/benchmark/manyspheres.py --help > usage: manyspheres.py [-h] [-o OUTPUT_BASENAME] [-s SPHERES] > [-n SPHERES_IN_SCENE] [-r RESOLUTION] [-v VIEW_SIZE] > [-f FRAMES] [-c] [-y] > > Benchmark ParaView geometry rendering > > optional arguments: > -h, --help show this help message and exit > -o OUTPUT_BASENAME, --output-basename OUTPUT_BASENAME > Basename to use for generated output files > -s SPHERES, --spheres SPHERES > The total number of spheres to render > -n SPHERES_IN_SCENE, --spheres-in-scene SPHERES_IN_SCENE > The number of spheres in the entire scene, > including > those not rendered. > -r RESOLUTION, --resolution RESOLUTION > Theta and Phi resolution to use for the spheres > -v VIEW_SIZE, --view-size VIEW_SIZE > View size used to render > -f FRAMES, --frames FRAMES > Number of frames > -c, --color Enable color renderings > -y, --OSPRay Use OSPRAY to render > > > The benchmark will generate several spheres in the shape of a cube and > sp[in the camera around them. When running in parallel, each rank will be > processing a subset of the spheres. A good value to use for "resolution" > is 726 since that gives you ~ 1M triangles per sphere. When benching > the performance of a system, I generally find it easiest to keep the > resolution filed while varying the number of spheres. > > For example, say you wanted to do a test run of 2048 spheres across 128 > ranks (each rank renders 16 spheres) with ~ 1M triangles per sphere in a > 1920x1080 view for 100 frames. You would use: > > mpirun -n 128 pvbatch ${ParaView_DIR}/lib/paraview-5 > .1/site-packages/paraview/benchmark/manyspheres.py -s 2048 -r 726 -v > 1920,1080 -f 100 > > This will output per-frame statistics across ranks as well as a final > summary of: Frames / Sec, Points / Frame, Polys / Frame, and MiPolys / > Sec. > > On Tue, Nov 29, 2016 at 3:32 PM, Scott, W Alan wrote: > >> Only benchmarking tool I can think of is the Timer Log within ParaView. >> Tools/ Timer Log. >> >> >> >> Alan >> >> >> >> *From:* Paraview-developers [mailto:paraview-developers-bo >> unces at paraview.org] *On Behalf Of *Khayam Gondal >> *Sent:* Tuesday, November 29, 2016 12:00 PM >> *To:* ParaView Developers List >> *Subject:* [EXTERNAL] [Paraview-developers] Benchmarking Paraview >> >> >> >> I have to benchmark paraview performance with different configurations >> such as with single vs multi GPU, with or without MPI support. I want to >> get results like GPU render time. Parallel IO timings. Server-Client >> communication latency. >> >> >> >> But i am kind of stuck here. I don't know if paraview have some >> benchmarking tools. Or whats is the best way to do such benchmarks? >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Search the list archives at: http://markmail.org/search/?q= >> Paraview-developers >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > > > -- > Ken Martin PhD > Chairman & CFO > Kitware Inc. > 28 Corporate Drive > Clifton Park NY 12065 > 518 371 3971 > > This communication, including all attachments, contains confidential and > legally privileged information, and it is intended only for the use of the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any disclosure, copying, distribution or any > action taken in reliance on it is prohibited and may be unlawful. If you > received this communication in error please notify us immediately and > destroy the original message. Thank you. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Nov 29 15:39:19 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 29 Nov 2016 20:39:19 +0000 Subject: [Paraview-developers] osmesa version of ParaView Message-ID: <5411832422714b7193b3dc3b47eacb40@ES01AMSNLNT.srn.sandia.gov> Cory/ Utkarsh/ Guys, I think we need to be able to build an osmesa version of ParaView, and we need this rendering option as a command line option for all Kitware Linux downloads. The reason is that the next version of Redhat - RHEL 7 will no longer allow the forwarding of GLX contexts. Thus, to be able to X forward ParaView back to a local computer, we will need to render into only an X window. This is already giving us issues at Sandia with new Linux installs. Is this possible? How hard will it be? Any ideas on schedule? Before I write this up as a bug, I figured I would see what type of discussion we get in this thread. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.martin at kitware.com Tue Nov 29 16:31:45 2016 From: ken.martin at kitware.com (Ken Martin) Date: Tue, 29 Nov 2016 16:31:45 -0500 Subject: [Paraview-developers] osmesa version of ParaView In-Reply-To: <5411832422714b7193b3dc3b47eacb40@ES01AMSNLNT.srn.sandia.gov> References: <5411832422714b7193b3dc3b47eacb40@ES01AMSNLNT.srn.sandia.gov> Message-ID: Couple quick thoughts If we can connect to the remote display using GLX (but not forwarded) then we can render remotely (offscreen but using normal OpenGL) and then copy the result to an Xwindow which is forwarded to a local machine. Sort of a RenderingDisplay=:0.0 Display=:1.0 where 1.0 is the forwarded one. I recall there being an issue with osmesa and accelerated opengl in the same binary but I have very limited experience with it. On Tue, Nov 29, 2016 at 3:39 PM, Scott, W Alan wrote: > Cory/ Utkarsh/ Guys, > > I think we need to be able to build an osmesa version of ParaView, and we > need this rendering option as a command line option for all Kitware Linux > downloads. The reason is that the next version of Redhat ? RHEL 7 will no > longer allow the forwarding of GLX contexts. Thus, to be able to X forward > ParaView back to a local computer, we will need to render into only an X > window. This is already giving us issues at Sandia with new Linux installs. > > > > Is this possible? How hard will it be? Any ideas on schedule? > > > > Before I write this up as a bug, I figured I would see what type of > discussion we get in this thread. > > > > Thanks, > > > > Alan > > > > -------------------------------------------------------- > > W. Alan Scott > > ParaView Support Manager > > > > SAIC > > Sandia National Laboratories, MS 0822 > > Org 9326 - Building 880 A1-K > > (505) 284-0932 FAX (505) 284-5619 > > --------------------------------------------------------- > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sur.chiranjib at gmail.com Wed Nov 30 02:56:22 2016 From: sur.chiranjib at gmail.com (Chiranjib Sur) Date: Wed, 30 Nov 2016 13:26:22 +0530 Subject: [Paraview-developers] paraview 5.2 runtime error with 'fontconfig" Message-ID: Hi, With my ParaView5.2 build (via superbuild), I get a run time error followed by a seg fault. Any clue what went missing during my build procedure? Here are the runtime log and the CMakeCache.txt files attached. My system configuration is : RHEL6, c++11 GNU compiler, python 2.7+, CMake 3.7, Qt4.8 Thanks, Chiranjib -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- # This is the CMakeCache file. # For build in directory: /glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build # It was generated by CMake: /glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/cmake # You can edit this file to change values found and used by cmake. # If you do not want to change any of the values, simply exit the editor. # If you do want to change a value, simply edit, save, and exit the editor. # The syntax for the file is as follows: # KEY:TYPE=VALUE # KEY is the name of a variable in the cache. # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. # VALUE is the current value for the KEY. ######################## # EXTERNAL cache entries ######################## //Enable shared libraries BUILD_SHARED_LIBS:BOOL=ON //Build testing BUILD_TESTING:BOOL=OFF //Path to a program. BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND //Path to a program. CMAKE_AR:FILEPATH=/usr/bin/ar //The build mode CMAKE_BUILD_TYPE:STRING=Release //The build type for the paraview project. CMAKE_BUILD_TYPE_paraview:STRING= //Enable/Disable color output during build. CMAKE_COLOR_MAKEFILE:BOOL=ON //CXX compiler CMAKE_CXX_COMPILER:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/GCC/4.9.2/bin/g++ //Flags used by the compiler during all build types. CMAKE_CXX_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_CXX_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //C compiler CMAKE_C_COMPILER:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/GCC/4.9.2/bin/gcc //Flags used by the compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the compiler during debug builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the compiler during release builds for minimum // size. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the compiler during release builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the compiler during release builds with debug info. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG //Flags used by the linker. CMAKE_EXE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Enable/Disable output of compile commands during generation. CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF //Install path prefix, prepended onto install directories. CMAKE_INSTALL_PREFIX:PATH=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build/install //Path to a program. CMAKE_LINKER:FILEPATH=/usr/bin/ld //Path to a program. CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake //Flags used by the linker during the creation of modules. CMAKE_MODULE_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_NM:FILEPATH=/usr/bin/nm //Path to a program. CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy //Path to a program. CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump //Value Computed by CMake CMAKE_PROJECT_NAME:STATIC=paraview-superbuild //Path to a program. CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib //Flags used by the linker during the creation of dll's. CMAKE_SHARED_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING= //If set, runtime paths are not added when installing shared libraries, // but are added when building. CMAKE_SKIP_INSTALL_RPATH:BOOL=NO //If set, runtime paths are not added when using shared libraries. CMAKE_SKIP_RPATH:BOOL=NO //Flags used by the linker during the creation of static libraries. CMAKE_STATIC_LINKER_FLAGS:STRING= //Flags used by the linker during debug builds. CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING= //Flags used by the linker during release minsize builds. CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING= //Flags used by the linker during release builds. CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING= //Flags used by the linker during Release with Debug Info builds. CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING= //Path to a program. CMAKE_STRIP:FILEPATH=/usr/bin/strip //If this value is on, makefiles will be generated without the // .SILENT directive, and all commands will be echoed to the console // during the make. This is useful for debugging only. With Visual // Studio IDE projects all commands are done without /nologo. CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE //Path to the coverage program that CTest uses for performing coverage // inspection COVERAGE_COMMAND:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/GCC/4.9.2/bin/gcov //Extra command line flags to pass to the coverage tool COVERAGE_EXTRA_FLAGS:STRING=-l //How many times to retry timed-out CTest submissions. CTEST_SUBMIT_RETRY_COUNT:STRING=3 //How long to wait between timed-out CTest submissions. CTEST_SUBMIT_RETRY_DELAY:STRING=5 //Path to a program. CVSCOMMAND:FILEPATH=/usr/bin/cvs //Options passed to the cvs update command. CVS_UPDATE_OPTIONS:STRING=-d -A -P //Maximum time allowed before CTest will kill the test. DART_TESTING_TIMEOUT:STRING=1500 //Request to build project adios ENABLE_adios:BOOL=OFF //Request to build project boost ENABLE_boost:BOOL=OFF //Request to build project catalyst ENABLE_catalyst:BOOL=OFF //Request to build project cgns ENABLE_cgns:BOOL=OFF //Request to build project cosmotools ENABLE_cosmotools:BOOL=OFF //Request to build project cxx11 ENABLE_cxx11:BOOL=OFF //Request to build project egl ENABLE_egl:BOOL=OFF //Request to build project ffmpeg ENABLE_ffmpeg:BOOL=OFF //Request to build project fontconfig ENABLE_fontconfig:BOOL=ON //Request to build project freetype ENABLE_freetype:BOOL=ON //Request to build project genericio ENABLE_genericio:BOOL=OFF //Request to build project glu ENABLE_glu:BOOL=OFF //Request to build project hdf5 ENABLE_hdf5:BOOL=OFF //Request to build project ispc ENABLE_ispc:BOOL=OFF //Request to build project llvm ENABLE_llvm:BOOL=OFF //Request to build project matplotlib ENABLE_matplotlib:BOOL=OFF //Request to build project mesa ENABLE_mesa:BOOL=OFF //Request to build project mpi ENABLE_mpi:BOOL=ON //Request to build project mxml ENABLE_mxml:BOOL=OFF //Request to build project netcdf ENABLE_netcdf:BOOL=OFF //Request to build project numpy ENABLE_numpy:BOOL=OFF //Request to build project osmesa ENABLE_osmesa:BOOL=OFF //Request to build project ospray ENABLE_ospray:BOOL=OFF //Request to build project paraview ENABLE_paraview:BOOL=ON //Request to build project paraviewgettingstartedguide ENABLE_paraviewgettingstartedguide:BOOL=OFF //Request to build project paraviewsdk ENABLE_paraviewsdk:BOOL=ON //Request to build project paraviewtutorial ENABLE_paraviewtutorial:BOOL=OFF //Request to build project paraviewtutorialdata ENABLE_paraviewtutorialdata:BOOL=OFF //Request to build project paraviewusersguide ENABLE_paraviewusersguide:BOOL=OFF //Request to build project paraviewweb ENABLE_paraviewweb:BOOL=OFF //Request to build project paraviewweblightviz ENABLE_paraviewweblightviz:BOOL=OFF //Request to build project paraviewwebvisualizer ENABLE_paraviewwebvisualizer:BOOL=OFF //Request to build project python ENABLE_python:BOOL=ON //Request to build project pythonsetuptools ENABLE_pythonsetuptools:BOOL=ON //Request to build project qt4 ENABLE_qt4:BOOL=ON //Request to build project qt5 ENABLE_qt5:BOOL=OFF //Request to build project silo ENABLE_silo:BOOL=OFF //Request to build project socat ENABLE_socat:BOOL=OFF //Request to build project szip ENABLE_szip:BOOL=OFF //Request to build project tbb ENABLE_tbb:BOOL=OFF //Request to build project visitbridge ENABLE_visitbridge:BOOL=OFF //Request to build project vortexfinder2 ENABLE_vortexfinder2:BOOL=OFF //Request to build project vrpn ENABLE_vrpn:BOOL=OFF //Request to build project xdmf3 ENABLE_xdmf3:BOOL=OFF //Path to a file. FREETYPE_INCLUDE_DIR_freetype2:PATH=/usr/include/freetype2 //Path to a file. FREETYPE_INCLUDE_DIR_ft2build:PATH=/usr/include //Path to a library. FREETYPE_LIBRARY_DEBUG:FILEPATH=FREETYPE_LIBRARY_DEBUG-NOTFOUND //Path to a library. FREETYPE_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libfreetype.so //Path to a program. GITCOMMAND:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/git/2.2.2/bin/git //Git command line client GIT_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/git/2.2.2/bin/git //Path to a program. HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND //Path to a file. LIBXML2_INCLUDE_DIR:PATH=/usr/include/libxml2 //Path to a library. LIBXML2_LIBRARIES:FILEPATH=/usr/lib64/libxml2.so //Path to a program. LIBXML2_XMLLINT_EXECUTABLE:FILEPATH=/usr/bin/xmllint //Command to build the project MAKECOMMAND:STRING=/glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/cmake --build . --config "${CTEST_CONFIGURATION_TYPE}" //Path to the memory checking command, used for memory error detection. MEMORYCHECK_COMMAND:FILEPATH=/usr/bin/valgrind //File that contains suppressions for the memory checker MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH= //Executable for running MPI programs. MPIEXEC:FILEPATH=/apps/3rdparty/hpcrnd/openmpi/1.8.3/RHEL6/gcc_4.4.7/bin/mpiexec //Maximum number of processors available to run MPI applications. MPIEXEC_MAX_NUMPROCS:STRING=2 //Flag used by MPI to specify the number of processes for MPIEXEC; // the next option will be the number of processes. MPIEXEC_NUMPROC_FLAG:STRING=-np //These flags will come after all flags given to MPIEXEC. MPIEXEC_POSTFLAGS:STRING= //These flags will be directly before the executable that is being // run by MPIEXEC. MPIEXEC_PREFLAGS:STRING= //Path to a program. MPI_CXX_COMPILER:FILEPATH=/apps/3rdparty/hpcrnd/openmpi/1.8.3/RHEL6/gcc_4.4.7/bin/mpicxx //MPI CXX compilation flags MPI_CXX_COMPILE_FLAGS:STRING= //MPI CXX include path MPI_CXX_INCLUDE_PATH:STRING=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/include //MPI CXX libraries to link against MPI_CXX_LIBRARIES:STRING=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi_cxx.so;/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi.so //MPI CXX linking flags MPI_CXX_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib -Wl,--enable-new-dtags //Path to a program. MPI_C_COMPILER:FILEPATH=/apps/3rdparty/hpcrnd/openmpi/1.8.3/RHEL6/gcc_4.4.7/bin/mpicc //MPI C compilation flags MPI_C_COMPILE_FLAGS:STRING= //MPI C include path MPI_C_INCLUDE_PATH:STRING=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/include //MPI C libraries to link against MPI_C_LIBRARIES:STRING=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi.so //MPI C linking flags MPI_C_LINK_FLAGS:STRING= -Wl,-rpath -Wl,/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib -Wl,--enable-new-dtags //Extra MPI libraries to link against MPI_EXTRA_LIBRARY:STRING=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi.so //MPI library to link against MPI_LIBRARY:FILEPATH=/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi_cxx.so //Path to a program. P4COMMAND:FILEPATH=P4COMMAND-NOTFOUND //If set, overrides the generated filename for the package PARAVIEWSDK_PACKAGE_FILE_NAME:STRING= //ParaView's build mode PARAVIEW_BUILD_TYPE:STRING= //Build documentation for the web PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF //The catalyst edition to build PARAVIEW_CATALYST_EDITION:STRING=Essentials //Enable Python support in catalyst PARAVIEW_CATALYST_PYTHON:BOOL=ON //Default to using the system OpenGL PARAVIEW_DEFAULT_SYSTEM_GL:BOOL=OFF //A list of projects for ParaView to depend on PARAVIEW_EXTERNAL_PROJECTS:STRING= //Extra arguments to be passed to ParaView when configuring. PARAVIEW_EXTRA_CMAKE_ARGUMENTS:STRING= //Freeze Python packages and modules into the application PARAVIEW_FREEZE_PYTHON:BOOL=OFF //If set, overrides the generated filename for the package PARAVIEW_PACKAGE_FILE_NAME:STRING= //String to use as a suffix for generated packages PARAVIEW_PACKAGE_SUFFIX:STRING= //Rendering backend to use for ParaView PARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 //The default version of ParaView to use if it can't be auto-determined PARAVIEW_VERSION_DEFAULT:STRING=5.2.0 PARAVIEW_WEB_TEST_REMOTE:BOOL=OFF //Pass LD_LIBRARY_PATH to build scripts PASS_LD_LIBRARY_PATH_FOR_BUILDS:BOOL=ON //pkg-config executable PKG_CONFIG_EXECUTABLE:FILEPATH=/usr/bin/pkg-config //Path to a library. PYTHON_LIBRARY:FILEPATH=PYTHON_LIBRARY-NOTFOUND //Path to a library. PYTHON_LIBRARY_DEBUG:FILEPATH=PYTHON_LIBRARY_DEBUG-NOTFOUND //Path to a library. PYTHON_LIBRARY_RELEASE:FILEPATH=PYTHON_LIBRARY_RELEASE-NOTFOUND //Path to a program. ProcessorCount_cmd_getconf:FILEPATH=/usr/bin/getconf //Path to a program. ProcessorCount_cmd_sysctl:FILEPATH=/sbin/sysctl //Path to a library. QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libarthurplugin.so //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=QT_CONTAINEREXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libcontainerextension.so //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libcustomwidgetplugin.so //Path to a program. QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qdbuscpp2xml //Path to a program. QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qdbusxml2cpp //Path to a program. QT_DESIGNER_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/designer //The location of the Qt docs QT_DOC_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/doc //The location of the Qt imports QT_IMPORTS_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/imports //Path to a program. QT_LINGUIST_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/linguist //Path to a program. QT_LRELEASE_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/lrelease //Path to a program. QT_LUPDATE_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/lupdate //The location of the Qt mkspecs containing qconfig.pri QT_MKSPECS_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/mkspecs //Path to a program. QT_MOC_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/moc //Path to a library. QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=QT_PHONONWIDGETS_PLUGIN_RELEASE-NOTFOUND //Path to a file. QT_PHONON_INCLUDE_DIR:PATH=QT_PHONON_INCLUDE_DIR-NOTFOUND //The Qt PHONON library QT_PHONON_LIBRARY:STRING= //Path to a library. QT_PHONON_LIBRARY_DEBUG:FILEPATH=QT_PHONON_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_PHONON_LIBRARY_RELEASE:FILEPATH=QT_PHONON_LIBRARY_RELEASE-NOTFOUND //The location of the Qt plugins QT_PLUGINS_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins //Path to a library. QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=QT_QCNCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/codecs/libqcncodecs.so //Path to a program. QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qcollectiongenerator //Path to a library. QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libqdeclarativeview.so //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=QT_QGENERICBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/bearer/libqgenericbearer.so //Path to a library. QT_QGIF_PLUGIN_DEBUG:FILEPATH=QT_QGIF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGIF_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqgif.so //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/graphicssystems/libqglgraphicssystem.so //Path to a library. QT_QICO_PLUGIN_DEBUG:FILEPATH=QT_QICO_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QICO_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqico.so //Path to a library. QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=QT_QJPCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/codecs/libqjpcodecs.so //Path to a library. QT_QJPEG_PLUGIN_DEBUG:FILEPATH=QT_QJPEG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QJPEG_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqjpeg.so //Path to a library. QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=QT_QKRCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/codecs/libqkrcodecs.so //Where can the qmake-qt4 library be found QT_QMAKE_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qmake //Path to a library. QT_QMNG_PLUGIN_DEBUG:FILEPATH=QT_QMNG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QMNG_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqmng.so //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE:FILEPATH=QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/sqldrivers/libqsqlite.so //Path to a library. QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/sqldrivers/libqsqlmysql.so //Path to a library. QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=QT_QSQLODBC_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=QT_QSQLODBC_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLPSQL_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/sqldrivers/libqsqlpsql.so //Path to a library. QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=QT_QSVGICON_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/iconengines/libqsvgicon.so //Path to a library. QT_QSVG_PLUGIN_DEBUG:FILEPATH=QT_QSVG_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QSVG_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqsvg.so //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libqt3supportwidgets.so //Path to a file. QT_QT3SUPPORT_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/Qt3Support //The Qt QT3SUPPORT library QT_QT3SUPPORT_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQt3Support.so //Path to a library. QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=QT_QT3SUPPORT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQt3Support.so //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/accessible/libqtaccessiblecompatwidgets.so //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/accessible/libqtaccessiblewidgets.so //Path to a file. QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANTCLIENT library QT_QTASSISTANTCLIENT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND //The Qt QTASSISTANT library QT_QTASSISTANT_LIBRARY:STRING= //Path to a library. QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND //The Qt QTCLUCENE library QT_QTCLUCENE_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtCLucene.so //Path to a library. QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=QT_QTCLUCENE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtCLucene.so //Path to a file. QT_QTCORE_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtCore //The Qt QTCORE library QT_QTCORE_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtCore.so //Path to a library. QT_QTCORE_LIBRARY_DEBUG:FILEPATH=QT_QTCORE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTCORE_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtCore.so //Path to a file. QT_QTDBUS_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtDBus //The Qt QTDBUS library QT_QTDBUS_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDBus.so //Path to a library. QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDBus.so //Path to a file. QT_QTDECLARATIVE_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtDeclarative //The Qt QTDECLARATIVE library QT_QTDECLARATIVE_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDeclarative.so //Path to a library. QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=QT_QTDECLARATIVE_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDeclarative.so //Path to a file. QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtDesigner //The Qt QTDESIGNERCOMPONENTS library QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDesignerComponents.so //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDesignerComponents.so //Path to a file. QT_QTDESIGNER_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtDesigner //The Qt QTDESIGNER library QT_QTDESIGNER_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDesigner.so //Path to a library. QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=QT_QTDESIGNER_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtDesigner.so //Path to a library. QT_QTGA_PLUGIN_DEBUG:FILEPATH=QT_QTGA_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTGA_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqtga.so //Path to a file. QT_QTGUI_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtGui //The Qt QTGUI library QT_QTGUI_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtGui.so //Path to a library. QT_QTGUI_LIBRARY_DEBUG:FILEPATH=QT_QTGUI_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTGUI_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtGui.so //Path to a file. QT_QTHELP_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtHelp //The Qt QTHELP library QT_QTHELP_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtHelp.so //Path to a library. QT_QTHELP_LIBRARY_DEBUG:FILEPATH=QT_QTHELP_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTHELP_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtHelp.so //Path to a library. QT_QTIFF_PLUGIN_DEBUG:FILEPATH=QT_QTIFF_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTIFF_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/imageformats/libqtiff.so //Path to a file. QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtMultimedia //The Qt QTMULTIMEDIA library QT_QTMULTIMEDIA_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtMultimedia.so //Path to a library. QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=QT_QTMULTIMEDIA_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtMultimedia.so //Path to a file. QT_QTNETWORK_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtNetwork //The Qt QTNETWORK library QT_QTNETWORK_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtNetwork.so //Path to a library. QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=QT_QTNETWORK_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtNetwork.so //Path to a file. QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND //The Qt QTNSPLUGIN library QT_QTNSPLUGIN_LIBRARY:STRING= //Path to a library. QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND //Path to a file. QT_QTOPENGL_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtOpenGL //The Qt QTOPENGL library QT_QTOPENGL_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtOpenGL.so //Path to a library. QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=QT_QTOPENGL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtOpenGL.so //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/graphicssystems/libqtracegraphicssystem.so //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/script/libqtscriptdbus.so //Path to a file. QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtScriptTools //The Qt QTSCRIPTTOOLS library QT_QTSCRIPTTOOLS_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtScriptTools.so //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtScriptTools.so //Path to a file. QT_QTSCRIPT_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtScript //The Qt QTSCRIPT library QT_QTSCRIPT_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtScript.so //Path to a library. QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=QT_QTSCRIPT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtScript.so //Path to a file. QT_QTSQL_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtSql //The Qt QTSQL library QT_QTSQL_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtSql.so //Path to a library. QT_QTSQL_LIBRARY_DEBUG:FILEPATH=QT_QTSQL_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSQL_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtSql.so //Path to a file. QT_QTSVG_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtSvg //The Qt QTSVG library QT_QTSVG_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtSvg.so //Path to a library. QT_QTSVG_LIBRARY_DEBUG:FILEPATH=QT_QTSVG_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTSVG_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtSvg.so //Path to a file. QT_QTTEST_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtTest //The Qt QTTEST library QT_QTTEST_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtTest.so //Path to a library. QT_QTTEST_LIBRARY_DEBUG:FILEPATH=QT_QTTEST_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTTEST_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtTest.so //Path to a file. QT_QTUITOOLS_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtUiTools //The Qt QTUITOOLS library QT_QTUITOOLS_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtUiTools.a //Path to a library. QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=QT_QTUITOOLS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtUiTools.a //Path to a library. QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=QT_QTWCODECS_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/codecs/libqtwcodecs.so //Path to a file. QT_QTWEBKIT_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtWebKit //The Qt QTWEBKIT library QT_QTWEBKIT_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtWebKit.so //Path to a library. QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=QT_QTWEBKIT_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtWebKit.so //Path to a file. QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtXmlPatterns //The Qt QTXMLPATTERNS library QT_QTXMLPATTERNS_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtXmlPatterns.so //Path to a library. QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=QT_QTXMLPATTERNS_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtXmlPatterns.so //Path to a file. QT_QTXML_INCLUDE_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include/QtXml //The Qt QTXML library QT_QTXML_LIBRARY:STRING=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtXml.so //Path to a library. QT_QTXML_LIBRARY_DEBUG:FILEPATH=QT_QTXML_LIBRARY_DEBUG-NOTFOUND //Path to a library. QT_QTXML_LIBRARY_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtXml.so //Path to a library. QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libqwebview.so //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND //Path to a program. QT_RCC_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/rcc //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=QT_TASKMENUEXTENSION_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libtaskmenuextension.so //The location of the Qt translations QT_TRANSLATIONS_DIR:PATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/translations //Path to a program. QT_UIC3_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/uic3 //Path to a program. QT_UIC_EXECUTABLE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/uic //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND //Path to a library. QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/plugins/designer/libworldtimeclockplugin.so //Path to scp command, used by CTest for submitting results to // a Dart server SCPCOMMAND:FILEPATH=/usr/bin/scp //Path to a program. SED_EXECUTABLE:FILEPATH=/bin/sed //Name of the computer/site where compile is being run SITE:STRING=bngsti-n-b00810 //Path to the SLURM sbatch executable SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND //Path to the SLURM srun executable SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND //The package to install by default SUPERBUILD_DEFAULT_INSTALL:STRING=paraview/TGZ //Do not update git repositories during the build SUPERBUILD_OFFLINE_BUILD:BOOL=OFF //Number of jobs to use when compiling subprojects SUPERBUILD_PROJECT_PARALLELISM:STRING=12 //Suppress output for bzip2 SUPPRESS_bzip2_OUTPUT:BOOL=OFF //Suppress output for fontconfig SUPPRESS_fontconfig_OUTPUT:BOOL=OFF //Suppress output for freetype SUPPRESS_freetype_OUTPUT:BOOL=OFF //Suppress output for libxml2 SUPPRESS_libxml2_OUTPUT:BOOL=OFF //Suppress output for mpi SUPPRESS_mpi_OUTPUT:BOOL=OFF //Suppress output for paraview SUPPRESS_paraview_OUTPUT:BOOL=OFF //Suppress output for png SUPPRESS_png_OUTPUT:BOOL=OFF //Suppress output for python SUPPRESS_python_OUTPUT:BOOL=OFF //Suppress output for pythonsetuptools SUPPRESS_pythonsetuptools_OUTPUT:BOOL=OFF //Suppress output for qt4 SUPPRESS_qt4_OUTPUT:BOOL=OFF //Suppress output for zlib SUPPRESS_zlib_OUTPUT:BOOL=OFF //Path to a program. SVNCOMMAND:FILEPATH=/usr/bin/svn //Enable the non-free parts of the superbuild USE_NONFREE_COMPONENTS:BOOL=OFF USE_SYSTEM_bzip2:BOOL=OFF USE_SYSTEM_freetype:BOOL=ON USE_SYSTEM_libxml2:BOOL=ON USE_SYSTEM_mpi:BOOL=ON USE_SYSTEM_png:BOOL=OFF USE_SYSTEM_python:BOOL=OFF USE_SYSTEM_qt4:BOOL=ON USE_SYSTEM_zlib:BOOL=OFF //The source selection for mesa mesa_SOURCE_SELECTION:STRING=13.0.0 //Enable the OpenSWR driver mesa_USE_SWR:BOOL=ON //Enable floating point textures via ARB_texture_float. mesa_USE_TEXTURE_FLOAT:BOOL=OFF //Target ISA for OSPRay (SSE, AVX, AVX2, AVX512, or ALL). ospray_BUILD_ISA:STRING=ALL //Value Computed by CMake paraview-superbuild_BINARY_DIR:STATIC=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build //Value Computed by CMake paraview-superbuild_SOURCE_DIR:STATIC=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/src //The source selection for paraview paraview_SOURCE_SELECTION:STRING=5.2.0 //Build Qt with OpenSSL support qt4_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt4 when configuring. qt4_EXTRA_CONFIGURATION_OPTIONS:STRING= //Work around a build issue in Qt. Use this if you see linker errors // with QtHelp and QCLucene. qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD:BOOL=OFF //Build with OpenSSL support. Requires system-installed OpenSSL // at runtime. qt5_ENABLE_OPENSSL:BOOL=OFF //Extra arguments to be passed to Qt when configuring. qt5_EXTRA_CONFIGURATION_OPTIONS:STRING= //Location for downloaded source tarballs superbuild_download_location:PATH=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build/downloads ######################## # INTERNAL cache entries ######################## //MODIFIED property for variable: BUILD_TESTING BUILD_TESTING-MODIFIED:INTERNAL=ON //ADVANCED property for variable: BZRCOMMAND BZRCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_AR CMAKE_AR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-ADVANCED:INTERNAL=1 //MODIFIED property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-MODIFIED:INTERNAL=ON //STRINGS property for variable: CMAKE_BUILD_TYPE CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Release;RelWithDebInfo;Debug //STRINGS property for variable: CMAKE_BUILD_TYPE_paraview CMAKE_BUILD_TYPE_paraview-STRINGS:INTERNAL=;Release;RelWithDebInfo;Debug //This is the directory where this CMakeCache.txt was created CMAKE_CACHEFILE_DIR:INTERNAL=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build //Major version of cmake used to create the current loaded cache CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3 //Minor version of cmake used to create the current loaded cache CMAKE_CACHE_MINOR_VERSION:INTERNAL=7 //Patch version of cmake used to create the current loaded cache CMAKE_CACHE_PATCH_VERSION:INTERNAL=0 //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1 //Path to CMake executable. CMAKE_COMMAND:INTERNAL=/glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/cmake //Path to cpack program executable. CMAKE_CPACK_COMMAND:INTERNAL=/glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/cpack //Path to ctest program executable. CMAKE_CTEST_COMMAND:INTERNAL=/glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/ctest //ADVANCED property for variable: CMAKE_CXX_COMPILER CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_COMPILER CMAKE_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS CMAKE_C_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //Path to cache edit program executable. CMAKE_EDIT_COMMAND:INTERNAL=/glb/ap/bngsti/proj/ir5/incsu0/Utils/cmake-3.7.0/build/bin/ccmake //Executable file format CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1 //Name of external makefile project generator. CMAKE_EXTRA_GENERATOR:INTERNAL= //Name of generator. CMAKE_GENERATOR:INTERNAL=Unix Makefiles //Name of generator platform. CMAKE_GENERATOR_PLATFORM:INTERNAL= //Name of generator toolset. CMAKE_GENERATOR_TOOLSET:INTERNAL= //Source directory with the top level CMakeLists.txt file for this // project CMAKE_HOME_DIRECTORY:INTERNAL=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/src //MODIFIED property for variable: CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX-MODIFIED:INTERNAL=ON //Install .so files without execute permission. CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0 //ADVANCED property for variable: CMAKE_LINKER CMAKE_LINKER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MAKE_PROGRAM CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_NM CMAKE_NM-ADVANCED:INTERNAL=1 //number of local generators CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=2 //ADVANCED property for variable: CMAKE_OBJCOPY CMAKE_OBJCOPY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_OBJDUMP CMAKE_OBJDUMP-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_RANLIB CMAKE_RANLIB-ADVANCED:INTERNAL=1 //Path to CMake installation. CMAKE_ROOT:INTERNAL=/glb/home/incsu0/ir5/Utils/cmake-3.7.0 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_SKIP_RPATH CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CMAKE_STRIP CMAKE_STRIP-ADVANCED:INTERNAL=1 //uname command CMAKE_UNAME:INTERNAL=/bin/uname //ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_COMMAND COVERAGE_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: COVERAGE_EXTRA_FLAGS COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVSCOMMAND CVSCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: CVS_UPDATE_OPTIONS CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: DART_TESTING_TIMEOUT DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1 //Request to build project bzip2 ENABLE_bzip2:INTERNAL=OFF //MODIFIED property for variable: ENABLE_fontconfig ENABLE_fontconfig-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_freetype ENABLE_freetype-MODIFIED:INTERNAL=ON //Request to build project libxml2 ENABLE_libxml2:INTERNAL=OFF //MODIFIED property for variable: ENABLE_mpi ENABLE_mpi-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_paraviewsdk ENABLE_paraviewsdk-MODIFIED:INTERNAL=ON //Request to build project png ENABLE_png:INTERNAL=OFF //MODIFIED property for variable: ENABLE_python ENABLE_python-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_pythonsetuptools ENABLE_pythonsetuptools-MODIFIED:INTERNAL=ON //MODIFIED property for variable: ENABLE_qt4 ENABLE_qt4-MODIFIED:INTERNAL=ON //Request to build project zlib ENABLE_zlib:INTERNAL=OFF //Details about finding Freetype FIND_PACKAGE_MESSAGE_DETAILS_Freetype:INTERNAL=[/usr/lib64/libfreetype.so][/usr/include;/usr/include/freetype2][v2.3.11()] //Details about finding Git FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/git/2.2.2/bin/git][v2.2.2()] //Details about finding LibXml2 FIND_PACKAGE_MESSAGE_DETAILS_LibXml2:INTERNAL=[/usr/lib64/libxml2.so][/usr/include/libxml2][v2.7.6()] //Details about finding MPI_C FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi.so][/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/include][v()] //Details about finding MPI_CXX FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi_cxx.so;/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/lib/libmpi.so][/apps/3rdparty/hpc/openmpi/1.8.3/RHEL6/gcc_4.4.7/include][v()] //Details about finding Qt4 FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qmake][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/moc][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/rcc][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/uic][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib][/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib/libQtCore.so][v4.8.6()] //ADVANCED property for variable: FREETYPE_INCLUDE_DIR_freetype2 FREETYPE_INCLUDE_DIR_freetype2-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_INCLUDE_DIR_ft2build FREETYPE_INCLUDE_DIR_ft2build-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_LIBRARY_DEBUG FREETYPE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: FREETYPE_LIBRARY_RELEASE FREETYPE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 //Result of TRY_COMPILE HAVE_void_ptr_size:INTERNAL=TRUE //ADVANCED property for variable: HGCOMMAND HGCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: LIBXML2_INCLUDE_DIR LIBXML2_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: LIBXML2_LIBRARIES LIBXML2_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: LIBXML2_XMLLINT_EXECUTABLE LIBXML2_XMLLINT_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MAKECOMMAND MAKECOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_COMMAND MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC MPIEXEC-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_POSTFLAGS MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPIEXEC_PREFLAGS MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILER MPI_CXX_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_INCLUDE_PATH MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LIBRARIES MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_CXX_LINK_FLAGS MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILER MPI_C_COMPILER-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_COMPILE_FLAGS MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_INCLUDE_PATH MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_LIBRARIES MPI_C_LIBRARIES-ADVANCED:INTERNAL=1 //ADVANCED property for variable: MPI_C_LINK_FLAGS MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1 //Scratch variable for MPI header detection MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND //Scratch variable for MPI lib detection MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND //ADVANCED property for variable: P4COMMAND P4COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_BUILD_TYPE PARAVIEW_BUILD_TYPE-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_CATALYST_EDITION PARAVIEW_CATALYST_EDITION-STRINGS:INTERNAL=Essentials;Extras;Rendering-Base //ADVANCED property for variable: PARAVIEW_EXTERNAL_PROJECTS PARAVIEW_EXTERNAL_PROJECTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_EXTRA_CMAKE_ARGUMENTS PARAVIEW_EXTRA_CMAKE_ARGUMENTS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PARAVIEW_PACKAGE_SUFFIX PARAVIEW_PACKAGE_SUFFIX-ADVANCED:INTERNAL=1 //STRINGS property for variable: PARAVIEW_RENDERING_BACKEND PARAVIEW_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2 //ADVANCED property for variable: PARAVIEW_VERSION_DEFAULT PARAVIEW_VERSION_DEFAULT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PASS_LD_LIBRARY_PATH_FOR_BUILDS PASS_LD_LIBRARY_PATH_FOR_BUILDS-ADVANCED:INTERNAL=1 PC_LIBXML_CFLAGS:INTERNAL=-I/usr/include/libxml2 PC_LIBXML_CFLAGS_I:INTERNAL= PC_LIBXML_CFLAGS_OTHER:INTERNAL= PC_LIBXML_FOUND:INTERNAL=1 PC_LIBXML_INCLUDEDIR:INTERNAL=/usr/include PC_LIBXML_INCLUDE_DIRS:INTERNAL=/usr/include/libxml2 PC_LIBXML_LDFLAGS:INTERNAL=-lxml2 PC_LIBXML_LDFLAGS_OTHER:INTERNAL= PC_LIBXML_LIBDIR:INTERNAL=/usr/lib64 PC_LIBXML_LIBRARIES:INTERNAL=xml2 PC_LIBXML_LIBRARY_DIRS:INTERNAL= PC_LIBXML_LIBS:INTERNAL= PC_LIBXML_LIBS_L:INTERNAL= PC_LIBXML_LIBS_OTHER:INTERNAL= PC_LIBXML_LIBS_PATHS:INTERNAL= PC_LIBXML_PREFIX:INTERNAL=/usr PC_LIBXML_STATIC_CFLAGS:INTERNAL=-I/usr/include/libxml2 PC_LIBXML_STATIC_CFLAGS_I:INTERNAL= PC_LIBXML_STATIC_CFLAGS_OTHER:INTERNAL= PC_LIBXML_STATIC_INCLUDE_DIRS:INTERNAL=/usr/include/libxml2 PC_LIBXML_STATIC_LDFLAGS:INTERNAL=-lxml2;-lz;-lm PC_LIBXML_STATIC_LDFLAGS_OTHER:INTERNAL= PC_LIBXML_STATIC_LIBDIR:INTERNAL= PC_LIBXML_STATIC_LIBRARIES:INTERNAL=xml2;z;m PC_LIBXML_STATIC_LIBRARY_DIRS:INTERNAL= PC_LIBXML_STATIC_LIBS:INTERNAL= PC_LIBXML_STATIC_LIBS_L:INTERNAL= PC_LIBXML_STATIC_LIBS_OTHER:INTERNAL= PC_LIBXML_STATIC_LIBS_PATHS:INTERNAL= PC_LIBXML_VERSION:INTERNAL=2.7.6 PC_LIBXML_libxml-2.0_INCLUDEDIR:INTERNAL= PC_LIBXML_libxml-2.0_LIBDIR:INTERNAL= PC_LIBXML_libxml-2.0_PREFIX:INTERNAL= PC_LIBXML_libxml-2.0_VERSION:INTERNAL= //ADVANCED property for variable: PKG_CONFIG_EXECUTABLE PKG_CONFIG_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_LIBRARY PYTHON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_LIBRARY_DEBUG PYTHON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: PYTHON_LIBRARY_RELEASE PYTHON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_getconf ProcessorCount_cmd_getconf-ADVANCED:INTERNAL=1 //ADVANCED property for variable: ProcessorCount_cmd_sysctl ProcessorCount_cmd_sysctl-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 QT_BINARY_DIR:INTERNAL=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DESIGNER_EXECUTABLE QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_DOC_DIR QT_DOC_DIR-ADVANCED:INTERNAL=1 QT_HEADERS_DIR:INTERNAL=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/include //ADVANCED property for variable: QT_IMPORTS_DIR QT_IMPORTS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LIBRARY_DIR QT_LIBRARY_DIR-ADVANCED:INTERNAL=1 //Qt library dir QT_LIBRARY_DIR:INTERNAL=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/lib //ADVANCED property for variable: QT_LINGUIST_EXECUTABLE QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LRELEASE_EXECUTABLE QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_LUPDATE_EXECUTABLE QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MKSPECS_DIR QT_MKSPECS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_MOC_EXECUTABLE QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_INCLUDE_DIR QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_PLUGINS_DIR QT_PLUGINS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //MODIFIED property for variable: QT_QMAKE_EXECUTABLE QT_QMAKE_EXECUTABLE-MODIFIED:INTERNAL=ON QT_QMAKE_EXECUTABLE_LAST:INTERNAL=/glb/data/hpcrnd/easybuild/PRODUCTION/software/rhel/6/Qt/4.8.6-goolf-2015.02/bin/qmake //ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG QT_QNATIVEWIFIBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE QT_QNATIVEWIFIBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_DEBUG QT_QTGA_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGA_PLUGIN_RELEASE QT_QTGA_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_INCLUDE_DIR QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_RCC_EXECUTABLE QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_TRANSLATIONS_DIR QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC3_EXECUTABLE QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_UIC_EXECUTABLE QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1 //ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1 //Have symbol Q_WS_MAC Q_WS_MAC:INTERNAL= //Have symbol Q_WS_QWS Q_WS_QWS:INTERNAL= //Have symbol Q_WS_WIN Q_WS_WIN:INTERNAL= //Have symbol Q_WS_X11 Q_WS_X11:INTERNAL= //ADVANCED property for variable: SCPCOMMAND SCPCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SED_EXECUTABLE SED_EXECUTABLE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SITE SITE-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SBATCH_COMMAND SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SLURM_SRUN_COMMAND SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1 //STRINGS property for variable: SUPERBUILD_DEFAULT_INSTALL SUPERBUILD_DEFAULT_INSTALL-STRINGS:INTERNAL=paraview/TGZ;catalyst/TGZ;paraviewsdk/TGZ //ADVANCED property for variable: SUPERBUILD_PROJECT_PARALLELISM SUPERBUILD_PROJECT_PARALLELISM-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_bzip2_OUTPUT SUPPRESS_bzip2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_fontconfig_OUTPUT SUPPRESS_fontconfig_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_freetype_OUTPUT SUPPRESS_freetype_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_libxml2_OUTPUT SUPPRESS_libxml2_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_mpi_OUTPUT SUPPRESS_mpi_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_paraview_OUTPUT SUPPRESS_paraview_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_png_OUTPUT SUPPRESS_png_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_python_OUTPUT SUPPRESS_python_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_pythonsetuptools_OUTPUT SUPPRESS_pythonsetuptools_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_qt4_OUTPUT SUPPRESS_qt4_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SUPPRESS_zlib_OUTPUT SUPPRESS_zlib_OUTPUT-ADVANCED:INTERNAL=1 //ADVANCED property for variable: SVNCOMMAND SVNCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: USE_NONFREE_COMPONENTS USE_NONFREE_COMPONENTS-ADVANCED:INTERNAL=1 //MODIFIED property for variable: USE_SYSTEM_freetype USE_SYSTEM_freetype-MODIFIED:INTERNAL=ON //MODIFIED property for variable: USE_SYSTEM_libxml2 USE_SYSTEM_libxml2-MODIFIED:INTERNAL=ON //MODIFIED property for variable: USE_SYSTEM_mpi USE_SYSTEM_mpi-MODIFIED:INTERNAL=ON //MODIFIED property for variable: USE_SYSTEM_python USE_SYSTEM_python-MODIFIED:INTERNAL=ON //MODIFIED property for variable: USE_SYSTEM_qt4 USE_SYSTEM_qt4-MODIFIED:INTERNAL=ON __pkg_config_checked_PC_LIBXML:INTERNAL=1 //STRINGS property for variable: mesa_SOURCE_SELECTION mesa_SOURCE_SELECTION-STRINGS:INTERNAL=13.0.0;git //ADVANCED property for variable: mesa_USE_SWR mesa_USE_SWR-ADVANCED:INTERNAL=1 //ADVANCED property for variable: mesa_USE_TEXTURE_FLOAT mesa_USE_TEXTURE_FLOAT-ADVANCED:INTERNAL=1 mesa_use_texture_float_warned_once:INTERNAL=OFF //ADVANCED property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-ADVANCED:INTERNAL=1 //STRINGS property for variable: ospray_BUILD_ISA ospray_BUILD_ISA-STRINGS:INTERNAL=SSE;AVX;AVX2;AVX512;ALL //STRINGS property for variable: paraview_SOURCE_SELECTION paraview_SOURCE_SELECTION-STRINGS:INTERNAL=5.2.0;git;source prefix_result:INTERNAL=/usr/lib64 //ADVANCED property for variable: qt4_ENABLE_OPENSSL qt4_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_EXTRA_CONFIGURATION_OPTIONS qt4_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD qt4_WORK_AROUND_BROKEN_ASSISTANT_BUILD-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_ENABLE_OPENSSL qt5_ENABLE_OPENSSL-ADVANCED:INTERNAL=1 //ADVANCED property for variable: qt5_EXTRA_CONFIGURATION_OPTIONS qt5_EXTRA_CONFIGURATION_OPTIONS-ADVANCED:INTERNAL=1 //ADVANCED property for variable: superbuild_download_location superbuild_download_location-ADVANCED:INTERNAL=1 superbuild_python_executable:INTERNAL=/glb/home/incsu0/ir5/ParaView-Superbuild/5.2/build/install/bin/python //CHECK_TYPE_SIZE: sizeof(void*) void_ptr_size:INTERNAL=8 -------------- next part -------------- A non-text attachment was scrubbed... Name: pv5.2.runtime.log Type: application/octet-stream Size: 15591 bytes Desc: not available URL: From david.lonie at kitware.com Wed Nov 30 11:41:30 2016 From: david.lonie at kitware.com (David Lonie) Date: Wed, 30 Nov 2016 11:41:30 -0500 Subject: [Paraview-developers] paraview 5.2 runtime error with 'fontconfig" In-Reply-To: References: Message-ID: Ben, is this related to your third party updates? On Wed, Nov 30, 2016 at 2:56 AM, Chiranjib Sur wrote: > Hi, > With my ParaView5.2 build (via superbuild), I get a run time error > followed by a seg fault. > Any clue what went missing during my build procedure? > > Here are the runtime log and the CMakeCache.txt files attached. > > My system configuration is : RHEL6, c++11 GNU compiler, python 2.7+, CMake > 3.7, Qt4.8 > > Thanks, > Chiranjib > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bastien.jacquet at kitware.com Wed Nov 30 11:54:59 2016 From: bastien.jacquet at kitware.com (Bastien Jacquet) Date: Wed, 30 Nov 2016 17:54:59 +0100 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: Hey Cory, I've successfully built the paraview superbuild with default option on my mac. I'm try to do the same with bigmac options. I'm wondering, why is the superbuild using a local, non-superbuild, "Qt-4.8.6-patched" install ? QT_QMAKE_EXECUTABLE:FILEPATH /Users/kitware/dashboards/support/Qt-4.8.6-patched/bin/qmake Should I be worried about the "patched" name ? Can I just use the superbuild Qt ? Bastien On Mon, Nov 28, 2016 at 4:19 PM, Cory Quammen wrote: > Bastien and Mathieu, > > The best thing would be to build against the ParaView SDK. I don't > think this is available in the Mac builds, though, and I'm not sure it > is available for other OS's either. > > Utkarsh, am I wrong about this? I don't see anything in the > ParaView.app that looks like an SDK. > > In some cases we have shipped these kinds of plugins with the ParaView > binaries and leave them unloaded by default. See the > GeodesicMeasurement plugin, for instance. If the plugin is > proprietary, that won't work, though. > > Otherwise, to be compatible with the official 5.2 binary, you would > need to have a 5.2 build of ParaView on bigmac, which is the buildbot > that produces the binaries, and build your plugin against that. > Checkout the v5.2.0 tag in the superbuild and set the build options to > those used for the official binary which are listed in one of the > buildbot superbuilds, e.g., > > https://buildbot.kitware.com/builders/paraview-bigmac-osx- > shared-release%2Bopengl2%2Bosx10.8%2Bqt4%2Bsuperbuild/builds/186 > > It may be more practical to build a custom ParaView binary on a Mac > you have on hand along with the plugin and distribute those to your > customer, especially if the plugin will be changing in the future. > > Hope that helps, > Cory > > > On Mon, Nov 28, 2016 at 5:33 AM, Bastien Jacquet > wrote: > > Hello Cory, > > > > It was actually a request from me. A customer wants his pv plugin > > distributed as a binary, compatible with Paraview official binary. Their > > main OS is OS X. > > Can you point me to the right path to do so ? > > > > Thanks, > > Bastien > > > > Bastien Jacquet, PhD > > Technical Leader - Computer Vision Team > > Kitware SAS > > 26 rue Louis Gu?rin - 69100 Villeurbanne - France > > F: +33 (0)4.37.45.04.15 > > > > On Sun, Nov 27, 2016 at 3:14 AM, Cory Quammen > > wrote: > >> > >> Mathieu, > >> > >> The Mac OS X release is built by the paraview-superbuild buildbot on > >> bigmac. I kicked off the builds for this release. What's up? > >> > >> Thanks, > >> Cory > >> > >> On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal > >> wrote: > >> > Hi > >> > > >> > Who is responsible for compiling the osx version of ParaView release ? > >> > > >> > Thanks, > >> > > >> > Mathieu Westphal > >> > > >> > _______________________________________________ > >> > Powered by www.kitware.com > >> > > >> > Visit other Kitware open-source projects at > >> > http://www.kitware.com/opensource/opensource.html > >> > > >> > Search the list archives at: > >> > http://markmail.org/search/?q=Paraview-developers > >> > > >> > Follow this link to subscribe/unsubscribe: > >> > http://public.kitware.com/mailman/listinfo/paraview-developers > >> > > >> > >> > >> > >> -- > >> Cory Quammen > >> Staff R&D Engineer > >> Kitware, Inc. > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Search the list archives at: > >> http://markmail.org/search/?q=Paraview-developers > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview-developers > > > > > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Nov 30 12:06:51 2016 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 30 Nov 2016 12:06:51 -0500 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: Qt takes a long time to build as I'm sure you know, so I think to save on superbuild build time, we are using an installed Qt. You might be able to use the superbuild Qt, but I can't guarantee you that it is working on OS X. Qt 4.8.6 needs to be patched to build on recent versions of OS X, hence the patched name. I'm not sure where the source for that comes from - it might exist on bigmac somewhere. Ben or Shawn would likely have a more authoritative answer than me. Cory On Wed, Nov 30, 2016 at 11:54 AM, Bastien Jacquet < bastien.jacquet at kitware.com> wrote: > Hey Cory, > > I've successfully built the paraview superbuild with default option on my > mac. > I'm try to do the same with bigmac options. > I'm wondering, why is the superbuild using a local, non-superbuild, > "Qt-4.8.6-patched" install ? > QT_QMAKE_EXECUTABLE:FILEPATH /Users/kitware/dashboards/ > support/Qt-4.8.6-patched/bin/qmake > Should I be worried about the "patched" name ? Can I just use the > superbuild Qt ? > > Bastien > > On Mon, Nov 28, 2016 at 4:19 PM, Cory Quammen > wrote: > >> Bastien and Mathieu, >> >> The best thing would be to build against the ParaView SDK. I don't >> think this is available in the Mac builds, though, and I'm not sure it >> is available for other OS's either. >> >> Utkarsh, am I wrong about this? I don't see anything in the >> ParaView.app that looks like an SDK. >> >> In some cases we have shipped these kinds of plugins with the ParaView >> binaries and leave them unloaded by default. See the >> GeodesicMeasurement plugin, for instance. If the plugin is >> proprietary, that won't work, though. >> >> Otherwise, to be compatible with the official 5.2 binary, you would >> need to have a 5.2 build of ParaView on bigmac, which is the buildbot >> that produces the binaries, and build your plugin against that. >> Checkout the v5.2.0 tag in the superbuild and set the build options to >> those used for the official binary which are listed in one of the >> buildbot superbuilds, e.g., >> >> https://buildbot.kitware.com/builders/paraview-bigmac-osx-sh >> ared-release%2Bopengl2%2Bosx10.8%2Bqt4%2Bsuperbuild/builds/186 >> >> It may be more practical to build a custom ParaView binary on a Mac >> you have on hand along with the plugin and distribute those to your >> customer, especially if the plugin will be changing in the future. >> >> Hope that helps, >> Cory >> >> >> On Mon, Nov 28, 2016 at 5:33 AM, Bastien Jacquet >> wrote: >> > Hello Cory, >> > >> > It was actually a request from me. A customer wants his pv plugin >> > distributed as a binary, compatible with Paraview official binary. Their >> > main OS is OS X. >> > Can you point me to the right path to do so ? >> > >> > Thanks, >> > Bastien >> > >> > Bastien Jacquet, PhD >> > Technical Leader - Computer Vision Team >> > Kitware SAS >> > 26 rue Louis Gu?rin - 69100 Villeurbanne - France >> > F: +33 (0)4.37.45.04.15 >> > >> > On Sun, Nov 27, 2016 at 3:14 AM, Cory Quammen > > >> > wrote: >> >> >> >> Mathieu, >> >> >> >> The Mac OS X release is built by the paraview-superbuild buildbot on >> >> bigmac. I kicked off the builds for this release. What's up? >> >> >> >> Thanks, >> >> Cory >> >> >> >> On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal >> >> wrote: >> >> > Hi >> >> > >> >> > Who is responsible for compiling the osx version of ParaView release >> ? >> >> > >> >> > Thanks, >> >> > >> >> > Mathieu Westphal >> >> > >> >> > _______________________________________________ >> >> > Powered by www.kitware.com >> >> > >> >> > Visit other Kitware open-source projects at >> >> > http://www.kitware.com/opensource/opensource.html >> >> > >> >> > Search the list archives at: >> >> > http://markmail.org/search/?q=Paraview-developers >> >> > >> >> > Follow this link to subscribe/unsubscribe: >> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >> >> > >> >> >> >> >> >> >> >> -- >> >> Cory Quammen >> >> Staff R&D Engineer >> >> Kitware, Inc. >> >> _______________________________________________ >> >> Powered by www.kitware.com >> >> >> >> Visit other Kitware open-source projects at >> >> http://www.kitware.com/opensource/opensource.html >> >> >> >> Search the list archives at: >> >> http://markmail.org/search/?q=Paraview-developers >> >> >> >> Follow this link to subscribe/unsubscribe: >> >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > >> > >> >> >> >> -- >> Cory Quammen >> Staff R&D Engineer >> Kitware, Inc. >> > > -- Cory Quammen Staff R&D Engineer Kitware, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Nov 30 12:28:08 2016 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 30 Nov 2016 12:28:08 -0500 Subject: [Paraview-developers] ParaView Release OSX Compilation In-Reply-To: References: Message-ID: You should just be able to use the superbuild Qt. As Cory mentioned, Qt 4.8.6 has to be patched for recent OSX versions. Ben has a project in the common superbuild that uses the superbuild to build and install Qt in a folder on the system and that is what we used to create that install of Qt. Look in the paraview superbuild source under superbuild/standalone-qt if you're interested. But you should get the same Qt by just running the superbuild. Shawn On Wed, Nov 30, 2016 at 12:06 PM, Cory Quammen wrote: > Qt takes a long time to build as I'm sure you know, so I think to save on > superbuild build time, we are using an installed Qt. You might be able to > use the superbuild Qt, but I can't guarantee you that it is working on OS X. > > Qt 4.8.6 needs to be patched to build on recent versions of OS X, hence > the patched name. I'm not sure where the source for that comes from - it > might exist on bigmac somewhere. > > Ben or Shawn would likely have a more authoritative answer than me. > > Cory > > On Wed, Nov 30, 2016 at 11:54 AM, Bastien Jacquet < > bastien.jacquet at kitware.com> wrote: > >> Hey Cory, >> >> I've successfully built the paraview superbuild with default option on my >> mac. >> I'm try to do the same with bigmac options. >> I'm wondering, why is the superbuild using a local, non-superbuild, >> "Qt-4.8.6-patched" install ? >> QT_QMAKE_EXECUTABLE:FILEPATH /Users/kitware/dashboards/supp >> ort/Qt-4.8.6-patched/bin/qmake >> Should I be worried about the "patched" name ? Can I just use the >> superbuild Qt ? >> >> Bastien >> >> On Mon, Nov 28, 2016 at 4:19 PM, Cory Quammen >> wrote: >> >>> Bastien and Mathieu, >>> >>> The best thing would be to build against the ParaView SDK. I don't >>> think this is available in the Mac builds, though, and I'm not sure it >>> is available for other OS's either. >>> >>> Utkarsh, am I wrong about this? I don't see anything in the >>> ParaView.app that looks like an SDK. >>> >>> In some cases we have shipped these kinds of plugins with the ParaView >>> binaries and leave them unloaded by default. See the >>> GeodesicMeasurement plugin, for instance. If the plugin is >>> proprietary, that won't work, though. >>> >>> Otherwise, to be compatible with the official 5.2 binary, you would >>> need to have a 5.2 build of ParaView on bigmac, which is the buildbot >>> that produces the binaries, and build your plugin against that. >>> Checkout the v5.2.0 tag in the superbuild and set the build options to >>> those used for the official binary which are listed in one of the >>> buildbot superbuilds, e.g., >>> >>> https://buildbot.kitware.com/builders/paraview-bigmac-osx-sh >>> ared-release%2Bopengl2%2Bosx10.8%2Bqt4%2Bsuperbuild/builds/186 >>> >>> It may be more practical to build a custom ParaView binary on a Mac >>> you have on hand along with the plugin and distribute those to your >>> customer, especially if the plugin will be changing in the future. >>> >>> Hope that helps, >>> Cory >>> >>> >>> On Mon, Nov 28, 2016 at 5:33 AM, Bastien Jacquet >>> wrote: >>> > Hello Cory, >>> > >>> > It was actually a request from me. A customer wants his pv plugin >>> > distributed as a binary, compatible with Paraview official binary. >>> Their >>> > main OS is OS X. >>> > Can you point me to the right path to do so ? >>> > >>> > Thanks, >>> > Bastien >>> > >>> > Bastien Jacquet, PhD >>> > Technical Leader - Computer Vision Team >>> > Kitware SAS >>> > 26 rue Louis Gu?rin - 69100 Villeurbanne - France >>> > F: +33 (0)4.37.45.04.15 >>> > >>> > On Sun, Nov 27, 2016 at 3:14 AM, Cory Quammen < >>> cory.quammen at kitware.com> >>> > wrote: >>> >> >>> >> Mathieu, >>> >> >>> >> The Mac OS X release is built by the paraview-superbuild buildbot on >>> >> bigmac. I kicked off the builds for this release. What's up? >>> >> >>> >> Thanks, >>> >> Cory >>> >> >>> >> On Fri, Nov 25, 2016 at 3:39 AM, Mathieu Westphal >>> >> wrote: >>> >> > Hi >>> >> > >>> >> > Who is responsible for compiling the osx version of ParaView >>> release ? >>> >> > >>> >> > Thanks, >>> >> > >>> >> > Mathieu Westphal >>> >> > >>> >> > _______________________________________________ >>> >> > Powered by www.kitware.com >>> >> > >>> >> > Visit other Kitware open-source projects at >>> >> > http://www.kitware.com/opensource/opensource.html >>> >> > >>> >> > Search the list archives at: >>> >> > http://markmail.org/search/?q=Paraview-developers >>> >> > >>> >> > Follow this link to subscribe/unsubscribe: >>> >> > http://public.kitware.com/mailman/listinfo/paraview-developers >>> >> > >>> >> >>> >> >>> >> >>> >> -- >>> >> Cory Quammen >>> >> Staff R&D Engineer >>> >> Kitware, Inc. >>> >> _______________________________________________ >>> >> Powered by www.kitware.com >>> >> >>> >> Visit other Kitware open-source projects at >>> >> http://www.kitware.com/opensource/opensource.html >>> >> >>> >> Search the list archives at: >>> >> http://markmail.org/search/?q=Paraview-developers >>> >> >>> >> Follow this link to subscribe/unsubscribe: >>> >> http://public.kitware.com/mailman/listinfo/paraview-developers >>> > >>> > >>> >>> >>> >>> -- >>> Cory Quammen >>> Staff R&D Engineer >>> Kitware, Inc. >>> >> >> > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 30 14:50:25 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 30 Nov 2016 19:50:25 +0000 Subject: [Paraview-developers] ParaView superbuild and Source Message-ID: I have set the following variables, attempting to turn off Paraview's downloading from the paraview.org website. Yet, SuperBuild is downloading everything externally! What am I doing wrong? How can I make ParaView not do this download and just fail? Are the switches just ignored? cMakeVars = cMakeVars +\ '-DParaView_FROM_GIT:BOOL=OFF '+\ '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' Groan. Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Nov 30 15:13:06 2016 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 30 Nov 2016 15:13:06 -0500 Subject: [Paraview-developers] ParaView superbuild and Source In-Reply-To: References: Message-ID: Alan, We refactored the superbuild so that other projects than paraview could have multiple possible sources. The new variable is paraview_SOURCE_SELECTION. The options are '5.2.0' (downloads tarball from paraview.org and the default), 'git' (pulls git master), and 'source' which uses an external source dir. The git and source options are customizable with other variables (to specify which source dir or which git branch/tag to use). I think what you want now is this: cMakeVars = cMakeVars +\ '-Dparaview_SOURCE_SELECTION:STRING=source '+\ '-Dparaview_SOURCE_DIR:PATH='+pvSrcDir+' ' The first one has the same effect as the first two in your example and the last one sets the path to the source dir of ParaView. HTH, Shawn On Wed, Nov 30, 2016 at 2:50 PM, Scott, W Alan wrote: > I have set the following variables, attempting to turn off Paraview?s > downloading from the paraview.org website. Yet, SuperBuild is > downloading everything externally! What am I doing wrong? How can I make > ParaView not do this download and just fail? Are the switches just ignored? > > > > > > cMakeVars = cMakeVars +\ > > '-DParaView_FROM_GIT:BOOL=OFF '+\ > > '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ > > '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' > > > > > > Groan. > > > > Alan > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensou > rce/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 30 15:15:22 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 30 Nov 2016 20:15:22 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView superbuild and Source In-Reply-To: References: Message-ID: Excellent, thanks! Where are things like this documented? Do you have to run ccmake, and just guess? Thanks again, Alan From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Wednesday, November 30, 2016 1:13 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] ParaView superbuild and Source Alan, We refactored the superbuild so that other projects than paraview could have multiple possible sources. The new variable is paraview_SOURCE_SELECTION. The options are '5.2.0' (downloads tarball from paraview.org and the default), 'git' (pulls git master), and 'source' which uses an external source dir. The git and source options are customizable with other variables (to specify which source dir or which git branch/tag to use). I think what you want now is this: cMakeVars = cMakeVars +\ '-Dparaview_SOURCE_SELECTION:STRING=source '+\ '-Dparaview_SOURCE_DIR:PATH='+pvSrcDir+' ' The first one has the same effect as the first two in your example and the last one sets the path to the source dir of ParaView. HTH, Shawn On Wed, Nov 30, 2016 at 2:50 PM, Scott, W Alan > wrote: I have set the following variables, attempting to turn off Paraview?s downloading from the paraview.org website. Yet, SuperBuild is downloading everything externally! What am I doing wrong? How can I make ParaView not do this download and just fail? Are the switches just ignored? cMakeVars = cMakeVars +\ '-DParaView_FROM_GIT:BOOL=OFF '+\ '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' Groan. Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 30 17:03:11 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 30 Nov 2016 22:03:11 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView superbuild and Source In-Reply-To: References: Message-ID: <67cf9f63b12b441c9400b281c1b863ed@ES01AMSNLNT.srn.sandia.gov> Hi Shawn, Nope, once again the Superbuild is downloading from the web. Any other ideas? I wrote up details here: https://gitlab.kitware.com/paraview/paraview/issues/17059. Are there tests for this stuff in the nightly testing suite? This has bit me at least half a dozen times at this point? Alan From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Wednesday, November 30, 2016 1:13 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] ParaView superbuild and Source Alan, We refactored the superbuild so that other projects than paraview could have multiple possible sources. The new variable is paraview_SOURCE_SELECTION. The options are '5.2.0' (downloads tarball from paraview.org and the default), 'git' (pulls git master), and 'source' which uses an external source dir. The git and source options are customizable with other variables (to specify which source dir or which git branch/tag to use). I think what you want now is this: cMakeVars = cMakeVars +\ '-Dparaview_SOURCE_SELECTION:STRING=source '+\ '-Dparaview_SOURCE_DIR:PATH='+pvSrcDir+' ' The first one has the same effect as the first two in your example and the last one sets the path to the source dir of ParaView. HTH, Shawn On Wed, Nov 30, 2016 at 2:50 PM, Scott, W Alan > wrote: I have set the following variables, attempting to turn off Paraview?s downloading from the paraview.org website. Yet, SuperBuild is downloading everything externally! What am I doing wrong? How can I make ParaView not do this download and just fail? Are the switches just ignored? cMakeVars = cMakeVars +\ '-DParaView_FROM_GIT:BOOL=OFF '+\ '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' Groan. Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawn.waldon at kitware.com Wed Nov 30 17:21:55 2016 From: shawn.waldon at kitware.com (Shawn Waldon) Date: Wed, 30 Nov 2016 17:21:55 -0500 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView superbuild and Source In-Reply-To: <67cf9f63b12b441c9400b281c1b863ed@ES01AMSNLNT.srn.sandia.gov> References: <67cf9f63b12b441c9400b281c1b863ed@ES01AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, As far as I know that should have worked. I'm CCing some of the folks who work more on the superbuild than I do. Some answers are also inline below. On Wed, Nov 30, 2016 at 5:03 PM, Scott, W Alan wrote: > Hi Shawn, > > Nope, once again the Superbuild is downloading from the web. Any other > ideas? I wrote up details here: https://gitlab.kitware.com/ > paraview/paraview/issues/17059. > Not at the moment. I remembered enough from helping test this that I could look up the variable names. You could use ccmake to check they are spelled correctly but AFAIK that should work. > > Are there tests for this stuff in the nightly testing suite? This has bit > me at least half a dozen times at this point? > We test the local source directory case on the buildbots. But I don't know if we actually make sure it is using the right source... I'll double check. Shawn > > > *From:* Shawn Waldon [mailto:shawn.waldon at kitware.com] > *Sent:* Wednesday, November 30, 2016 1:13 PM > *To:* Scott, W Alan > *Cc:* paraview-developers at paraview.org > *Subject:* [EXTERNAL] Re: [Paraview-developers] ParaView superbuild and > Source > > > > Alan, > > We refactored the superbuild so that other projects than paraview could > have multiple possible sources. The new variable is > paraview_SOURCE_SELECTION. The options are '5.2.0' (downloads tarball from > paraview.org and the default), 'git' (pulls git master), and 'source' > which uses an external source dir. The git and source options are > customizable with other variables (to specify which source dir or which git > branch/tag to use). I think what you want now is this: > > cMakeVars = cMakeVars +\ > > '-Dparaview_SOURCE_SELECTION:STRING=source '+\ > > '-Dparaview_SOURCE_DIR:PATH='+pvSrcDir+' ' > > The first one has the same effect as the first two in your example and the > last one sets the path to the source dir of ParaView. > > > > HTH, > > Shawn > > > > On Wed, Nov 30, 2016 at 2:50 PM, Scott, W Alan wrote: > > I have set the following variables, attempting to turn off Paraview?s > downloading from the paraview.org website. Yet, SuperBuild is > downloading everything externally! What am I doing wrong? How can I make > ParaView not do this download and just fail? Are the switches just ignored? > > > > > > cMakeVars = cMakeVars +\ > > '-DParaView_FROM_GIT:BOOL=OFF '+\ > > '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ > > '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' > > > > > > Groan. > > > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Search the list archives at: http://markmail.org/search/?q= > Paraview-developers > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 30 17:58:11 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 30 Nov 2016 22:58:11 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: osmesa version of ParaView In-Reply-To: References: <5411832422714b7193b3dc3b47eacb40@ES01AMSNLNT.srn.sandia.gov> Message-ID: So, just to be really clear (I got a bit confused here?) I am on a Linux box, such as my local blade or Linux workstation. I want to test a remote Paraview install, or my data is on a remote Linux server (and I want to run a standalone version of ParaView). I want to do the following: ssh -X (or ssh -Y) paraview ?magicFlagsGoHere and it just works on a remote Linux box that does not allow a GLX context. Thanks, alan From: Ken Martin [mailto:ken.martin at kitware.com] Sent: Tuesday, November 29, 2016 2:32 PM To: Scott, W Alan Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] osmesa version of ParaView Couple quick thoughts If we can connect to the remote display using GLX (but not forwarded) then we can render remotely (offscreen but using normal OpenGL) and then copy the result to an Xwindow which is forwarded to a local machine. Sort of a RenderingDisplay=:0.0 Display=:1.0 where 1.0 is the forwarded one. I recall there being an issue with osmesa and accelerated opengl in the same binary but I have very limited experience with it. On Tue, Nov 29, 2016 at 3:39 PM, Scott, W Alan > wrote: Cory/ Utkarsh/ Guys, I think we need to be able to build an osmesa version of ParaView, and we need this rendering option as a command line option for all Kitware Linux downloads. The reason is that the next version of Redhat ? RHEL 7 will no longer allow the forwarding of GLX contexts. Thus, to be able to X forward ParaView back to a local computer, we will need to render into only an X window. This is already giving us issues at Sandia with new Linux installs. Is this possible? How hard will it be? Any ideas on schedule? Before I write this up as a bug, I figured I would see what type of discussion we get in this thread. Thanks, Alan -------------------------------------------------------- W. Alan Scott ParaView Support Manager SAIC Sandia National Laboratories, MS 0822 Org 9326 - Building 880 A1-K (505) 284-0932 FAX (505) 284-5619 --------------------------------------------------------- _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -- Ken Martin PhD Chairman & CFO Kitware Inc. 28 Corporate Drive Clifton Park NY 12065 518 371 3971 This communication, including all attachments, contains confidential and legally privileged information, and it is intended only for the use of the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. If you received this communication in error please notify us immediately and destroy the original message. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Nov 30 19:17:23 2016 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 1 Dec 2016 00:17:23 +0000 Subject: [Paraview-developers] [EXTERNAL] Re: ParaView superbuild and Source In-Reply-To: References: <67cf9f63b12b441c9400b281c1b863ed@ES01AMSNLNT.srn.sandia.gov> Message-ID: <133a220f524b445ab0d84f4ec8db41ed@ES01AMSNLNT.srn.sandia.gov> Shawn, OK ? with this one issue I have dug a bit deeper. What I had was according to the directions on the ParaView Superbuild site, located here: https://gitlab.kitware.com/paraview/paraview-superbuild. You told me to do something different. Neither appears to work. So, issue number one is to figure what we need to do, and get it working correctly, and second is to update the docs. Help? Thanks, Alan From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Wednesday, November 30, 2016 3:22 PM To: Scott, W Alan ; Chuck Atkins ; Ben Boeckel Cc: paraview-developers at paraview.org Subject: Re: [EXTERNAL] Re: [Paraview-developers] ParaView superbuild and Source Hi Alan, As far as I know that should have worked. I'm CCing some of the folks who work more on the superbuild than I do. Some answers are also inline below. On Wed, Nov 30, 2016 at 5:03 PM, Scott, W Alan > wrote: Hi Shawn, Nope, once again the Superbuild is downloading from the web. Any other ideas? I wrote up details here: https://gitlab.kitware.com/paraview/paraview/issues/17059. Not at the moment. I remembered enough from helping test this that I could look up the variable names. You could use ccmake to check they are spelled correctly but AFAIK that should work. Are there tests for this stuff in the nightly testing suite? This has bit me at least half a dozen times at this point? We test the local source directory case on the buildbots. But I don't know if we actually make sure it is using the right source... I'll double check. Shawn From: Shawn Waldon [mailto:shawn.waldon at kitware.com] Sent: Wednesday, November 30, 2016 1:13 PM To: Scott, W Alan > Cc: paraview-developers at paraview.org Subject: [EXTERNAL] Re: [Paraview-developers] ParaView superbuild and Source Alan, We refactored the superbuild so that other projects than paraview could have multiple possible sources. The new variable is paraview_SOURCE_SELECTION. The options are '5.2.0' (downloads tarball from paraview.org and the default), 'git' (pulls git master), and 'source' which uses an external source dir. The git and source options are customizable with other variables (to specify which source dir or which git branch/tag to use). I think what you want now is this: cMakeVars = cMakeVars +\ '-Dparaview_SOURCE_SELECTION:STRING=source '+\ '-Dparaview_SOURCE_DIR:PATH='+pvSrcDir+' ' The first one has the same effect as the first two in your example and the last one sets the path to the source dir of ParaView. HTH, Shawn On Wed, Nov 30, 2016 at 2:50 PM, Scott, W Alan > wrote: I have set the following variables, attempting to turn off Paraview?s downloading from the paraview.org website. Yet, SuperBuild is downloading everything externally! What am I doing wrong? How can I make ParaView not do this download and just fail? Are the switches just ignored? cMakeVars = cMakeVars +\ '-DParaView_FROM_GIT:BOOL=OFF '+\ '-DParaView_FROM_SOURCE_DIR:BOOL=ON '+\ '-DPARAVIEW_SOURCE_DIR:PATH='+pvSrcDir+' ' Groan. Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Search the list archives at: http://markmail.org/search/?q=Paraview-developers Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: