consider using cuda_wrap_srcs instead of cuda_add_library

[cyrush]

cuda_wrap_srcs is more flexible than cuda_add_library.

Basically, we can use it to create an object lib for the nvcc compilation results, and then use that with the normal CMake add_library.

This is the approach we took in Strawman (https://github.com/llnl/strawman)
https://github.com/LLNL/strawman/blob/develop/src/strawman/CMakeLists.txt

It doesn't fix the overall issues with not being able to set specific properties for cuda targets after they are create, but it would help us create a clean solution to issues like #74 and #60

@davidbeckingsale what do you think?

[DavidPoliakoff]

@cyrush , is there a PR with this implemented? I'm having trouble compiling CUDA under BLT (#136), and would like to see if alternative implementations would work.

[cyrush]

Not yet ...

[white238]

Closed due to removal of FindCUDA

[davidbeckingsale]

We technically still use FindCUDA to detect the location of the CUDA libraries. Do we know if CMake's native CUDA support works for object libraries?