What is the correct option to build VTK with an external VTK-m module, rather than the built-in copy? The build options documentation indicates VTK_MODULE_USE_EXTERNAL_<name>
. I have tried several permutations of <name>
, also forum and source code searches with no working answer so far. Thank you for any advice.
Not all third party packages support that option because they are either “always external” (e.g., Catalyst and MPI) or are always internal (VTK-m being one of them). I’m interested in support an external build, but it hasn’t been done yet.
Ben, thanks for that info. I look forward to external build whenever it will be available. I am trying to improve support for MacPorts, and I prefer to break up very large builds into modules, when possible.