For my Fedora 25 system using negativo17 nvidia/cuda repository
https://negativo17.org/nvidia-driver/
all the cuda binaries, libraries and includes are not on a single cuda root directory that can be specified by a single CUDA_HOME variable.
R however has separate flags for R_HOME and R_INCLUDE
with_r_home
with_r_include
Thus with using this cuda repository, I'm unable to compile gmatrix since the cuda binaries and libraries are in standard system locations but the includes are in a separate /usr/include/cuda directory.
I could symlink the includes, but it would be a maintenance nightmare.
For my Fedora 25 system using negativo17 nvidia/cuda repository https://negativo17.org/nvidia-driver/ all the cuda binaries, libraries and includes are not on a single cuda root directory that can be specified by a single CUDA_HOME variable.
R however has separate flags for R_HOME and R_INCLUDE
Thus with using this cuda repository, I'm unable to compile gmatrix since the cuda binaries and libraries are in standard system locations but the includes are in a separate /usr/include/cuda directory.
I could symlink the includes, but it would be a maintenance nightmare.
As Fedora 26 is about to be released in a few weeks, it is expected that negativo1's nvidia and cuda repository will be adopted as standard third party repository through GNOME Software. https://blogs.gnome.org/uraeus/2016/11/01/discrete-graphics-and-fedora-workstation-25/