Recent changes to BuildWindowsVS2012

BuildWindowsVS2012 modified by vISTe

vISTe — Wed, 05 Feb 2014 23:36:36 -0000

--- v42
+++ v43
@@ -25,7 +25,7 @@
 - Go to Start > All Programs > Microsoft Visual Studio 2012 > Visual Studio Tools > VS2012 x64 Cross Tools Command Prompt. All build operations will now be done in 64-bit mode.
 - In the DOS window type 'cd C:\\QtLibs\\4.8.2-x64'.
 - Use command 'configure.exe -debug-and-release' for configuration. (if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win32-msvc2010. If your Qt is 4.8.4 this argument may be win32-msvc2012 ). Answer to questions asked by configuration tool by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
-- When the preparation is finished, type 'nmake' to start the 64-bit build of Qt. This may take a very long time, i.e., several hours. It's best to start this process at the end of the day. When you come back the next day everything should be ready.
+- When the preparation is finished, type 'nmake' to start the 64-bit build of Qt. This may take a very long time, i.e., several hours. It's best to start this process at the end of the day. When you come back the next day everything should be ready. In case of HashSet.h error like (wtf/HashSet.h(180) : error C2664: 'std::pair<_Ty1,_Ty2>::pair...) use the patch here: . 
 - When the build has finished add the directory C:\\QtLibs\\4.8.2-x64\\bin to the system environment variable PATH and the directory C:\\QtLibs\\4.8.2-x64 as the QTDIR system variable (create it if it does not exist).

 Build VTK for 64-bit

BuildWindowsVS2012 modified by vISTe

vISTe — Mon, 03 Feb 2014 21:19:32 -0000

--- v41
+++ v42
@@ -40,6 +40,7 @@
 -Then press F7 to build the source. (Debug or/and Release). 
 - You will get an error on "make_pair (var1,var2)" constructions that are not allowed anymore in VS2012. You should replace them by "make_pair(var1,var2)" in (vtkMapArrayValue)
 - You will also get an error in file vtkAdjacencyMatrixToEdgeTable.cxx. In order solve it you need to add "#include  ". 
+- If your VTK is 5.10 and compile mod is Debug there is an error at vtkqtchart files about vtkMath::IsNan. Please try release mode because VTKQtCharts is deprecated at 5.10 and will be removed in 6.0.
 - Everything should build fine from there.
 - When the build has finished add the directory C:\\VTKLibs\\5.8.0-x64\\bin\\Debug (or Release) to the system PATH. When you are running vIST/e you should make sure that the right directory(Debug/Release) is being referred to. This is necessary for finding dlls at runtime. Do not install VTK to the system because VTK_DIR is going to be set in cmake-gui settings of vIST/e. If you want to test vIST/e  both in release and debug mode, compile VTK in both modes successively, it will create Debug and Release automaticly under C:\\VTKLibs\\5.8.0-x64\\bin as described above. You can also add both paths to the system PATH environment variable.

BuildWindowsVS2012 modified by vISTe

vISTe — Tue, 29 Oct 2013 15:36:30 -0000

--- v40
+++ v41
@@ -24,7 +24,7 @@
 - Download Qt source code at  and unpack it to directory C:\\QtLibs and rename the directory 'qt-everywhere-opensource-src-4.8.2' to '4.8.2-x64'.
 - Go to Start > All Programs > Microsoft Visual Studio 2012 > Visual Studio Tools > VS2012 x64 Cross Tools Command Prompt. All build operations will now be done in 64-bit mode.
 - In the DOS window type 'cd C:\\QtLibs\\4.8.2-x64'.
-- Type 'configure.exe -debug-and-release'(if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win32-msvc2010. If your Qt is 4.8.4 this argument may be win32-msvc2012 ). Answer questions by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
+- Use command 'configure.exe -debug-and-release' for configuration. (if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win32-msvc2010. If your Qt is 4.8.4 this argument may be win32-msvc2012 ). Answer to questions asked by configuration tool by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
 - When the preparation is finished, type 'nmake' to start the 64-bit build of Qt. This may take a very long time, i.e., several hours. It's best to start this process at the end of the day. When you come back the next day everything should be ready.
 - When the build has finished add the directory C:\\QtLibs\\4.8.2-x64\\bin to the system environment variable PATH and the directory C:\\QtLibs\\4.8.2-x64 as the QTDIR system variable (create it if it does not exist).

BuildWindowsVS2012 modified by vISTe

vISTe — Thu, 30 May 2013 11:38:32 -0000

--- v39
+++ v40
@@ -70,7 +70,7 @@
 - If building ends without any error the dlls can be found in ..\\YourBuildDirectory\\tool\\bin\Release (or  Debug).
 - To launch vIST/e from Visual Studio, right-click the **vIST/e** project and select **Set as Startup Project**. Then press **F5** to start vIST/e if you compiled in Debug mode else use **Ctrl-F5**.
 - - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode in VS2012 for compiling. While doing this, make sure that if you try viste in release mode, your path has  ${VTK_DIR}\bin\Release before the  ${VTK_DIR}\bin\Debug.
--Similarly If viste is prepared in Release mode and compiled and run in debug mode "'vISTe.exe' (Win32): Loaded 'C:\Windows\System32\guard64.dll'. Cannot find or open the PDB file." error may occur. Solution is same, run cmake-gui again and compile and run viste in that mode. 
+-Similarly If viste is prepared in Release mode and compiled and run in debug mode "'vISTe.exe' (Win32): Loaded 'C:\Windows\System32\guard64.dll'. Cannot find or open the PDB file." error may occur. Close and rerun Visual Studio. If this does not work solution is the same as above, run cmake-gui again and compile and run viste in that mode. 
 - At first startup, vIST/e may produce some messages, e.g., about a missing settings.xml (which it will create), but also about certain files being invalid Qt plugins. This is caused by the fact that the build directory where vISTe.exe is located also contains non-DLL files which the plugin loader tries to load. This fails of course and vIST/e shows an error. The best thing to do is to hold down the 'Enter' button to quickly run through all error messages until the tool itself starts. The next you start vIST/e this will not happen anymore.

 - It might be the shaders are not found. Move the shaders directory where vISTe.exe is located

BuildWindowsVS2012 modified by vISTe

vISTe — Wed, 22 May 2013 14:05:11 -0000

--- v38
+++ v39
@@ -24,7 +24,7 @@
 - Download Qt source code at  and unpack it to directory C:\\QtLibs and rename the directory 'qt-everywhere-opensource-src-4.8.2' to '4.8.2-x64'.
 - Go to Start > All Programs > Microsoft Visual Studio 2012 > Visual Studio Tools > VS2012 x64 Cross Tools Command Prompt. All build operations will now be done in 64-bit mode.
 - In the DOS window type 'cd C:\\QtLibs\\4.8.2-x64'.
-- Type 'configure.exe -debug-and-release'(if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win64-msvc2012). Answer questions by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
+- Type 'configure.exe -debug-and-release'(if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win32-msvc2010. If your Qt is 4.8.4 this argument may be win32-msvc2012 ). Answer questions by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
 - When the preparation is finished, type 'nmake' to start the 64-bit build of Qt. This may take a very long time, i.e., several hours. It's best to start this process at the end of the day. When you come back the next day everything should be ready.
 - When the build has finished add the directory C:\\QtLibs\\4.8.2-x64\\bin to the system environment variable PATH and the directory C:\\QtLibs\\4.8.2-x64 as the QTDIR system variable (create it if it does not exist).

BuildWindowsVS2012 modified by vISTe

vISTe — Tue, 21 May 2013 15:55:51 -0000

--- v37
+++ v38
@@ -24,7 +24,7 @@
 - Download Qt source code at  and unpack it to directory C:\\QtLibs and rename the directory 'qt-everywhere-opensource-src-4.8.2' to '4.8.2-x64'.
 - Go to Start > All Programs > Microsoft Visual Studio 2012 > Visual Studio Tools > VS2012 x64 Cross Tools Command Prompt. All build operations will now be done in 64-bit mode.
 - In the DOS window type 'cd C:\\QtLibs\\4.8.2-x64'.
-- Type 'configure.exe -debug-and-release'(it might be necessary for you to use the option -platform win64-msvc2010). Answer questions by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
+- Type 'configure.exe -debug-and-release'(if there are more than one compilers already loaded, it might be necessary for you to use the option -platform win64-msvc2012). Answer questions by selecting Open Source and Yes options. Configure.exe will prepare the Qt build for 64-bit platforms, generating both debug and release libraries. This may take a while.
 - When the preparation is finished, type 'nmake' to start the 64-bit build of Qt. This may take a very long time, i.e., several hours. It's best to start this process at the end of the day. When you come back the next day everything should be ready.
 - When the build has finished add the directory C:\\QtLibs\\4.8.2-x64\\bin to the system environment variable PATH and the directory C:\\QtLibs\\4.8.2-x64 as the QTDIR system variable (create it if it does not exist).

BuildWindowsVS2012 modified by vISTe

vISTe — Tue, 14 May 2013 12:39:27 -0000

--- v36
+++ v37
@@ -69,7 +69,7 @@
 - Open the solution file **Project.sln** and make sure the configuration is set to the platform 'x64' and compile mode displayed in combo box in the middle of the main window is the same with what you selected while compiling VTK and while the cmake-gui configuration of vIST/e. Then press **F7** to build all project modules. You may get some errors because it is missing the linking library to 'opengl32.lib'. You need to add the library to the "RightClick>Properties MenuItem>Configuration Properties>Linker>Input>Additional dependencies' field of  plugin projects GPUGlyphPlugin, RayCastPlugin, FiberVisualisationPlugin in Solution Explorer window. Adding opengl32.lib to each of their configurations should remove the linking issues. Note that 3 plugins can be selected together before the Right-Click, rather than selecting projects one by one and setting their link dependencies. 
 - If building ends without any error the dlls can be found in ..\\YourBuildDirectory\\tool\\bin\Release (or  Debug).
 - To launch vIST/e from Visual Studio, right-click the **vIST/e** project and select **Set as Startup Project**. Then press **F5** to start vIST/e if you compiled in Debug mode else use **Ctrl-F5**.
-- - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode in VS2012 for compiling.
+- - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode in VS2012 for compiling. While doing this, make sure that if you try viste in release mode, your path has  ${VTK_DIR}\bin\Release before the  ${VTK_DIR}\bin\Debug.
 -Similarly If viste is prepared in Release mode and compiled and run in debug mode "'vISTe.exe' (Win32): Loaded 'C:\Windows\System32\guard64.dll'. Cannot find or open the PDB file." error may occur. Solution is same, run cmake-gui again and compile and run viste in that mode. 
 - At first startup, vIST/e may produce some messages, e.g., about a missing settings.xml (which it will create), but also about certain files being invalid Qt plugins. This is caused by the fact that the build directory where vISTe.exe is located also contains non-DLL files which the plugin loader tries to load. This fails of course and vIST/e shows an error. The best thing to do is to hold down the 'Enter' button to quickly run through all error messages until the tool itself starts. The next you start vIST/e this will not happen anymore.

BuildWindowsVS2012 modified by vISTe

vISTe — Fri, 26 Apr 2013 11:16:00 -0000

--- v35
+++ v36
@@ -69,7 +69,8 @@
 - Open the solution file **Project.sln** and make sure the configuration is set to the platform 'x64' and compile mode displayed in combo box in the middle of the main window is the same with what you selected while compiling VTK and while the cmake-gui configuration of vIST/e. Then press **F7** to build all project modules. You may get some errors because it is missing the linking library to 'opengl32.lib'. You need to add the library to the "RightClick>Properties MenuItem>Configuration Properties>Linker>Input>Additional dependencies' field of  plugin projects GPUGlyphPlugin, RayCastPlugin, FiberVisualisationPlugin in Solution Explorer window. Adding opengl32.lib to each of their configurations should remove the linking issues. Note that 3 plugins can be selected together before the Right-Click, rather than selecting projects one by one and setting their link dependencies. 
 - If building ends without any error the dlls can be found in ..\\YourBuildDirectory\\tool\\bin\Release (or  Debug).
 - To launch vIST/e from Visual Studio, right-click the **vIST/e** project and select **Set as Startup Project**. Then press **F5** to start vIST/e if you compiled in Debug mode else use **Ctrl-F5**.
-- - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode.
+- - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode in VS2012 for compiling.
+-Similarly If viste is prepared in Release mode and compiled and run in debug mode "'vISTe.exe' (Win32): Loaded 'C:\Windows\System32\guard64.dll'. Cannot find or open the PDB file." error may occur. Solution is same, run cmake-gui again and compile and run viste in that mode. 
 - At first startup, vIST/e may produce some messages, e.g., about a missing settings.xml (which it will create), but also about certain files being invalid Qt plugins. This is caused by the fact that the build directory where vISTe.exe is located also contains non-DLL files which the plugin loader tries to load. This fails of course and vIST/e shows an error. The best thing to do is to hold down the 'Enter' button to quickly run through all error messages until the tool itself starts. The next you start vIST/e this will not happen anymore.

 - It might be the shaders are not found. Move the shaders directory where vISTe.exe is located

BuildWindowsVS2012 modified by vISTe

vISTe — Thu, 25 Apr 2013 15:08:36 -0000

--- v34
+++ v35
@@ -69,7 +69,7 @@
 - Open the solution file **Project.sln** and make sure the configuration is set to the platform 'x64' and compile mode displayed in combo box in the middle of the main window is the same with what you selected while compiling VTK and while the cmake-gui configuration of vIST/e. Then press **F7** to build all project modules. You may get some errors because it is missing the linking library to 'opengl32.lib'. You need to add the library to the "RightClick>Properties MenuItem>Configuration Properties>Linker>Input>Additional dependencies' field of  plugin projects GPUGlyphPlugin, RayCastPlugin, FiberVisualisationPlugin in Solution Explorer window. Adding opengl32.lib to each of their configurations should remove the linking issues. Note that 3 plugins can be selected together before the Right-Click, rather than selecting projects one by one and setting their link dependencies. 
 - If building ends without any error the dlls can be found in ..\\YourBuildDirectory\\tool\\bin\Release (or  Debug).
 - To launch vIST/e from Visual Studio, right-click the **vIST/e** project and select **Set as Startup Project**. Then press **F5** to start vIST/e if you compiled in Debug mode else use **Ctrl-F5**.
-
+- - In case of "QWidget: Must Construct a QApplication before a QPaintDevice" error at the startup, empty build directory then rerun cmake-gui with the correct build mode then use the same build mode.
 - At first startup, vIST/e may produce some messages, e.g., about a missing settings.xml (which it will create), but also about certain files being invalid Qt plugins. This is caused by the fact that the build directory where vISTe.exe is located also contains non-DLL files which the plugin loader tries to load. This fails of course and vIST/e shows an error. The best thing to do is to hold down the 'Enter' button to quickly run through all error messages until the tool itself starts. The next you start vIST/e this will not happen anymore.

 - It might be the shaders are not found. Move the shaders directory where vISTe.exe is located

BuildWindowsVS2012 modified by vISTe

vISTe — Tue, 23 Apr 2013 08:20:02 -0000

--- v33
+++ v34
@@ -41,7 +41,7 @@
 - You will get an error on "make_pair (var1,var2)" constructions that are not allowed anymore in VS2012. You should replace them by "make_pair(var1,var2)" in (vtkMapArrayValue)
 - You will also get an error in file vtkAdjacencyMatrixToEdgeTable.cxx. In order solve it you need to add "#include  ". 
 - Everything should build fine from there.
-- When the build has finished add the directory C:\\VTKLibs\\5.8.0-x64\\bin\\Debug (or Release) to the system PATH. When you are running vIST/e you should make sure that the right directory(Debug/Release) is being referred to. This is necessary for finding dlls at runtime. Do not install VTK to the system because VTK_DIR is going to be set in cmake-gui settings of vIST/e. If you want to test vIST/e  both in release and debug mode, compile VTK in both modes successively, it will create Debug and Release automaticly under C:\\VTKLibs\\5.8.0-x64\\bin as described above.
+- When the build has finished add the directory C:\\VTKLibs\\5.8.0-x64\\bin\\Debug (or Release) to the system PATH. When you are running vIST/e you should make sure that the right directory(Debug/Release) is being referred to. This is necessary for finding dlls at runtime. Do not install VTK to the system because VTK_DIR is going to be set in cmake-gui settings of vIST/e. If you want to test vIST/e  both in release and debug mode, compile VTK in both modes successively, it will create Debug and Release automaticly under C:\\VTKLibs\\5.8.0-x64\\bin as described above. You can also add both paths to the system PATH environment variable.

 Checkout vIST/e source code
 ---------------------------
@@ -66,7 +66,7 @@
 - Click configure until no more red colored items are visible. vIST/e by default enables all plugins except those that require special libaries. For example, the IllustrativeClusters plugin requires GLEW and is disabled. Also, the FiberTrackingCUDA plugin requires CUDA and is also disabled. Be sure you carefully set the CMAKE_BUILD_TYPE variable.
 - cmake-gui application will show a VTK_DIR variable; C:\\VTKLibs\\5.8.0-x64\\ is the correct path. (During the linking ${VTK_DIR}\\bin\\Release or Debug will be searched because Cmake makes the necessary adjustments. If you configured and compiled vISTe in Release(Debug) the corresponding VTK dll files must be in the corresponding VTK directory. If you want to test vIST/e in both Debug and Release modes and you have compiled VTK in both modes be sure that system PATH environment variable includes both ${VTK_DIR}\\bin\\Release and ${VTK_DIR}\\bin\\Debug. But strangely I found that the ${VTK_DIR}\\bin\\Debug directory path should be given before?)  
 - When no more red colored items are visible, press **Generate** to generate the 64-bit Visual Studio solution.
-- Open the solution file **Project.sln** and make sure the configuration is set to the platform 'x64' and compile mode displayed in combo box in the middle of the main window is the same with what you selected while compiling VTK. Then press **F7** to build all project modules. You may get some errors because it is missing the linking library to 'opengl32.lib'. You need to add the library to the "RightClick>Properties MenuItem>Configuration Properties>Linker>Input>Additional dependencies' field of  plugin projects GPUGlyphPlugin, RayCastPlugin, FiberVisualisationPlugin in Solution Explorer window. Adding opengl32.lib to each of their configurations should remove the linking issues. Note that 3 plugins can be selected together before the Right-Click, rather than selecting projects one by one and setting their link dependencies. 
+- Open the solution file **Project.sln** and make sure the configuration is set to the platform 'x64' and compile mode displayed in combo box in the middle of the main window is the same with what you selected while compiling VTK and while the cmake-gui configuration of vIST/e. Then press **F7** to build all project modules. You may get some errors because it is missing the linking library to 'opengl32.lib'. You need to add the library to the "RightClick>Properties MenuItem>Configuration Properties>Linker>Input>Additional dependencies' field of  plugin projects GPUGlyphPlugin, RayCastPlugin, FiberVisualisationPlugin in Solution Explorer window. Adding opengl32.lib to each of their configurations should remove the linking issues. Note that 3 plugins can be selected together before the Right-Click, rather than selecting projects one by one and setting their link dependencies. 
 - If building ends without any error the dlls can be found in ..\\YourBuildDirectory\\tool\\bin\Release (or  Debug).
 - To launch vIST/e from Visual Studio, right-click the **vIST/e** project and select **Set as Startup Project**. Then press **F5** to start vIST/e if you compiled in Debug mode else use **Ctrl-F5**.