Hi Ben,
thanks for your feedback.
VS 2017 build of VTK 8.2.0 was working 100% fine, .class files were produced correctly, and vtk.jar generated without any problem. Were makefiles different for VTK 8.2.0 as far as building of Java class files is concerned?
Regarding the Ninja build under Windows, and the compilation warnings that I reported in my previous message, today I will make a brand-new attempt starting from a “clean” situation, and I will report back.
I did not set any custom flag manually in my previous attempt.
By the way, I’ve taken a look at the compilation options which are set on my VS 2017 project, as produced by CMake’s output when choosing VS 2017 as the generator, and the “/EHsc” option (see warning in my previous post) is indeed present in the compiler command line. So, I am not sure why it would not be present in case of using Ninja as the generator.
A preliminary question: is Ninja the “standard / usual” build system you use also under Windows for building VTK (including Java)? Or should I prefer VS 2017 as the generator?
Thanks in advance for your feedback.
Best regards,
Marco Sambin