MSB8066 error while building 3DSlicer latest version

image
The cmake has compiled and generated without any error. I am getting this error message while building 3DSlicer in visual studio 2022 .I have searched this topic and found out to use the latest version of 3d slicer patched after 28 SEP 2022. I have tried it with the latest version updated on 14-Nov-2022.But the error still persists. I have been stuck with his for the past one week. Kindly help. Many users had asked this question but there is no proper answer.

I tried with:
CMake = 3.19.5, 3.22.4, 3.25.0
Visual studio = 2019, 2022
QT = 5.12.2
OS = WIindows 10 64 bit
git version 2.38.1.windows.1

You may get the error because your build folder path is too long. Please restart the build from scratch using F:\D\S5 for source code and F:\D\S5R or F:\D\S5D for the build folder.

Hello Lassoan,
I build the code as you suggested but still the error occurs.
image

I’ve set up build on a completely new machine

CMake = 3.22.4 (with 3.25.0 or fails, see CHECK_TYPE_SIZE regression in CMake-3.25.0 (#24180) · Issues · CMake / CMake · GitLab)
Visual studio = 2022, toolset v143
QT = 5.15.2
OS = WIindows 11 64 bit

The build completed suxxeasfully.

The main difference that I see that you tried to use Qt-5.12. In the build instructions the required Qt version is 5.15.2. Try to use that and let us know if it fixed the issue.

Thanks for replying, I have build the slicer as per your suggestion .
CMake = 3.22.4
Visual Studio 2022, v143
QT= 5.15.2
OS = Windows 10 ,64 bit.

The build still fails at CTK.

C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): warning MSB8065: Custom build for item “F:\D\S5D\CTK-build\CMakeFiles\efd08cadf5a1ea590d1828fc661b072b\CTK-configure.rule” succeeded, but specified output “f:\d\s5d\ctk-build\ctk-prefix\src\ctk-stamp\release\ctk-configure” has not been created. This may cause incremental build to work incorrectly. [F:\D\S5D\CTK-build\CTK.vcxproj]

36>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): warning MSB8064: Custom build for item “F:\D\S5D\CTK-build\CMakeFiles\efd08cadf5a1ea590d1828fc661b072b\CTK-build.rule” succeeded, but specified dependency “f:\d\s5d\ctk-build\ctk-prefix\src\ctk-stamp\release\ctk-configure” does not exist. This may cause incremental build to work incorrectly. [F:\D\S5D\CTK-build\CTK.vcxproj]

This is the build log of CTK.

Build started…
1>------ Build started: Project: CTK, Configuration: Release x64 ------
1>Performing update step for ‘CTK’
1>No patch step for ‘CTK’
1>Performing configure step for ‘CTK’
1>loading initial cache file F:/D/S5D/CTK-prefix/tmp/CTK-cache-Release.cmake
1>-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.17134.
1>CMake Deprecation Warning at F:/D/S5D/CTK/Utilities/DGraph/CMakeLists.txt:21 (cmake_minimum_required):
1> Compatibility with CMake < 2.8.12 will be removed from a future version of
1> CMake.
1>
1> Update the VERSION argument value or use a … suffix to tell
1> CMake that the project does not need compatibility with older versions.
1>
1>
1>-- Generated: F:/D/S5D/CTK-build/DGraphInput-alldep.txt
1>-- Generated: F:/D/S5D/CTK-build/DGraphInput-alldep-withext.txt
1>-- Generated: F:/D/S5D/CTK-build/DGraphInput.txt
1>-- SuperBuild - First pass
1>-- SuperBuild - First pass - done
1>-- SuperBuild - Log4Qt[OPTIONAL]
1>-- SuperBuild - ZMQ[OPTIONAL]
1>-- SuperBuild - QtSOAP[OPTIONAL]
1>-- SuperBuild - qxmlrpc[OPTIONAL]
1>-- SuperBuild - qRestAPI[OPTIONAL]
1>-- SuperBuild - OpenIGTLink[OPTIONAL]
1>-- SuperBuild - CTK => Requires VTK, PythonQt, DCMTK, ITK, QtTesting,
1>-- SuperBuild - VTK[OK]
1>-- SuperBuild - PythonQt[OK]
1>-- SuperBuild - DCMTK[OK]
1>-- SuperBuild - ITK[OK]
1>-- SuperBuild - QtTesting[OK]
1>-- Adding project:QtTesting
1>-- SuperBuild - CTK[OK]
1>-- Configuring done
1>-- Generating done
1>-- Build files have been written to: F:/D/S5D/CTK-build
1>Performing build step for ‘CTK’
1>MSBuild version 17.3.1+2badb37d1 for .NET Framework
1> Performing update step for ‘PythonQt’
1> No patch step for ‘PythonQt’
1> Performing configure step for ‘PythonQt’
1> loading initial cache file F:/D/S5D/CTK-build/PythonQt-cmake/tmp/PythonQt-cache-Release.cmake
1> – Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.17134.
1> – PythonQt: Required Qt components [Core;Widgets;Multimedia;PrintSupport;Network;MultimediaWidgets;UiTools]
1> – Configuring done
1> – Generating done
1> – Build files have been written to: F:/D/S5D/CTK-build/PythonQt-build
1> No build step for ‘PythonQt’
1> Performing install step for ‘PythonQt’
1> MSBuild version 17.3.1+2badb37d1 for .NET Framework
1> PythonQt.vcxproj → F:\D\S5D\CTK-build\PythonQt-build\Release\PythonQt.dll
1> – Install configuration: “Release”
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/lib/PythonQt.lib
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/bin/PythonQt.dll
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtBoolResult.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtClassInfo.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtClassWrapper.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtConversion.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtCppWrapperFactory.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtDoc.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQt.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtImporter.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtImportFileInterface.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtInstanceWrapper.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtMethodInfo.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtMisc.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtObjectPtr.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtProperty.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtQFileImporter.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtSignalReceiver.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtSlot.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtSlotDecorator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtSignal.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtStdDecorators.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtStdIn.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtStdOut.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtSystem.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtThreadSupport.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtUtils.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtVariants.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQtPythonInclude.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/PythonQt/PythonQt_QtBindings.h
1> Completed ‘PythonQt’
1> Performing update step for ‘QtTesting’
1> No patch step for ‘QtTesting’
1> Performing configure step for ‘QtTesting’
1> loading initial cache file F:/D/S5D/CTK-build/QtTesting-cmake/tmp/QtTesting-cache-Release.cmake
1> – Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.17134.
1> – Configuring done
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> CMake Warning (dev) in CMakeLists.txt:
1> Policy CMP0020 is not set: Automatically link Qt executables to qtmain
1> target on Windows. Run “cmake --help-policy CMP0020” for policy details.
1> Use the cmake_policy command to set the policy and suppress this warning.
1> This warning is for project developers. Use -Wno-dev to suppress it.
1>
1> – Generating done
1> – Build files have been written to: F:/D/S5D/CTK-build/QtTesting-build
1> Performing build step for ‘QtTesting’
1> MSBuild version 17.3.1+2badb37d1 for .NET Framework
1> QtTesting.vcxproj → F:\D\S5D\CTK-build\QtTesting-build\Release\QtTesting.dll
1> Performing install step for ‘QtTesting’
1> MSBuild version 17.3.1+2badb37d1 for .NET Framework
1> QtTesting.vcxproj → F:\D\S5D\CTK-build\QtTesting-build\Release\QtTesting.dll
1> – Install configuration: “Release”
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/lib/QtTesting.lib
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/bin/QtTesting.dll
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/QtTestingExport.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pq3DViewEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pq3DViewEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractActivateEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractBooleanEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractButtonEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractDoubleEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractIntEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractItemViewEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractItemViewEventPlayerBase.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractItemViewEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractItemViewEventTranslatorBase.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractMiscellaneousEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractSliderEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqAbstractStringEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqBasicWidgetEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqBasicWidgetEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqCheckEventOverlay.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqComboBoxEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqComboBoxEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqCommentEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqDoubleSpinBoxEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventComment.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventDispatcher.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventObserver.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventRecorder.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventSource.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqEventTypes.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqLineEditEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqListViewEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqListViewEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqMenuEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqNativeFileDialogEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqNativeFileDialogEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqObjectNaming.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqPlayBackEventsDialog.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqRecordEventsDialog.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqSpinBoxEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqStdoutEventObserver.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTabBarEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTabBarEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTableViewEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTableViewEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTestUtility.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqThreadedEventSource.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTimer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTreeViewEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqTreeViewEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqWidgetEventPlayer.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/pqWidgetEventTranslator.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/include/QtTesting/QtTestingConfigure.h
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/lib/cmake/qttesting/QtTestingConfig.cmake
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/lib/cmake/qttesting/QtTestingTargets.cmake
1> – Up-to-date: F:/D/S5D/CTK-build/CMakeExternals/Install/lib/cmake/qttesting/QtTestingTargets-release.cmake
1> Completed ‘QtTesting’
1> Performing configure step for ‘CTK’
1> loading initial cache file F:/D/S5D/CTK-build/CTK-prefix/tmp/CTK-cache-Release.cmake
1> – Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.17134.
1> CMake Deprecation Warning at F:/D/S5D/CTK/Utilities/DGraph/CMakeLists.txt:21 (cmake_minimum_required):
1> Compatibility with CMake < 2.8.12 will be removed from a future version of
1> CMake.
1>
1> Update the VERSION argument value or use a … suffix to tell
1> CMake that the project does not need compatibility with older versions.
1>
1>
1> – Generated: F:/D/S5D/CTK-build/CTK-build/DGraphInput-alldep.txt
1> – Generated: F:/D/S5D/CTK-build/CTK-build/DGraphInput-alldep-withext.txt
1> – Generated: F:/D/S5D/CTK-build/CTK-build/DGraphInput.txt
1> – SuperBuild - First pass
1> – SuperBuild - First pass - done
1> – Trying to find DCMTK expecting DCMTKConfig.cmake
1> – Trying to find DCMTK expecting DCMTKConfig.cmake - ok
1> – [ITK] Skipping nonexistent library directory or not set variable [ITK_LIBRARY_DIRS]
1> – [VTK] Skipping nonexistent include directory or not set variable [VTK_INCLUDE_DIRS]
1> – [VTK] Skipping nonexistent library directory or not set variable [VTK_LIBRARY_DIRS]
1> – CTKCore: BFD support disabled
1> – Looking for decorator header ctkCorePythonQtDecorators.h
1> – Looking for decorator header ctkCorePythonQtDecorators.h - Found
1> – Looking for decorator header ctkWidgetsPythonQtDecorators.h
1> – Looking for decorator header ctkWidgetsPythonQtDecorators.h - Found
1> – Looking for decorator header ctkDICOMCorePythonQtDecorators.h
1> – Looking for decorator header ctkDICOMCorePythonQtDecorators.h - Found
1> – Looking for decorator header ctkDICOMWidgetsPythonQtDecorators.h
1> – Looking for decorator header ctkDICOMWidgetsPythonQtDecorators.h - Found
1> – ITK is setting CTKImageProcessingITKCore’s MSVC_RUNTIME_LIBRARY to dynamic
1> – Looking for decorator header ctkImageProcessingITKCorePythonQtDecorators.h
1> – Looking for decorator header ctkImageProcessingITKCorePythonQtDecorators.h - Not found
1> – Looking for decorator header ctkScriptingPythonWidgetsPythonQtDecorators.h
1> – Looking for decorator header ctkScriptingPythonWidgetsPythonQtDecorators.h - Not found
1> – Looking for decorator header ctkVisualizationVTKCorePythonQtDecorators.h
1> – Looking for decorator header ctkVisualizationVTKCorePythonQtDecorators.h - Not found
1> – Looking for decorator header ctkVisualizationVTKWidgetsPythonQtDecorators.h
1> – Looking for decorator header ctkVisualizationVTKWidgetsPythonQtDecorators.h - Found
1> – Looking for decorator header ctkQtTestingPythonQtDecorators.h
1> – Looking for decorator header ctkQtTestingPythonQtDecorators.h - Not found
1> – Including CMake built-in module CMakePackageConfigHelpers
1> – Including CMake built-in module CMakePackageConfigHelpers - ok
1> – Configuring done
1> – Generating done
1> – Build files have been written to: F:/D/S5D/CTK-build/CTK-build
1> Performing build step for ‘CTK’
1> MSBuild version 17.3.1+2badb37d1 for .NET Framework
1> CTKCore.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKCore.dll
1> CTKCorePythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKCorePythonQt.pyd
1> CTKDICOMCore.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKDICOMCore.dll
1> CTKDICOMCorePythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKDICOMCorePythonQt.pyd
1> CTKWidgets.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKWidgets.dll
1> CTKDICOMWidgets.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKDICOMWidgets.dll
1> CTKDICOMWidgetsPlugins.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\designer\Release\CTKDICOMWidgetsPlugins.dll
1> CTKDICOMWidgetsPythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKDICOMWidgetsPythonQt.pyd
1> CTKImageProcessingITKCore.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKImageProcessingITKCore.dll
1> CTKImageProcessingITKCorePythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKImageProcessingITKCorePythonQt.pyd
1> CTKVisualizationVTKCore.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKVisualizationVTKCore.dll
1> CTKVisualizationVTKWidgets.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKVisualizationVTKWidgets.dll
1> CTKQtTesting.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKQtTesting.dll
1> CTKQtTestingPythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKQtTestingPythonQt.pyd
1> CTKScriptingPythonCore.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKScriptingPythonCore.dll
1> CTKScriptingPythonWidgets.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKScriptingPythonWidgets.dll
1> CTKScriptingPythonWidgetsPlugins.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\designer\Release\CTKScriptingPythonWidgetsPlugins.dll
1> CTKScriptingPythonWidgetsPythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKScriptingPythonWidgetsPythonQt.pyd
1> CTKVisualizationVTKCorePythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKVisualizationVTKCorePythonQt.pyd
1> CTKVisualizationVTKWidgetsPlugins.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\designer\Release\CTKVisualizationVTKWidgetsPlugins.dll
1> CTKVisualizationVTKWidgetsPythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKVisualizationVTKWidgetsPythonQt.pyd
1> CTKWidgetsPlugins.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\designer\Release\CTKWidgetsPlugins.dll
1> CTKWidgetsPythonQt.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\CTKWidgetsPythonQt.pyd
1> ctkDICOM.vcxproj → F:\D\S5D\CTK-build\CTK-build\bin\Release\ctkDICOM.exe
1> Forcing configure step for ‘CTK’
1> No install step for ‘CTK’
1> Completed ‘CTK’
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): warning MSB8065: Custom build for item “F:\D\S5D\CTK-build\CMakeFiles\efd08cadf5a1ea590d1828fc661b072b\CTK-configure.rule” succeeded, but specified output “f:\d\s5d\ctk-build\ctk-prefix\src\ctk-stamp\release\ctk-configure” has not been created. This may cause incremental build to work incorrectly. [F:\D\S5D\CTK-build\CTK.vcxproj]
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(247,5): warning MSB8064: Custom build for item “F:\D\S5D\CTK-build\CMakeFiles\efd08cadf5a1ea590d1828fc661b072b\CTK-build.rule” succeeded, but specified dependency “f:\d\s5d\ctk-build\ctk-prefix\src\ctk-stamp\release\ctk-configure” does not exist. This may cause incremental build to work incorrectly. [F:\D\S5D\CTK-build\CTK.vcxproj]
1>No install step for ‘CTK’
1>Completed ‘CTK’
1>Done building project “CTK.vcxproj”.

This build is successful.

Yes. But there is MSB8065 warning in CTK build, which is eventually making MSB8066 error.

1 Like

You were building CTK in release mode in a folder named S5D. Is this a debug or release mode build?

It is a x64 release mode build.

I don’t see any issue here then. Open the top-level Slicer.sln, build in Release mode, and if any External project fails to build then open the .sln file of that (as you did for CTK). You’ll then be able to find the actual error message. Hopefully from the error message it will be obvious what the problem is and how to fix it.

1 Like

Hello Lassoan,
Thank you for your help.
I tried to build slicer in a new system and the build has succeeded. The system that I tried to build before has lot of dependencies in system path and I couldn’t remove it till the slicer was building because I need to use them for my other projects also, Anyways, Now if I copy the source and build folder from the succeeded system and copy it in my system , can I able to execute it without any issues?

Yes, if you build Slicer in Release mode and create a package then it can be used on any computer.

1 Like