D5210: Proper CUDA handling

[Milian Wolff]

mwolff added a comment.


  I think you are still abusing the code architecture for compiler support here.
  
  - the auto-detected nvcc path should be used in a default compiler provider for cuda
  - it can then be cloned and custom args can be added
  - or one adds a completely new cuda compiler with custom clang args
  
  i.e. only add parserArgumentsCuda, move the auto-detection + path stuff to a compiler provider or what it is again. I haven't had a look at the code. if you have trouble with this tell me and I'll have a closer look at the code and try to make it work the way I imagine it for this

REPOSITORY
  R32 KDevelop

REVISION DETAIL
  https://phabricator.kde.org/D5210

To: qi437103, kfunk, #kdevelop, mwolff
Cc: kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170329/47b45d6e/attachment.html>