Hello,
I found the lines below very concerning (there is one like this for each of the Java wrappings):
511>Project file contains ToolsVersion="17.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="Current". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424.
511>Target "EnableIntermediateOutputPathMismatchWarning" skipped, due to false condition; ('$(RestoreProjectStyle)' == 'PackageReference') was evaluated as ('' == 'PackageReference').
511>Target "_CheckForInvalidConfigurationAndPlatform" in file "C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets":
511> Set Property: _InvalidConfigurationMessageText=The BaseOutputPath/OutputPath property is not set for project 'vtkChartsCoreJava.vcxproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Release' Platform='Win32'.
511> Set Property: _InvalidConfigurationMessageText=The BaseOutputPath/OutputPath property is not set for project 'vtkChartsCoreJava.vcxproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Release' Platform='Win32'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform.
Other parts of the log refer to 14.42.34433. It looks like a corrupted or misconfigured VS2022 installation to me - or - you are somehow re-using VS project files (.vcxproj files) configured for another VS.
I’d try:
- Make sure you have a clean and healthy VS2022 Community installation. Keep an eye for other VS installed in your system.
- Start a new, clean build of VTK from scratch (delete everything in the build directory).
best,
PC