[Paraview] ParaView-Superbuild Win10 Errors

Jamil Goettlich jamil.goettlich at gmail.com
Tue Mar 27 10:37:00 EDT 2018


 Hi Shawn,

thanks a lot for the tip, configuring worked with the Visual Studio 12.0
compiler! Now I am getting a lot of build errors though.

C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning C4244:
'=' : conversion from 'double' to 'float', possible loss of data
[255/256] Linking C shared library bin\hdf5.dll
   Creating library bin\hdf5.lib and object bin\hdf5.exp
[256/256] Linking C shared library bin\hdf5_hl.dll
   Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp
ninja: build stopped: subcommand failed.

LINK : fatal error LNK1104: cannot open file 'quat\quat.lib'
[3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll
[4/97] Building CXX object client_src\CMakeFiles\vrpn_
print_messages.dir\vrpn_print_messages.C.obj
[5/97] Building CXX object client_src\CMakeFiles\ff_
client.dir\ff_client.C.obj
[6/97] Building CXX object client_src\CMakeFiles\phan_
client.dir\phan_client.C.obj
[7/97] Building CXX object client_src\CMakeFiles\
printvals.dir\printvals.C.obj
ninja: build stopped: subcommand failed.
CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43
(message):
  Failed with exit code 1

These are some examples. My it be possible that the ninja version is not
suited either? Do you know what ninja version you were building the
superbuild with?

Thanks a lot,
Jamil

(P.s. Sorry Shawn for my posting mistake)

2018-03-27 16:07 GMT+02:00 Shawn Waldon <shawn.waldon at kitware.com>:

> Hi Jamil,
>
> Please keep replies CCed to the mailing list (Reply All) so others can
> contribute to the discussion (or find answers to their own problems later
> in the archives).
>
> We use the most recent release of ninja on most of our build machines (so
> that one should work).  I'm not sure why you are getting that error
> messages from what you have included... maybe others on the list can chime
> in or you can give more details.
>
> Shawn
>
> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich <
> jamil.goettlich at gmail.com> wrote:
>
>> Hi Shawn,
>>
>> thanks a lot for the tip, configuring worked with the Visual Studio 12.0
>> compiler! Now I am getting a lot of build errors though.
>>
>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning
>> C4244: '=' : conversion from 'double' to 'float', possible loss of data
>> [255/256] Linking C shared library bin\hdf5.dll
>>    Creating library bin\hdf5.lib and object bin\hdf5.exp
>> [256/256] Linking C shared library bin\hdf5_hl.dll
>>    Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp
>> ninja: build stopped: subcommand failed.
>>
>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib'
>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll
>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri
>> nt_messages.dir\vrpn_print_messages.C.obj
>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien
>> t.dir\ff_client.C.obj
>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli
>> ent.dir\phan_client.C.obj
>> [7/97] Building CXX object client_src\CMakeFiles\printval
>> s.dir\printvals.C.obj
>> ninja: build stopped: subcommand failed.
>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43
>> (message):
>>   Failed with exit code 1
>>
>> These are some examples. My it be possible that the ninja version is not
>> suited either? Do you know what ninja version you were building the
>> superbuild with?
>>
>> Thanks a lot,
>> Jamil
>>
>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon <shawn.waldon at kitware.com>:
>>
>>> Hi Jamil,
>>>
>>> I'm not sure if this will get you all the way to a build, but here are
>>> some pointers:
>>>
>>> We build with the visual studio compiler but use the Ninja generator
>>> since it is significantly faster than VS.
>>>
>>> VS 2017 may not work.  Our binaries are built with 2013 right now and we
>>> plan to move to 2015 after the current release cycle.  If you want what you
>>> are building to be compatible with the Kitware binaries, you will need to
>>> use 2013.  Also, I believe there are compiler errors if you use 2017 right
>>> now.
>>>
>>> To build with Ninja and VS compilers, you need to be in a visual studio
>>> command prompt rather than a normal shell (it sets a bunch of environment
>>> vars, which I think is what is missing in your last example).  To convert a
>>> normal command prompt you run (example is for VS2015, your path may differ)
>>> 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64'
>>> in your shell and it will set the environment variables for you.  If you
>>> have the environment set up before running cmake -G Ninja it should just
>>> pick the right compiler.
>>>
>>> HTH,
>>>
>>> Shawn
>>>
>>> On Mon, Mar 26, 2018 at 10:59 AM, Jamil Goettlich <
>>> jamil.goettlich at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am having Problems building ParaView with ParaView-Superbuild. As
>>>> Visual Studio is not supported, I tried other build systems and compilers.
>>>> Unfortunately none of them succeeded. On the other hand I was able to build
>>>> small HelloWord programs with each of the combinations listed below and
>>>> without any errors. Here is what I did:
>>>>
>>>> First, I cloned from git:
>>>> git clone --recursive https://gitlab.kitware.com/par
>>>> aview/paraview-superbuild.git
>>>> Then cd paraview-superbuild and created new folder (build).
>>>>
>>>> The following cases did not work out (Doesnt matter if using Git Bash
>>>> or VS Command Prompt):
>>>> Build System: Ninja, Compiler: MinGW
>>>> command: cmake .. -G "Ninja"
>>>> Error:
>>>> CMake Error at superbuild/projects/win32/boost.cmake:5 (message):
>>>>   At least Visual Studio 9.0 is required
>>>> Call Stack (most recent call first):
>>>>   superbuild/cmake/SuperbuildMacros.cmake:477 (include)
>>>>   superbuild/CMakeLists.txt:145 (_superbuild_discover_projects)
>>>>
>>>> Although I have Visual Studio 15 2017 installed it does not seem to
>>>> work.
>>>>
>>>> Build System: Ninja, Compiler: MSVC compiler (cl.exe in C:\Program
>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools
>>>> \MSVC\14.12.25827\bin\Hostx64\x64)
>>>> Error:
>>>>
>>>> The C compiler
>>>> "C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools
>>>> /MSVC/14.12.25827/bin/Hostx86/x64/cl.exe"
>>>> is not able to compile a simple test program.
>>>> It fails with the following output:
>>>> Change Dir: C:/Tools/paraview-superbuild/build/CMakeFiles/CMakeTmp
>>>> Run Build Command:"nmake" "/NOLOGO" "cmTC_008b4\fast"
>>>> "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools
>>>> \MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe" -f
>>>> CMakeFiles\cmTC_008b4.dir\build.make /nologo -L
>>>> CMakeFiles\cmTC_008b4.dir\build
>>>>
>>>> Building C object CMakeFiles/cmTC_008b4.dir/testCCompiler.c.obj
>>>>
>>>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe
>>>> @C:\Users\JamiG\AppData\Local\Temp\nmD540.tmp
>>>>
>>>> testCCompiler.c
>>>>
>>>> C:\Tools\paraview-superbuild\build\CMakeFiles\CMakeTmp\testCCompiler.c:
>>>> fatal error C1001: An internal error has occurred in the compiler.
>>>>
>>>> (compiler file 'msc1.cpp', line 1507)
>>>>
>>>> To work around this problem, try simplifying or changing the program
>>>> near the locations listed above.
>>>>
>>>> Please choose the Technical Support command on the Visual C++
>>>>
>>>> Help menu, or open the Technical Support help file for more information
>>>>
>>>> Internal Compiler Error in C:\PROGRA~2\MIB055~1\2017\COMM
>>>> UN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe. You will be
>>>> prompted to send an error report to Microsoft later.
>>>>
>>>> NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COM
>>>> MUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx86\x64\cl.exe' : return code
>>>> '0x2'
>>>>
>>>> Stop.
>>>>
>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
>>>> Studio\2017\Community\VC\Tools\MSVC\14.12.25827\bin\Hostx64\x64\nmake.exe"'
>>>> : return code '0x2'
>>>>
>>>> Stop.
>>>>
>>>>
>>>> Build System: NMake, Compiler: MSVC compiler (cl.exe in C:\Program
>>>> Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools
>>>> \MSVC\14.12.25827\bin\Hostx64\x64)
>>>>
>>>> Here, cmake recognized the compiler, but it throws another error
>>>> Error:
>>>>
>>>> CMake Error at C:/Program Files/CMake/share/cmake-3.10/M
>>>> odules/CMakeDetermineRCCompiler.cmake:20 (message):
>>>> Could not find compiler set in environment variable RC:
>>>> rc.
>>>> Call Stack (most recent call first):
>>>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC.cmake:323
>>>> (enable_language)
>>>> C:/Program Files/CMake/share/cmake-3.10/Modules/Platform/Windows-MSVC-C.cmake:5
>>>> (__windows_compiler_msvc)
>>>> C:/Program Files/CMake/share/cmake-3.10/Modules/CMakeCInformation.cmake:48
>>>> (include)
>>>> CMakeLists.txt:3 (project)
>>>>
>>>> CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage
>>>>
>>>>
>>>> I am out of ideas now.
>>>> I would be really happy for a detailed build description as I am sure I
>>>> did not understand something properly.
>>>>
>>>> And every hint on how to resolve on of those errors is very welcome too.
>>>>
>>>>
>>>> Thanks in advance!
>>>>
>>>>
>>>> _______________________________________________
>>>> 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:
>>>> https://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180327/0ab6e626/attachment.html>


More information about the ParaView mailing list