The FindTBB modules that come with packages such as OSPRay don't
provide TBB_LIBRARY_RELEASE but instead only provide TBB_LIBRARY.
If TBB_LIBRARY_RELEASE isn't found, and TBB_LIBRARY is we will use
that as the release library

The command set_target_properties over-writes any existing values of the
property. Fixed the problem by using set_property with APPEND.

CMake 3.12 introduces a ...<max> syntax in the version given to
cmake_minimum_required to automatically set policies to NEW up
to that version. Use it to avoid listing policies explicitly.

If somebody is using the official TBB binaries on linux
they will encounter issues as the .so files are actually
link scripts which CMake doesn't support. We now manually
work around this problem.

Found via `codespell` and `grep`
more typos

includes source typo change and a typo that needs further review
follow-up typos


Follow-up typos


Revert a commit

Code extracted from:

    https://gitlab.kitware.com/third-party/taotuple.git

at commit ae4936580baf117373e73c23f0f8407d7589e6ff (for/vtk-m).

CUDA currently doesn't support building for `compute_` and having compiled
in virtuals ( using separable compilation ). So we need to transition everything
over to `sm_`

Matthew Letter authored Dec 21, 2017 and Maynard, Robert committed Jan 08, 2018

adding logic for determining a location for cuda windows, the location has to be valid for cmake to config cuda correctly.

Fermi architecture support is being deprecated
in the CUDA 8.0 Toolkit so we are removing it from the all build

modifying CUDA_NVCC_FLAGS to CMAKE_CUDA_FLAGS and CMAKE_CUDA_FLAGS is a string not a list so changed the way the flags are being added to the variable

Ported cuda compiler flags logic from ConfigureComponents over to vtkmDeviceAdapters.cmake

Renamed vtkmBackends.cmake to vtkmDeviceAdapters.cmake and renamed all references to vtkmBackends.cmake to use the new naming scheme.

Obviously this does mean that CUDA is not supported with 3.3.