[Paraview-developers] [EXTERNAL] Re: ParaView superbuild and Source

[Scott, W Alan]

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 <wascott at sandia.gov>; Chuck Atkins <chuck.atkins at kitware.com>; Ben Boeckel <ben.boeckel at kitware.com>
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 <wascott at sandia.gov<mailto:wascott at sandia.gov>> 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<mailto:shawn.waldon at kitware.com>]
Sent: Wednesday, November 30, 2016 1:13 PM
To: Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>>
Cc: paraview-developers at paraview.org<mailto: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<http://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 <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
I have set the following variables, attempting to turn off Paraview’s downloading from the paraview.org<http://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<http://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: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161201/c64033af/attachment-0001.html>