I used a system Python which is pointed at a Python we distribute with Mantid on Windows. BTW, do you want me to pass along the patches I have for the USE_SYSTEM_matplotlib issues I run into, or should I just handle those in a Superbuild fork?
Thanks, M On Sep 11, 2014, at 1:21 AM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>> wrote: Michael, with VS2012, what was your selection for Python? Were you using system Python or did you let the superbuild build its own? Utkarsh On Fri, Sep 5, 2014 at 4:58 PM, Reuter, Michael A. <reute...@ornl.gov<mailto:reute...@ornl.gov>> wrote: I’m working with VS2012. Thanks for the update on Mavericks. M On Sep 5, 2014, at 4:32 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com>> wrote: Great! Which VS was this? The Pygments thing should be tracked down. I'll see what's happening there. BTW, I am making progress on Mavericks build. I think I have most things ironed out. I'll send an updated email once I have dashboard testing it. Utkarsh On Fri, Sep 5, 2014 at 4:29 PM, Reuter, Michael A. <reute...@ornl.gov<mailto:reute...@ornl.gov>> wrote: I switched to Ninja and shortened up the paths, but what really got things working was passing the VTK_USE_SYSTEM_PYGMENTS down to the ParaView CMake config via the PV_EXTRA_CMAKE_ARGS. After that, the build went smoothly. I hit a snag on creating the package because I’m triggering the USE_SYSTEM_matplotlib option and the Projects/win32/paraview.bundle.cmake does not trap the copying of matplotlib related items when this flag is used. I see a similar issue in the Projects/apple/paraview.bundle.cmake file as well. I added a AND NOT USE_SYSTEM_matplotlib to the if (matplotlib_ENABLED) line and that fixed the generated cmake_install.cmake file and the package created fine. I’ve tested the resulting package and so far so good. M On Sep 3, 2014, at 10:24 AM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com<mailto:utkarsh.ayac...@kitware.com><mailto:utkarsh.ayac...@kitware.com>> wrote: 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. <reute...@ornl.gov<mailto:reute...@ornl.gov><mailto:reute...@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/lib/site-packages/pygments ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\filters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\formatters ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/site-packages/pygments\lexers ... 322> Listing C:/Users/2zr/Build/ParaView-Superbuild/paraview/src/paraview-build/lib/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: reute...@ornl.gov<mailto:reute...@ornl.gov><mailto:reute...@ornl.gov> _______________________________________________ Powered by www.kitware.com<http://www.kitware.com><http://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
