[Paraview] [Non-DoD Source] Re: Superbuild repo change?

Wed Feb 22 08:10:04 EST 2017

Cory - so I did a “git pull” and “git submodule update” in my existing
paraview-superbuild repository directory and that 5.3.0-RC1 information
was not in the versions.cmake file.     I did a clean “git clone” and I
then received the correct files.        I’m not a git expert - so I’m not
sure why I had to do a clean “git clone”.   I thought I “git pull” should
have done a proper update.      I must be missing something with my
repository update commands …..

_______________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

-----Original Message-----
From: Cory Quammen <cory.quammen at kitware.com>
Date: Tuesday, February 21, 2017 at 1:36 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: "ben.boeckel at kitware.com" <ben.boeckel at kitware.com>, ParaView
<paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?

Rick,

What is the SHA-1 for last commit in your paraview-superbuild
directory? The latest commit on master is
22e4b36087b523e01994b90f7b1c5eabb6c0755b. In the file versions.cmake
at line 63, 5.3.0-RC1 should be listed as a version option.

Thanks,
Cory

On Tue, Feb 21, 2017 at 11:31 AM, Angelini, Richard C (Rick) CIV
USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> I did a “git pull” and “git submodule update” in the paraview-superbuild
> directory.   I then changed the source flag in my cmake command:
>
> -Dparaview_SOURCE_SELECTION="5.3.0-RC1”
>
> and I get this error when doing a clean build.
>
> -- Detecting CXX compile features - done
> -- Check size of void*
> -- Check size of void* - done
> CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:338
> (message):
>   The 5.3.0-RC1 source selection for paraview does not exist.
> Call Stack (most recent call first):
>   versions.cmake:62 (superbuild_set_selectable_source)
>   superbuild/CMakeLists.txt:96 (include)
>
>
> I grepp’ed through the paraview-superbuild directory and I don’t see any
> references to 5.3.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Cory Quammen <cory.quammen at kitware.com>
> Date: Tuesday, February 21, 2017 at 10:07 AM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: "ben.boeckel at kitware.com" <ben.boeckel at kitware.com>, ParaView
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
>
> All active links contained in this email were disabled.  Please verify
>the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to
>a
> Web browser.
>
>
>
>
> ----
>
> Hi Rick,
>
> From paraview-superbuild master (remember to run 'git submodule
> update' after updating master), you should be able to set
> paraview_SOURCE_SELECTION to 5.3.0-RC1. Then just configure and build.
>
> These directions are distilled from the README.md file in the
> superbuild directory [1]. Relevant excerpt:
>
> "3. Another option is to use a source tarball of a ParaView release.
> For that, set paraview_SOURCE_SELECTION to the version to build such
> as 5.2.0. The superbuild offers the lastest stable release as well as
> release candidate in preparation for the release. This is the best way
> to build a released version of ParaView."
>
> For each release candidate and release, we add an entry under
> paraview_SOURCE_SELECTION that you can select.
>
> Let us know if you run into problems.
>
> Thanks,
> Cory
>
> [1]
> 
>Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/maste
>r
> /README.md
>
> On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> What are the instructions for using PVSB to build the 5.3- RC ?
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Ben Boeckel <ben.boeckel at kitware.com>
>> Reply-To: "ben.boeckel at kitware.com" <ben.boeckel at kitware.com>
>> Date: Wednesday, February 15, 2017 at 11:34 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change?
>>
>> On Wed, Feb 15, 2017 at 13:50:13 +0000, 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” and “scipy" in the
>>> CMakeLists.txt:
>>
>> You need to run `git submodule update` to update the common-superbuild
>> bits.
>>
>>> After removing those entries, the cmake completes and the build starts
>>>and
>>> passes out in qt4.
>>> I’m not sure why it’s complaining about OS X 10.7 or later?)
>>
>> What version of Xcode are you using?
>>
>> --Ben
>>
>> _______________________________________________
>> Powered by Caution-www.kitware.com
>>
>> Visit other Kitware open-source projects at
>>Caution-http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>>Caution-http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at:
>>Caution-http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> Caution-http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170222/7404dfb5/attachment.bin>