Hi,
There is currently a lot of effort put into the superbuild directory.
It seems interesting, but I can't find much information on the
functionnality being developped.
Is it somehow related to branded apps?
Is there a wiki page describing the functionnality?
Best,
Stephane
Stephane PLO
Hi,
Is it possible to "make install" with the Superbuild? I set the
CMAKE_INSTALL_PREFIX but "make install" doesn't work and the packages are
all in a PACKAGE-prefix directory in the build directory. Am I doing
something wrong?
Thanks,
Paul
___
Powere
I created a superbuild yesterday, and now when I run ParaView, I see the
following error. Then, Linux basically locks up. I also get the second line
below in the ParaView Output window. Has anyone else seen this?
Thanks,
Alan
(:19814): Gtk-WARNING **: Attempt to load unknown IM context type
Hi Stephane,
SuperBuild is something I am working on to build ParaView and it's
dependencies using CMake's external_project feature. External_Project allows
us to download, patch, configure, build and install a dependency with an
easy to use function call, regardless if the dependency uses CMake n
Oops, hit send too quickly.
It will also build (probably today) CGNS and Silo (on Linux/Mac) as well.
I will keep everyone posted!
On Fri, Jan 7, 2011 at 9:00 AM, David Partyka wrote:
> Hi Stephane,
>
> SuperBuild is something I am working on to build ParaView and it's
> dependencies using CMak
It seems that in the SuperBuild directory the contents of the
External_HDF5.cmake seem to have the contents of External_PNG.cmake instead.
Just FYI if it matters.
___
Mike Jackson www.bluequartz.net
Principal Software
Hi Paul,
The superbuild is something new I wrote to help produce our binaries
available for download on the website. It wouldn't be hard to propagate
CMAKE_INSTALL_PREFIX into each of the dependencies. I will make a bug for
myself to add this functionality.
http://www.paraview.org/Bug/view.php?id
I've been playing around with SuperBuild and it seems to working correct. But,
it also seems to be pulling the most recent source updates from the git
repository. Is there a way use SuperBuild to only build the most recent
production release (3.98.1)?
Thanks
___
Is there a way to tell the SuperBuild process to not look for software updates
using GIT? I doing a build on a system that doesn't have public network
access and I'm actually dying on a complaint about my instance of git being too
old. However, I have already copied in the sources, so I don
hello everyone,
does anybody out there would like to share some experience with a recent
ParaView Superbuild (>=version 5.2) with *Docker* ?
- Suggestions/recommendations for existing Dockerfiles ?
- Suggestions for settings like: Qt version, Mesa3D vs. OpenGL, ... ?
Thanks a lot.
B
I have this fixed on my local branch. I'll be merging shortly.
On Thu, Feb 17, 2011 at 12:51 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> It seems that in the SuperBuild directory the contents of the
> External_HDF5.cmake seem to have the contents of External_PNG.cmake instead.
> J
I went to the Paraview SuperBuild page and found this message:
"Updated for ParaView Superbuild have moved to the source repository
<https://gitlab.kitware.com/paraview/paraview-superbuild/> starting with
ParaView 5.2. For docs for earlier versions, please check out the history
tab fo
I think there is an error in the page :
http://paraview.org/Wiki/ParaView_Binaries
I tried to download Xcode 4.3 for my mac 10.6.8 to build a plugin
compatible with the official binaries. But Xcode 4.3 is only available
for Lion.
So my question is: The 3.98.0 binary for mac is really compil
-6080
Email: reute...@ornl.gov
From: , "Richard C CIV USARMY ARL (RickUS)"
mailto:richard.c.angelini@mail.mil>>
Date: Friday, April 19, 2013 8:39 AM
To: "paraview@paraview.org<mailto:paraview@paraview.org>"
mailto:paraview@paraview.org>>
Subject: [Paraview
You can do the following:
> edit the versions.cmake file
> in there, you'll find a stub like so
add_revision(paraview
GIT_REPOSITORY git://paraview.org/ParaView.git
GIT_TAG "master")
Change that to something as follows:
add_revision(paraview
URL
URL_MD5 )
I think I want to add some mo
Maybe when we tag a release in Superbuild we modify the verions.cmake to
point to tarballs for just that tag. That allows people to be able to
replicate the release without having to do anything.
On Wed, May 1, 2013 at 12:07 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:
> You can do
That sounds like a good idea.
On Wed, May 1, 2013 at 12:51 PM, Robert Maynard
wrote:
> Maybe when we tag a release in Superbuild we modify the verions.cmake to
> point to tarballs for just that tag. That allows people to be able to
> replicate the release without having to do anything.
>
>
> On W
ectory and then rerun "make install", I get the proper
installation. Am I setting the wrong variable when I run the cmake
command?This is the correct variable as described in the wiki page at
http://paraview.org/Wiki/ParaView/Superbuild
I'm seeing this
in/cc" is not able to compile a simple test program.
It fails with the following output:
Change Dir:
/Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp
Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075
[1/2] Building C object
Hi,
I'm having an issue with the ParaView Superbuild on Windows
(VS2012). I get this error during the build process:
322> Compiling Python package 'pygments'
322> Listing
C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-bu
I did a fresh pull of the ParaView superbuild repository, and now I can’t do
a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
First, I had to remove the entries for “qt” and “scipy" in the
CMakeLists.txt:
-- Determined source version for paraview: 5.2.0
CMake Error at superbuild/CMakeList
On Fri, Apr 07, 2017 at 18:30:11 +0200, Florian Hoffmann wrote:
> does anybody out there would like to share some experience with a recent
> ParaView Superbuild (>=version 5.2) with *Docker* ?
>
> - Suggestions/recommendations for existing Dockerfiles ?
>
> - Suggestions
On Mon, Apr 10, 2017 at 3:49 PM, Ben Boeckel
wrote:
> On Fri, Apr 07, 2017 at 18:30:11 +0200, Florian Hoffmann wrote:
> > does anybody out there would like to share some experience with a recent
> > ParaView Superbuild (>=version 5.2) with *Docker* ?
> >
> > - S
On Mon, Apr 10, 2017 at 16:18:21 +0200, Nabil Ghodbane wrote:
> it is not clear to me what you did. Did you build your own docker with
> Paraview on top of it and if this is the case could you share the
> Dockerfile you implemented to build the docker image?
The Dockerfile (and associated files) w
thanks for sharing!
Nabil Ghodbane (Ph. D. Habil*.*)
Phone: +33 6 34 42 33 43
Mailto: nabil.ghodb...@gmail.com
On Mon, Apr 10, 2017 at 5:27 PM, Ben Boeckel
wrote:
> On Mon, Apr 10, 2017 at 16:18:21 +0200, Nabil Ghodbane wrote:
> > it is not clear to me what you did. Did you build your own dock
Hi Rick,
It looks like you caught us in transition moving the build
instructions from the wiki to the paraview-superbuild repository.
We have just added build instructions from the README.md file located at:
https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md
The
Hi Felipe,
You were right there was a slight issue on the page that we just fix.
The computer on which we build on is a 10.7.3 but we definitely use the
10.6 SDK to allow the generated binaries to work from 10.6 to 10.8.
Hope that helps, and thanks for reporting the issue.
Seb
On Wed, Jan 9, 2
It should be clear that the binaries are 64bit so they will not work on
32bit SnowLeopard machines. If you need a 32bit OSX build for legacy
machines you will need to compile and build ParaView yourself.
On Wed, Jan 9, 2013 at 8:51 AM, Sebastien Jourdain <
sebastien.jourd...@kitware.com> wrote:
: Wednesday, May 01, 2013 12:08 PM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] SuperBuild question
You can do the following:
> edit the versions.cmake file
> in there, you'll find a stub like so
add_revision(paraview
GIT_REP
it [mailto:utkarsh.ayac...@kitware.com]
> Sent: Wednesday, May 01, 2013 12:08 PM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] SuperBuild question
>
> You can do the following:
>
>> edit the versions.cmake f
the installation
> directory and then rerun "make install", I get the proper installation.
> Am I setting the wrong variable when I run the cmake command? This is the
> correct variable as described in the wiki page at
> http://paraview.org/Wiki/ParaView/Superbuild
>
&
: Wednesday, May 29, 2013 8:43 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild installation directory
Rick,
There is always going to be a BUILD/install. This is where all the
internal packages ParaViewSuperbuild builds are temporarily
RL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild installation directory
Rick,
There is always going to be a BUILD/install. This is where all the
internal packages ParaViewSuperbuild builds are temporarily installed.
Something is resetting the CMAKE_INSTALL_PREFIX. I can
> From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
> Sent: Wednesday, May 29, 2013 8:43 AM
> To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Superbuild installation directory
>
> Rick,
>
> There
esday, May 29, 2013 8:43 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild installation directory
Rick,
There is always going to be a BUILD/install. This is where all the
internal packages ParaViewSuperbuild builds are temporari
; Rick Angelini
>>>
>>> USArmy Research Laboratory
>>> CISD/HPC Architectures Team
>>> Building 120 Cube 315
>>> Phone: 410-278-6266
>>>
>>>
>>> From: Utkarsh Ayachit [utkarsh.a
I'm trying to pass some MPI-related flags through the Superbuild cmake. These
flags need to get passed down to the actual Paraview source cmake, but they
don't seem to getting included. If I run ccmake I can see that the flags have
not been set - and if I manually add the flags at that time,
I want to pass a VTK build parameter from the Superbuild down into the depths
of the ParaView build. In my top level cmake command, I'm passing the flag:
-DVTK_USE_OFFSCREEN:BOOL=ON \
but if I look in the paraview/src/*build/CMakeCache.txt file I'm getting this:
VTK_USE_OFFSCREEN:BOOL=OFF
Sh
ion differences.
Utkarsh
On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. wrote:
> Hi,
>
>
>
> I’m having an issue with the ParaView Superbuild on Windows
> (VS2012). I get this error during the build process:
>
>
>
> 322> Compiling
is not able to compile a simple test program.
>
> It fails with the following output:
>
>Change Dir:
> /Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp
>
> Run Build Command:/usr/local/bin/ninja cmTryCompileExec4050157075
>
>
: Ninja -- broken
CMake Error at /Applications/CMake
2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
(message):
The C compiler "/usr/bin/cc" is not able to compile a simple test program.
It fails with the following output:
Change Dir:
/Users/2zr/build/ParaV
for working C compiler using: Ninja -- broken
> CMake Error at /Applications/CMake
> 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
> (message):
> The C compiler "/usr/bin/cc" is not able to compile a simple test program.
>
> It fails with th
king C compiler using: Ninja
>> -- Check for working C compiler using: Ninja -- broken
>> CMake Error at /Applications/CMake
>> 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
>> (message):
>> The C compiler "/usr/bin/cc" is not able to co
Compiler.cmake:61
(message):
The C compiler "/usr/bin/cc" is not able to compile a simple test program.
It fails with the following output:
Change Dir:
/Users/2zr/build/ParaView-Superbuild/paraview/src/paraview-build/CMakeFiles/CMakeTmp
Run Build Command:/usr/local/bin/n
ja -- broken
> CMake Error at /Applications/CMake
> 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
> (message):
> The C compiler "/usr/bin/cc" is not able to compile a simple test program.
>
> It fails with the following output:
>
> Change D
0:07 AM, Reuter, Michael A.
mailto:reute...@ornl.gov>> wrote:
Hi,
I’m having an issue with the ParaView Superbuild on Windows
(VS2012). I get this error during the build process:
322> Compiling Python package 'pygments'
322> Listing
C:/User
Once that's working, you can give
> VS2012 try. Hopefully, it should work (except the Python caveat), but
> I am always wary of VS version differences.
>
> Utkarsh
>
>
>
> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A.
> mailto:reute...@ornl.gov>> wrote:
&g
2008. Once that's working, you can give
>> VS2012 try. Hopefully, it should work (except the Python caveat), but
>> I am always wary of VS version differences.
>>
>> Utkarsh
>>
>>
>>
>> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A.
>>
r during CMake (2.8.12.2) generation for
>> the ParaView subproject:
>>
>> -- The C compiler identification is unknown
>> -- The CXX compiler identification is unknown
>> -- Check for working C compiler using: Ninja
>> -- Check for working C compiler
n
CMake Error at /Applications/CMake
2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61
(message):
The C compiler "/usr/bin/cc" is not able to compile a simple test program.
It fails with the following output:
Change Dir:
/Users/2zr/build/ParaView-Superbuild/para
ation for
> the ParaView subproject:
>
> -- The C compiler identification is unknown
> -- The CXX compiler identification is unknown
> -- Check for working C compiler using: Ninja
> -- Check for working C compiler using: Ninja -- broken
> CMake Error at /Applications/CMake
> 2.8-
rrently untested. As a first pass, if
>>> possible, I'd suggest using VS 2008. Once that's working, you can give
>>> VS2012 try. Hopefully, it should work (except the Python caveat), but
>>> I am always wary of VS version differences.
>>>
>>> Utkar
nl.gov><mailto:reute...@ornl.gov>> wrote:
Hi,
I’m having an issue with the ParaView Superbuild on Windows
(VS2012). I get this error during the build process:
322> Compiling Python package 'pygments'
322> Listing
C:/Users/2zr/Build/
opefully, it should work (except the Python caveat), but
> I am always wary of VS version differences.
>
> Utkarsh
>
>
>
> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. <mailto:reute...@ornl.gov><mailto:reute...@ornl.gov>> wrote:
> Hi,
>
>
>
&g
..@ornl.govreute...@ornl.gov>reute...@ornl.gov>> wrote:
Hi,
I’m having an issue with the ParaView Superbuild on Windows
(VS2012). I get this error during the build process:
322> Compiling Python package 'pygments'
322> Listing
C:
Thanks Michael. Both these changes are now merged in.
http://review.source.kitware.com/#/t/4658/
Utkarsh
On Thu, Sep 11, 2014 at 2:02 PM, Reuter, Michael A. wrote:
> The patches are attached. They aren’t much but they help get the package (on
> Windows and OSX) built without issues. The packag
Is it possible to build ParaView with the superbuild, but change a few lines of
code? I want to comment out a few warnings. These lines of source code keep
getting written over.
Thanks,
Alan
___
Powered by www.kitware.com
Visit other Kitware open
I am trying to get a debugger into a CGNS build of ParaView. CGNS builds seems
to be dying trying to link to HDF5. Has anyone else seen this? Any ideas how
to compile debug with CGNS and the Superbuild?
Here is some of the errors that I am seeing:
checking whether build environment is sane..
On Wed, Feb 15, 2017 at 13:50:13 +, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) wrote:
> I did a fresh pull of the ParaView superbuild repository, and now I can’t do
> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
>
> First, I had to remove the entries for “qt” an
> I did a fresh pull of the ParaView superbuild repository, and now I can’t do
> a clean build of PV 5.2.0 on my Mac (OSX 10.9.5).
>
> First, I had to remove the entries for “qt” and “scipy“ in the CMakeLists.txt:
..
> After removing those entries, the cmake completes and t
I have the latest OS X and qt4 and qt5 installed by brew.
I use the current superbuild, which covers PV 4.4 (why not 5.0?) but build
fails.
I use the default setting in my build and just set
CMAKE_INSTALL_PREFIX and ENABLE_paraview
make
…
-- Installing:
/Users/fwein/code/ParaViewSuperbuild/bu
Once I have finally been able to get coerce ParaView/Superbuild to actually
compile all the way through, just how do I create a "Distribution" or install
it somewhere of my choosing? I tried running ccmake and setting the
CMAKE_INSTALL_PREFIX but that didn't not effect any
Rick,
Can you try using -D arguments with the correct syntax and see if that
works?
cmake documentation states the following:
-D := = Create a cmake cache entry.
Ensure that you pass each of the -D arguments correctly with ":type"
suffix. You can identify the type for the variables by
am
Building 120 Cube 315
Phone: 410-278-6266
From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Wednesday, June 12, 2013 11:48 AM
To: Angelini, Richard C (Rick) CIV USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing comp
tran_COMPILER:FILEPATH=/opt/sgi/mpt/mpt-2.07/bin/mpif90
> > MPI_Fortran_COMPILE_FLAGS:STRING=
> > MPI_Fortran_INCLUDE_PATH:STRING=
> > MPI_Fortran_LIBRARIES:STRING=
> > MPI_Fortran_LINK_FLAGS:STRING=
> >
> >
> >
> >
> > Rick Angelini
>
); paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing compiler flags
Hi Richard,
the solution seems to be elsewhere...
The variables that get propagated to ParaView don't have necessarily the same
names. (I've listed the ones that are not using the
I'm currently pushing a fix that remove that PV_ prefix. So once it's in,
you should be good.
commit 3fb38e429260288cbb723fb198fa396e6cc2de27
Author: Sebastien Jourdain
Date: Thu Jun 13 14:59:55 2013 -0400
Remove PV_ prefix for ParaView MPI variable names
Change-Id: Ia40c16c77bbd494c4
It kind of looks like something funky is still going on with this, at least
for using the system MPI. In my superbuild cmake cache I get the following
for MPI_C_LIBRARIES:
/usr/lib/libmpich.so;/usr/lib/libopa.so;/usr/lib/libmpl.so;/usr/lib/x86_64-linux-gnu/librt.so;/usr/lib/libcr.so;/usr/lib/x86_64
0-278-6266
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Monday, June 17, 2013 3:07 PM
To: Sebastien Jourdain
Cc: Utkarsh Ayachit; Angelini, Richard C (Rick) CIV USARMY ARL (US);
paraview@paraview.org
Subject: Re: [Paraview] Superbuild: passing compiler flags
It kind of looks like
] On Behalf Of Utkarsh
Ayachit
Sent: Wednesday, September 03, 2014 10:25 AM
To: Reuter, Michael A.
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild and Windows
Michael,
Are you using VS generator? Can you switch to using Ninja? You can still use
the MSVC compilers. The error is
view-boun...@paraview.org] On Behalf Of Utkarsh
> Ayachit
> Sent: Wednesday, September 03, 2014 10:25 AM
> To: Reuter, Michael A.
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Superbuild and Windows
>
> Michael,
>
> Are you using VS generator? Can you switch to using Ninj
Classification: UNCLASSIFIED
Caveats: NONE
Thanks Utkarsh
-simon
-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Wednesday, September 03, 2014 10:48 AM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview@paraview.org
Subject: Re: [Paraview] Superbuild
Classification: UNCLASSIFIED
Caveats: NONE
Hello,
http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to
build a specific version, I will do
git clone git://paraview.org/ParaViewSuperbuild.git
cd ParaViewSuperbuild
git checkout v4.1.0
That has always worked for me for v4.1.0
On Fri, Mar 13, 2015 at 02:55:09 +, Scott, W Alan wrote:
> Is it possible to build ParaView with the superbuild, but change a few
> lines of code? I want to comment out a few warnings. These lines of
> source code keep getting written over.
You could apply a "patch"[1] (using an ExternalData
On Thu, Mar 12, 2015 at 23:18:54 -0400, Ben Boeckel wrote:
> Without looking, I can't remember the exact names of the cache
> variables, but they're something like "paraview_GIT_URL" and
> "paraview_GIT_HASH".
They are PARAVIEW_GIT_REPOSITORY and PARAVIEW_GIT_TAG (which is any git
refname, not jus
I don't follow...what do you mean by "get a debugger into a CGNS build
of ParaView"? You are getting these errors when building ParaView or
running in in a debugger?
On Fri, Mar 13, 2015 at 8:19 PM, Scott, W Alan wrote:
> I am trying to get a debugger into a CGNS build of ParaView. CGNS builds
>
Hi all,
I met a new problem with paraview-superbuild while building the paraview
binaries: building process do not find hdf5. I found a thread about this
(Paraview 5.2, on Feb 22) but it do not provide any solution.
The global cmake setup is (for hdf5):
-DENABLE_hdf5=ON
-DUSE_SYSTEM_hdf5
Hi folks,
ParaView's superbuild git repository has now been tagged with v5.4.1.
Thanks,
Cory
--
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensourc
Hi,
I'm trying to build paraview with the superbuild procedure, and with a custom
install of Qt5.
I'm calling cmake with the following options :
cmake -Dqt5_enabled=On -DUSE_SYSTEM_qt5=On(/Off)
-DQt5_DIR=/path/to/qt/5.9.1/lib/cmake/Qt5 ..
Note that, in doubt, I've also exported Qt5_DIR as
Hi there,
Has anyone successfully gotten the zlib module in the paraview
superbuild to build and install? On my machine, it is failing on
finding zlib.h; I am not sure how to interface with the Python
setup.py patch to suggest additional directories (like ZLIB_INSTALL)
to search for the
Hi all,
I’m trying to build ParaView using the super build. Everything works, except
the creation of an RPM.
When I say everything works, I mean:
* I am able to install ParaView to a location in my user directory (~Programs/)
and run ParaView from there.
* I can package a tar.gz using cpack -G
I compiled paraview 3.14 on snowleopard, with the cmake OSX variables set
to 10.5 so that the resulting binary would run on everything above leopard.
On Tue, May 1, 2012 at 1:54 PM, Michael Jackson
wrote:
> Once I have finally been able to get coerce ParaView/Superbuild to actually
> c
Paraview/Superbuild to use the Gallium llvmpipe
backend if possible. I tried modifying it versions.cmake and osmesa.cmake
to point to version Mesa 9.2.2 and use the recommended configuration
settings from the Paraview and Mesa 3D site and I must have fouled
something up since I had compilation failures
Hi Simon,
What you are doing as a workaround is indeed how production builds
should be created. The ParaView superbuild is now set up to check out
the master branch of ParaView, which varies day to day. In 4.1 and
prior to that, it was set up to check out out the release branch,
which was far
@paraview.org
Subject: Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED)
Hi Simon,
What you are doing as a workaround is indeed how production builds should be
created. The ParaView superbuild is now set up to check out the master branch
of ParaView, which varies day to day. In 4.1 and
Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
On 10/11/14, 6:04 PM, "Cory Quammen" wrote:
>Hi Simon,
>
>What you are doing as a workaround is indeed how production builds
>should be created. The ParaView superbuild is now set up to check out
>the master
__
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone: 410-278-6266
>
>
>
>
> On 10/11/14, 6:04 PM, "Cory Quammen" wrote:
>
>>Hi Simon,
>>
>>What you are doing as a workaround is indeed how prod
gt;
>>
>>
>>
>>
>>
>> __
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone: 410-278-6266
>>
>>
>>
>>
>> On 10/11/14, 6:04 PM, "Cory Quammen" wrote:
ing libraries). Then re-run the build with “GIT=OFF” , manually
>>> download the production tarball, and then re-run the build. Does this
>>> sound like the best solution?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
Tag "v4.2.0-1" is now available on the ParaView Superbuild repo.
Utkarsh
On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit
wrote:
> Doh! I see I added the tag but forgot to toggle the git/branch name,
> which for 4.1.0 I had set to be "release". I'll add a new &qu
Should you also update the Paraview SuperBuild wiki page?
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone: 410-278-6266
On 10/14/14, 8:57 AM, "Utkarsh Ayachit"
wrote:
>Tag "v4.2.0-1" is now available on
Yup :)...all set.
On Tue, Oct 14, 2014 at 9:07 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) wrote:
> Should you also update the Paraview SuperBuild wiki page?
>
>
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
); paraview@paraview.org
Subject: Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED)
Yup :)...all set.
On Tue, Oct 14, 2014 at 9:07 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US)
wrote:
> Should you also update the Paraview SuperBuild wiki p
I have a question, which is probably related to my lack of experience
with git:
https://gitlab.kitware.com/paraview/common-superbuild/blob/master/versions.cmake
contains the line
set(qt5_ver "${qt5_ver_series}.1")
However, when I follow
https://gitlab.kitware.com/paraview/paraview-
On Tue, Apr 18, 2017 at 18:15:00 +0200, Patrick Begou wrote:
> Something additionnal to set ?
This was fixed in VTK here:
https://gitlab.kitware.com/vtk/vtk/commit/641fc17e5e63f7ae5c3654f86a4ac97a33a2c63a
HDF5 can be found with targets or with library paths. The VTK module
system does not c
On Tue, Apr 18, 2017 at 13:23:36 -0400, Ben Boeckel wrote:
> We can fix this in the superbuild by setting that in `paraview.cmake`.
> I'll make that change.
https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests
Thanks Ben for this quick answer and very quick solution.
I've checked out your branch:
git fetch https://gitlab.kitware.com/ben.boeckel/paraview-superbuild.git
paraview-hdf5-no-targets
git checkout -b ben.boeckel/paraview-superbuild-paraview-hdf5-no-targets
FETCH_HEAD
and it solve
gcc (GCC) 4.8.1 and the configure command
generated by paraview-superbuild process in superbuild/osmesa/src is:
./configure --prefix=/kareline/data/begou/PARAVIEW5/build-kareline/install
--enable-opengl --disable-gles1 --disable-gles2 --disable-va --disable-xvmc
--disable-vdpau
--enable-shared-g
On Thu, Feb 08, 2018 at 15:46:27 +, Hermitte Luc (CS SI) wrote:
> I'm calling cmake with the following options?:
> cmake -Dqt5_enabled=On -DUSE_SYSTEM_qt5=On(/Off)
> -DQt5_DIR=/path/to/qt/5.9.1/lib/cmake/Qt5 ..
The input setting is `ENABLE_qt5`. The `qt5_enabled` variable indicates
whethe
I have but of course I wrote it ;-). What platform/compiler are you using?
Can you send the error messages?
On Tue, Aug 16, 2011 at 6:17 PM, Matthew Turk wrote:
> Hi there,
>
> Has anyone successfully gotten the zlib module in the paraview
> superbuild to build and install? On my
1 - 100 of 188 matches
Mail list logo
