Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
“git pull” and “git submodule update” seem to have worked for 5.3.0-RC2. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Wednesday, February 22, 2017 at 9:04 AM To: Rick Angelini Cc: Cory Quammen , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > 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 ….. What is the output of the following commands: - git config branch.master.remote - git remote show $output_from_previous_command - git remote show origin --Ben smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
On Wed, Feb 22, 2017 at 13:10:04 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > 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 ….. What is the output of the following commands: - git config branch.master.remote - git remote show $output_from_previous_command - git remote show origin --Ben ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Rick, Interesting. I would think that should have worked, assuming you are on the 'master' branch, and my local testing suggests it would. What I usually do these days to be be more explicit in my git updates is: git checkout master git fetch origin git merge origin/master 'git pull' does essentially the last two if you are on the 'master' branch. If you are on another branch, FETCH_HEAD may already point to the tip of the remote branch, and so there may be nothing to merge. In any case, a fresh 'git clone' is sure to work, though as you say, you really shouldn't have to. Thanks for testing the release candidate. Best, Cory On Wed, Feb 22, 2017 at 8:10 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > 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 > Date: Tuesday, February 21, 2017 at 1:36 PM > To: Rick Angelini > Cc: "ben.boec...@kitware.com" , ParaView > > 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) 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 >> Date: Tuesday, February 21, 2017 at 10:07 AM >> To: Rick Angelini >> Cc: "ben.boec...@kitware.com" , ParaView >> >> 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/m
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
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 Date: Tuesday, February 21, 2017 at 1:36 PM To: Rick Angelini Cc: "ben.boec...@kitware.com" , ParaView 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) 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 > Date: Tuesday, February 21, 2017 at 10:07 AM > To: Rick Angelini > Cc: "ben.boec...@kitware.com" , ParaView > > 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) 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 >> Reply-To: "ben.boec...@kitware.com" >> Date: Wednesday, February 15, 2017 at 11:34 AM >> To: Rick Angelini >> Cc: ParaView >> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? >> >> 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” and “scipy" in the >>> CMakeLists.txt: >> >> You need to run `git submodule update` to update the common-superbuild >> bits. >> >>> After removing
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) 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 > Date: Tuesday, February 21, 2017 at 10:07 AM > To: Rick Angelini > Cc: "ben.boec...@kitware.com" , ParaView > > 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/master > /README.md > > On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY > RDECOM ARL (US) 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 >> Reply-To: "ben.boec...@kitware.com" >> Date: Wednesday, February 15, 2017 at 11:34 AM >> To: Rick Angelini >> Cc: ParaView >> Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? >> >> 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” 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. ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
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 Date: Tuesday, February 21, 2017 at 10:07 AM To: Rick Angelini Cc: "ben.boec...@kitware.com" , ParaView 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/master /README.md On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 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 > Reply-To: "ben.boec...@kitware.com" > Date: Wednesday, February 15, 2017 at 11:34 AM > To: Rick Angelini > Cc: ParaView > Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > > 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” 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. smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
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] https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md On Tue, Feb 21, 2017 at 8:42 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 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 > Reply-To: "ben.boec...@kitware.com" > Date: Wednesday, February 15, 2017 at 11:34 AM > To: Rick Angelini > Cc: ParaView > Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > > 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” 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 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 > -- 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 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
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 Reply-To: "ben.boec...@kitware.com" Date: Wednesday, February 15, 2017 at 11:34 AM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? 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” 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 smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Ben/Fabian I just did another quick test and it looks like the PVSB 5.2 build on my OS X 10.9 system that this flag was required to get the build to work: -DCMAKE_OSX_SDK="macosx10.9” and this one was apparently optional and not required: -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M acOSX.platform/Developer/SDKs/MacOSX10.9.sdk” Thanks for your help. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Friday, February 17, 2017 at 7:57 AM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set … > I’m not sure if I needed to set both variables, but I recalled seeing >this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
On Fri, Feb 17, 2017 at 12:43:17 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Cmake was complaining about CMAKE_OSX_SDK not being set … > I’m not sure if I needed to set both variables, but I recalled seeing this > in a mail thread, so I just set it! 8-) Ah, then you just set it to what you had. That's fine :) . I just saw "10.9" and assumed you were setting it to an older version. --Ben ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Cmake was complaining about CMAKE_OSX_SDK not being set … I’m not sure if I needed to set both variables, but I recalled seeing this in a mail thread, so I just set it! 8-) Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Thursday, February 16, 2017 at 4:00 PM To: Rick Angelini Cc: Fabian Wein , ParaView Subject: Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change? On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE command: > > -DCMAKE_OSX_SDK="macosx10.9" \ > >-DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/ >M > acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" That shouldn't be necessary for Qt5 (though if it works, that's great). --Ben smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
On Thu, Feb 16, 2017 at 16:53:55 +, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) wrote: > Fabian - thank you - that was enough of a hint to get me over the hump. > Switched my build to qt5 AND based on some information from a previous > email thread, I added the following to my CMAKE command: > > -DCMAKE_OSX_SDK="macosx10.9" \ > -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M > acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" That shouldn't be necessary for Qt5 (though if it works, that's great). --Ben ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Fabian - thank you - that was enough of a hint to get me over the hump. Switched my build to qt5 AND based on some information from a previous email thread, I added the following to my CMAKE command: -DCMAKE_OSX_SDK="macosx10.9" \ -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/M acOSX.platform/Developer/SDKs/MacOSX10.9.sdk" Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Fabian Wein Date: Wednesday, February 15, 2017 at 4:58 PM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? > 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 the build starts >and passes out in qt4. > I’m not sure why it’s complaining about OS X 10.7 or later?) For recent OS X qt4 is known to not compile. Use qt5 and it works (macOS 10.12) Fabian smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: [Paraview] [Non-DoD Source] Re: Superbuild repo change?
Duh. “git submodule update” seems to fix things related to the qt and scipy issue. My Mac has Xcode version 6.2 Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Ben Boeckel Reply-To: "ben.boec...@kitware.com" Date: Wednesday, February 15, 2017 at 11:34 AM To: Rick Angelini Cc: ParaView Subject: [Non-DoD Source] Re: [Paraview] Superbuild repo change? 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” 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 smime.p7s Description: S/MIME cryptographic signature ___ 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