[Paraview-developers] [Non-DoD Source] Re: windows 10 superbuild VS2013 requirement (UNCLASSIFIED)
David E DeMarle
dave.demarle at kitware.com
Wed Jun 7 11:37:15 EDT 2017
Likely that the compiler check is happening before the flag to disable the
subproject is setup.
Would you mind removing the check (projects/win32/ispc.cmake) and telling
me if condifuration continues?
David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Wed, Jun 7, 2017 at 10:46 AM, Su, Simon M CIV USARMY RDECOM ARL (US) <
simon.m.su.civ at mail.mil> wrote:
> CLASSIFICATION: UNCLASSIFIED
>
> thank you David. It is on a clean build. I am equally puzzled.
>
> thanks
> -simon
>
> -----Original Message-----
> From: David E DeMarle [mailto:dave.demarle at kitware.com]
> Sent: Wednesday, June 07, 2017 10:11 AM
> To: Su, Simon M CIV USARMY RDECOM ARL (US) <simon.m.su.civ at mail.mil>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] windows 10
> superbuild
> VS2013 requirement (UNCLASSIFIED)
>
> 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.
>
>
> ________________________________
>
>
>
> I don't know why your command to turn off the ispc subproject isn't being
> respected then.
>
> Is c:\Users\one\build\pvsb-5.4\build initially empty or does it still
> have the
> contents of a previous build?
>
> I would expect the above to work fine in a clean build.
>
>
> With a partial or old build, editing cmakecache (via cmake-gui or command
> line) to turn of ispc and configuring should also work.
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Wed, Jun 7, 2017 at 9:59 AM, Su, Simon M CIV USARMY RDECOM ARL (US)
> <simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil > >
> wrote:
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Thank you David. But I think I also needed something else....
> Please see
> below.
>
> thanks
> -simon
>
>
> c:\Users\one\build\pvsb-5.4\build>cmake -G
> Ninja -DCMAKE_INSTALL_PREFIX=ParaView-5.4.0
> -DCMAKE_BUILD_TYPE=Release -DENABLE_mpi:BOOL=ON
> -DENABLE_python:BOOL=ON -DENABLE_paraview:BOOL=ON
> -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF
> -DENABLE_embree:BOOL=OFF -DENABLE_qt4:BOOL=OFF
> -DENABLE_qt5:BOOL=ON -DENABLE_cxx11:BOOL=ON
> -DENABLE_bzip2:BOOL=ON -DENABLE_png:BOOL=ON
> -DENABLE_numpy:BOOL=ON -DENABLE_paraviewtutorial:BOOL=ON
> -DENABLE_paraviewtutorialdata:BOOL=ON
> -DENABLE_paraviewusersguide:BOOL=ON -DENABLE_paraviewweb:BOOL=ON
> -DENABLE_paraviewweblightviz:BOOL=ON -DENABLE_
> paraviewwebvisualizer:BOOL=ON
> -DENABLE_visitbridge:BOOL=ON
> -DENABLE_vrpn:BOOL=ON ..\paraview-superbuild
>
> -- The C compiler identification is MSVC 19.0.24215.1
>
> -- The CXX compiler identification is MSVC 19.0.24215.1
>
> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
> Visual
> Studio 14.0/VC/bin/amd64/cl.exe
>
> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
> Visual
> Studio 14.0/VC/bin/amd64/cl.exe -- works
>
> -- Detecting C compiler ABI info
>
> -- Detecting C compiler ABI info - done
>
> -- Check for working CXX compiler: C:/Program Files
> (x86)/Microsoft Visual
> Studio 14.0/VC/bin/amd64/cl.exe
>
> -- Check for working CXX compiler: C:/Program Files
> (x86)/Microsoft Visual
> Studio 14.0/VC/bin/amd64/cl.exe -- works
>
> -- Detecting CXX compiler ABI info
>
> -- Detecting CXX compiler ABI info - done
>
> -- Detecting CXX compile features
>
> -- Detecting CXX compile features - done
>
> -- Check size of void*
>
> -- Check size of void* - done
>
> -- Found Git: C:/Program Files/Git/cmd/git.exe (found version
> "2.10.2.windows.1")
>
> -- Determined source version for paraview: 5.4.0
>
> CMake Error at projects/win32/ispc.cmake:2 (message):
>
> The ispc project requires Visual Studio 2013.
>
> Call Stack (most recent call first):
>
> superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>
> superbuild/CMakeLists.txt:113 (_superbuild_discover_projects)
>
>
>
>
>
>
>
> -- Configuring incomplete, errors occurred!
>
> See also "C:/Users/one/build/pvsb-5.4/
> build/CMakeFiles/CMakeOutput.log".
>
>
>
>
>
> -----Original Message-----
> From: David E DeMarle [Caution-mailto:dave.demarle at kitware.com <
> Caution-mailto:dave.demarle at kitware.com > ]
> Sent: Wednesday, June 07, 2017 8:47 AM
> To: Su, Simon M CIV USARMY RDECOM ARL (US) <
> simon.m.su.civ at mail.mil <
> Caution-mailto:simon.m.su.civ at mail.mil > >
> Cc: ParaView Developers <paraview-developers at paraview.org <
> Caution-mailto:paraview-developers at paraview.org > >
> Subject: [Non-DoD Source] Re: [Paraview-developers] windows 10
> superbuild
> VS2013 requirement (UNCLASSIFIED)
>
> 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.
>
>
> ________________________________
>
>
>
> Turn off embree as well.
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909 < tel:518-881-4909 >
>
> On Wed, Jun 7, 2017 at 8:23 AM, Su, Simon M CIV USARMY RDECOM ARL
> (US)
> <simon.m.su.civ at mail.mil < Caution-mailto:simon.m.su.civ at mail.mil
> > <
> Caution-Caution-mailto:simon.m.su.civ at mail.mil <
> Caution-mailto:simon.m.su.civ at mail.mil > > > wrote:
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Hello,
>
> On Windows 10 64bit, when I tried to use VS 2015 community
> for my
> ParaView
> superbuild build, the cmake is complaining ospray requires
> VS2013
> even when
> I have the following set
>
> -DENABLE_ospray:BOOL=OFF -DENABLE_ispc:BOOL=OFF
>
> Is there a way to use VS2015 community compiler to build
> ParaView
> superbuild?
>
> thank you much
> -simon
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> _______________________________________________
> Powered by Caution-Caution-www.kitware.com <
> Caution-http://Caution-Caution-www.kitware.com > <
> Caution-Caution-http://www.kitware.com < Caution-http://www.kitware.com
> > >
>
> Visit other Kitware open-source projects at
> Caution-Caution-http://www.kitware.com/opensource/opensource.html
> <
> Caution-http://www.kitware.com/opensource/opensource.html > <
> Caution-Caution-http://www.kitware.com/opensource/opensource.html
> <
> Caution-http://www.kitware.com/opensource/opensource.html > >
>
> Search the list archives at:
> Caution-Caution-http://markmail.org/search/?q=Paraview-developers
> <
> Caution-http://markmail.org/search/?q=Paraview-developers > <
> Caution-Caution-http://markmail.org/search/?q=Paraview-developers
> <
> Caution-http://markmail.org/search/?q=Paraview-developers > >
>
> Follow this link to subscribe/unsubscribe:
> Caution-Caution-http://public.
> kitware.com/mailman/listinfo/paraview-developers
> < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
> > <
> Caution-Caution-http://public.kitware.com/mailman/listinfo/
> paraview-developers
> < Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
> > >
>
>
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
>
>
>
> CLASSIFICATION: UNCLASSIFIED
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170607/5f694e5e/attachment.html>
More information about the Paraview-developers
mailing list