63ef84ed78
As we remove more and more virtual methods from VTK-m, I expect several users will be interested in completely removing them from the build for several reasons. 1. They may be compiling for hardware that does not support virtual methods. 2. They may need to compile for CUDA but need shared libraries. 3. It should go a bit faster. To enable this, a CMake option named `VTKm_NO_DEPRECATED_VIRTUAL` is added. It defaults to `OFF`. But when it is `ON`, none of the code that both uses virtuals and is deprecated will be built. Currently, only `ArrayHandleVirtual` is deprecated, so the rest of the virtual classes will still be built. As we move forward, more will be removed until all virtual method functionality is removed.
30 lines
1.2 KiB
C++
30 lines
1.2 KiB
C++
//============================================================================
|
|
// 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.
|
|
//============================================================================
|
|
|
|
#define vtk_m_worklet_Keys_cxx
|
|
#include <vtkm/worklet/Keys.h>
|
|
#include <vtkm/worklet/Keys.hxx>
|
|
|
|
#define VTK_M_KEYS_EXPORT(T) \
|
|
template class VTKM_WORKLET_EXPORT vtkm::worklet::Keys<T>; \
|
|
template VTKM_WORKLET_EXPORT VTKM_CONT void vtkm::worklet::Keys<T>::BuildArrays( \
|
|
const vtkm::cont::ArrayHandle<T>& keys, \
|
|
vtkm::worklet::KeysSortType sort, \
|
|
vtkm::cont::DeviceAdapterId device)
|
|
|
|
VTK_M_KEYS_EXPORT(vtkm::Id);
|
|
VTK_M_KEYS_EXPORT(vtkm::Id2);
|
|
VTK_M_KEYS_EXPORT(vtkm::Id3);
|
|
#ifdef VTKM_USE_64BIT_IDS
|
|
VTK_M_KEYS_EXPORT(vtkm::IdComponent);
|
|
#endif
|
|
|
|
#undef VTK_M_KEYS_EXPORT
|