mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-19 18:45:43 +00:00
ad1e7b5bdb
This mechanism sets up CMake variables that allow a user to select which modules/libraries to create. Dependencies will be tracked down to ensure that all of a module's dependencies are also enabled. The modules are also arranged into groups. Groups allow you to set the enable flag for a group of modules at once. Thus, if you have several modules that are likely to be used together, you can create a group for them. This can be handy in converting user-friendly CMake options (such as `VTKm_ENABLE_RENDERING`) to the modules that enable that by pointing to the appropriate group.
31 lines
1022 B
CMake
31 lines
1022 B
CMake
##============================================================================
|
|
## Copyright (c) Kitware, Inc.
|
|
## All rights reserved.
|
|
## See LICENSE.txt for details.
|
|
##
|
|
## This software is distributed WITHOUT ANY WARRANTY; without even
|
|
## the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
|
|
## PURPOSE. See the above copyright notice for more information.
|
|
##============================================================================
|
|
|
|
# Headers, which are used by tests all over VTK-m, are expected to be in the
|
|
# testing directory where tests are located. We could move things around so
|
|
# that this module is built in the testing directory and the tests are created
|
|
# somewhere else, which would also be confusing to developers trying to add
|
|
# tests. This seems like the least confusing option.
|
|
set(headers
|
|
../testing/RenderTest.h
|
|
../testing/Testing.h
|
|
)
|
|
|
|
set(sources
|
|
RenderTest.cxx
|
|
Testing.cxx
|
|
)
|
|
|
|
vtkm_library(
|
|
NAME vtkm_rendering_testing
|
|
SOURCES ${sources}
|
|
HEADERS ${headers}
|
|
)
|