[vtk-developers] vtk-8.2.0-rc2 problem building wheels

[Matt McCormick]

On Mon, Dec 17, 2018 at 4:13 PM Ben Boeckel <ben.boeckel at kitware.com> wrote:
>
> On Mon, Dec 17, 2018 at 15:07:35 -0500, Matt McCormick wrote:
>
> > Yes -- we are talking about providing the package / module dependency
> > resolution of the system, which is not provided by CMake, and using
> > CMake's build system in a consistent way, as opposed to a secondary
> > build system.
>
> I'm confused. I thought you were mentioning providing an encapsulation
> for the ~150 lines that VTK has in its top-level CMakeLists.txt (finding
> module files, scanning them, building them, wrapping, handling the
> vtk-config.cmake file, etc.). That infrastructure is not provided by VTK
> and nor, IMO, should it. Dependent projects will still need to do those
> 100+ lines in order to be a "proper" project and provide something for
> `find_package` to work well.

The purpose is not to create dependent projects. The purpose is to
create VTK modules. What is the distinction? The former requires
creation, from scratch, a project dependency resolution system and an
ad-hoc way to specify dependencies. The latter facilitates extending
VTK as a library in a scalable way.