[Paraview] Superbuild and Windows (UNCLASSIFIED)

Wed Sep 3 10:51:19 EDT 2014

Classification: UNCLASSIFIED
Caveats: NONE

Thanks Utkarsh
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Wednesday, September 03, 2014 10:48 AM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] Superbuild and Windows (UNCLASSIFIED)

Yes, Ninja is indeed the preferred and the only tested generators for ParaView's Windows superbuild for all VS variants.

Yes, that's indeed the Ninja. When using CMake, you just need to pick the Ninja generator. For all intents and purposes it;s like nmake. So you'll need to run CMake through the visual studio command prompt (also the builds need to be triggered throught the command prompt) otherwise you'll get compiler not working errors.

Utkarsh

On Wed, Sep 3, 2014 at 10:41 AM, Su, Simon M CTR USARMY ARL (US) <simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Utkarsh,
>
> Is Ninja also preferred if I am using VS2008 to build the superbuild on Windows?
>
> Is this the Ninja - http://martine.github.io/ninja/manual.html ?
>
> Thanks
> -simon
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of 
> Utkarsh Ayachit
> Sent: Wednesday, September 03, 2014 10:25 AM
> To: Reuter, Michael A.
> Cc: paraview at 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 popping up when the build is trying to compiler the pygments *.py files. You'll get the same error later when it's trying to compile the ParaView *.py files.
>
> Also, another thing to note is that Windows has issues with long paths. So I'd suggest moving the superbuild source and build directories to something lower to avoid those e.g. C:/tmp/pvs-src and C:/tmp/pvs-build.
>
> Finally, if you're using VS2012, you'll need to use a system Python.
> Currently. the Python included in the superbuild is intended for 
> VS2008. Also VS2012, is currently 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.
>
> Utkarsh
>
>
>
> On Wed, Sep 3, 2014 at 10:07 AM, Reuter, Michael A. <reuterma at 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/ParaView-Superbuild/paraview/src/paraview-build/li
>> b
>> /site-packages/pygments
>> ...
>>
>>
>>
>>          322>  Listing
>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li
>> b
>> /site-packages/pygments\filters
>> ...
>>
>>
>>
>>          322>  Listing
>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li
>> b
>> /site-packages/pygments\formatters
>> ...
>>
>>
>>
>>          322>  Listing
>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li
>> b
>> /site-packages/pygments\lexers
>> ...
>>
>>
>>
>>          322>  Listing
>> C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/li
>> b
>> /site-packages/pygments\styles
>> ...
>>
>>
>>
>>          322>  ImportError: No module named site
>>
>>
>>
>>      9>C:\Program Files
>> (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5):
>> error MSB6006: "cmd.exe" exited with code 1.
>> [C:\Users\2zr\Build\ParaView-Superbuild\paraview.vcxproj]
>>
>>
>>
>>          322>
>>
>>          322>Build FAILED.
>>
>>
>>
>> However, the site module exists when I run python. I’m building from 
>> a script so I can control the environment. Everything else seems to 
>> build just fine. However, nothing appears in the install directory 
>> for cpack to find. I can’t tell if this build error is disrupting the 
>> process or something else is going wrong. What controls the pygments 
>> build so I can shut it off for now?
>>
>>
>>
>> Thanks,
>>
>> M
>>
>>
>>
>> Dr. Michael Reuter
>>
>> Scientific Data Analysis Group
>>
>> Neutron Data Analysis and Visualization Division
>>
>> Oak Ridge National Laboratory
>>
>>
>>
>> Office: 1-865-241-7216
>>
>> Fax: 1-865-574-6080
>>
>> Email: reuterma at ornl.gov
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
> _______________________________________________
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

Classification: UNCLASSIFIED
Caveats: NONE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140903/5af5235a/attachment.bin>