aevaSlicer windows build fails on vs2019 factory machines
This may have been introduced after upgrading to Slicer 5.0.3 (0102bbec). Slicer has moved to VS2022. Building aevaslicer locally on VS2022 also succeeds without issues. This is mainly a problem with the windows factory machines used for aevaSlicer that are still use vs2019. Easiest fix is to update the build scripts to use VS2022 just like Slicer-core.
Failure message is on libFFI :
LINK : fatal error LNK1181: cannot open input file 'C:\D\E\A-0-build\LibFFI-build\objlib.dir\Release\debug.obj' [C:\D\E
\A-0-build\LibFFI-build\ffi_static.vcxproj] [C:\D\E\A-0-build\slicersources-build\LibFFI.vcxproj]
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(
241,5): error MSB8066: Custom build for 'C:\D\E\A-0-build\CMakeFiles\904136fef52b9be7e58b257472708c68\LibFFI-update.rul
e;C:\D\E\A-0-build\CMakeFiles\904136fef52b9be7e58b257472708c68\LibFFI-configure.rule;C:\D\E\A-0-build\CMakeFiles\904136
fef52b9be7e58b257472708c68\LibFFI-build.rule;C:\D\E\A-0-build\CMakeFiles\904136fef52b9be7e58b257472708c68\LibFFI-instal
l.rule;C:\D\E\A-0-build\CMakeFiles\7c617d3f63ff7e4e4872e0dc280338a2\LibFFI-complete.rule;C:\D\E\A-0-build\CMakeFiles\f4
0b137df7d9729655a7a62a6f5eb2fe\LibFFI.rule' exited with code 1. [C:\D\E\A-0-build\slicersources-build\LibFFI.vcxproj]
It appears that libFFI doesn't switch properly to release
build configuration as indicated by parent/Slicer project.
Edited by Shreeraj Jadhav