# strange error when building paraview superbuild on Windows 10 with cmake

**URL:** https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514
**Category:** ParaView Support
**Created:** [September 3, 2018, 3:05pm UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514 "2018-09-03T15:05:18Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![quagfeng](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/q/3e96dc/32.png) [@quagfeng](https://discourse.paraview.org/u/quagfeng)
#### Post date: [September 3, 2018, 3:05pm UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/1 "2018-09-03T15:05:18Z")

</div>

Hi,

I follow the link here  
[https://gitlab.kitware.com/paraview/paraview-superbuild](https://gitlab.kitware.com/paraview/paraview-superbuild)  
to build Paraview 5.5.2 on my PC.  
Following the link it is said that

> The superbuild can be built with a Makefiles or Ninja CMake generator. The IDE generators (Xcode and Visual Studio) are not supported.

However, if I try with Makefiles/Ninja generator in cmake, it ends with a CMake 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:673 (include)  
> superbuild/CMakeLists.txt:145 (\_superbuild\_discover\_projects)

I also find the following method by using Ninja + VS 12/14 compiler( with vcvarsall.bat, see the following link) in the archives of the old mailing lists, but this method doesn’t work for me either, I still get the same error (At least Visual Studio 9.0 is required…):  
[https://markmail.org/message/cjnniaac4lt2ldy4](https://markmail.org/message/cjnniaac4lt2ldy4)

could anyone give some help?

---

<div class="post-metadata">

### Author: ![Haocheng\_Liu](https://discourse.paraview.org/user_avatar/discourse.paraview.org/haocheng_liu/32/46_2.png) [@Haocheng\_Liu](https://discourse.paraview.org/u/Haocheng_Liu)
#### Post date: [September 4, 2018, 12:46am UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/2 "2018-09-04T00:46:51Z")

</div>

> [@quagfeng](#):
>
> 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:673 (include)  
> superbuild/CMakeLists.txt:145 (\_superbuild\_discover\_projects)

It looks like CMake does not find the visual studio compiler. Did you run cmake via the visual studio interface(aka visual studio x64 win64 command prompt)? If using CMake-gui, did you specify the compiler?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 4, 2018, 7:45am UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/3 "2018-09-04T07:45:03Z")

</div>

> [@quagfeng](#):
>
> f I try with Makefiles/Ninja generator in cmake, it ends with a CMake Error

Make sure you run cmake-gui and ninja from the visual studio native command.

---

<div class="post-metadata">

### Author: ![quagfeng](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/q/3e96dc/32.png) [@quagfeng](https://discourse.paraview.org/u/quagfeng)
#### Post date: [September 4, 2018, 9:32am UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/4 "2018-09-04T09:32:42Z")

</div>

Hi Haocheng,

thank you very much for your reply!  
The Cmake-gui seems need more variables to be set, so I switched to the command line.  
I tried to run the cmake via the visual studio interface, but I still got the “At least Visual Studio 9.0 is required” error.

However, today I found out that the visual studio interface only adjusts the **path** variable and sets some other variables. Then based on the adjusted **path** , cmake finds the compiler for MinGW/Strawberry for me at first. After deleting unneeded entries in my **path** variable, the cmake can finally find the VS compiler and I get rid of this error.

But now I get a new error:

> CMake Error at superbuild/cmake/SuperbuildUtils.cmake:45 (message):  
> CMAKE\_BUILD\_TYPE must be one of: Release, RelWithDebInfo.  
> Call Stack (most recent call first):  
> superbuild/CMakeLists.txt:25 (include)

Based on this [link](https://stackoverflow.com/questions/19024259/how-to-change-the-build-type-to-release-mode-in-cmake?rq=1), I tried the following command:

> cmake --config Release -GNinja …

But I still get this “CMAKE\_BUILD\_TYPE” error. Do you know how to solve this?

---

<div class="post-metadata">

### Author: ![quagfeng](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/q/3e96dc/32.png) [@quagfeng](https://discourse.paraview.org/u/quagfeng)
#### Post date: [September 4, 2018, 9:36am UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/5 "2018-09-04T09:36:07Z")

</div>

Hi Mathieu,

thank you very much for your reply!  
The Cmake-gui seems need more variables to be set, so I switched to the command line.  
Actually, with Cmake-gui I get this error:

> CMake Error at C:/Program Files/CMake/share/cmake-3.12/Modules/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.12/Modules/Platform/Windows-MSVC.cmake:380 (enable\_language)  
> C:/Program Files/CMake/share/cmake-3.12/Modules/Platform/Windows-MSVC-C.cmake:5 (\_\_windows\_compiler\_msvc)  
> C:/Program Files/CMake/share/cmake-3.12/Modules/CMakeCInformation.cmake:48 (include)  
> CMakeLists.txt:3 (project)

> CMake Error: CMAKE\_RC\_COMPILER not set, after EnableLanguage

I tried to run the cmake via the visual studio interface, but I still got the “At least Visual Studio 9.0 is required” error.

Today I found out that the visual studio interface only adjusts the **path** variable and sets some other variables. Then based on the adjusted **path** , cmake finds the compiler for MinGW/Strawberry for me at first. After deleting unneeded entries in my **path** variable, the cmake can finally find the VS compiler and I get rid of this error.

But now I get a new error:

> CMake Error at superbuild/cmake/SuperbuildUtils.cmake:45 (message):  
> CMAKE\_BUILD\_TYPE must be one of: Release, RelWithDebInfo.  
> Call Stack (most recent call first):  
> superbuild/CMakeLists.txt:25 (include)

Based on this [link](https://stackoverflow.com/questions/19024259/how-to-change-the-build-type-to-release-mode-in-cmake?rq=1), I tried the following command:

> cmake --config Release -GNinja …

But I still get this “CMAKE\_BUILD\_TYPE” error. Do you know how to solve this?

---

<div class="post-metadata">

### Author: ![Haocheng\_Liu](https://discourse.paraview.org/user_avatar/discourse.paraview.org/haocheng_liu/32/46_2.png) [@Haocheng\_Liu](https://discourse.paraview.org/u/Haocheng_Liu)
#### Post date: [September 4, 2018, 12:11pm UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/6 "2018-09-04T12:11:24Z")

</div>

> [@quagfeng](#):
>
> cmake --config Release -GNinja …

Can you try `cmake -DCMAKE_BUILD_TYPE=Release`?

Or you can manally change the `CMAKE_BUILD_TYPE` variable in the CMakeCache.txt file.

---

<div class="post-metadata">

### Author: ![quagfeng](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/q/3e96dc/32.png) [@quagfeng](https://discourse.paraview.org/u/quagfeng)
#### Post date: [September 4, 2018, 1:25pm UTC](https://discourse.paraview.org/t/strange-error-when-building-paraview-superbuild-on-windows-10-with-cmake/514/7 "2018-09-04T13:25:48Z")

</div>

Thank you very much! Now I have built it successfully.
