- 08 Jan, 2019 40 commits
-
-
Ben Boeckel authored
-
Ben Boeckel authored
It isn't part of VTK's public interface.
-
Ben Boeckel authored
-
Ben Boeckel authored
This helps to find packages that VTK itself needs by adding additional locations to `CMAKE_PREFIX_PATH`. The hard work goes into figuring out which prefixes to add.
-
Ben Boeckel authored
This allows ParaView to easily replicate VTK's package.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
In the long run, it would be nice to have exported module targets be part of a namespace. However, the logic assumes that module names are targets as well. There needs to be some way to find out the target name of a module and use it instead of the module name in various locations.
-
Ben Boeckel authored
Testing within an example is currently broken. Investigation is necessary.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
Some third party packages do not work properly with this setting, so exclude them for now.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
This is so that there is a place to insert new logic for the new module system.
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-
Ben Boeckel authored
-