+1 on dumping the custom CMake toolchains in VTK and using the native CMake support instead. Obviously a lot easier to maintain, and more scalable when needing to configure more CMake properties than the ones currently hardcoded. Some useful links:
- https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos
- https://cmake.org/cmake/help/latest/prop_tgt/FRAMEWORK.html
I don’t know anything about the Android build, but it looks like there was support even before: https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html#cross-compiling-for-android
Those tickets might help with dependency issues on iOS:
- FindThreads: https://gitlab.kitware.com/cmake/cmake/-/issues/18993#note_631486
- findPackage with CONFIG: https://gitlab.kitware.com/cmake/cmake/-/issues/19655#note_619698
See this comment on the CMake’s issue tracker to follow on that topic:
https://gitlab.kitware.com/cmake/cmake/-/issues/21752#note_903018
@ken-martin @ben.boeckel I thought VTK had an iOS job with tests on CDash but I can’t seem to find it. I haven’t done any vtk development for iOS in a while: has it been removed, or am I misremembering?