THIS IS A TEST INSTANCE ONLY! REPOSITORIES CAN BE DELETED AT ANY TIME!
This website requires JavaScript.
Explore
Help
Sign In
jolheiser
/
nixpkgs
Watch
1
Star
0
Fork
0
You've already forked nixpkgs
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
9c441c41d7
nixpkgs
/
pkgs
/
development
/
compilers
/
cudatoolkit
History
Daniel Zinn
86c283824f
If cuda headers are presented to nix in $out/include they are added to future gcc calls via a -isystem flag. However, cuda does not allow kernel calls from template function if these are located in system-headers. We thus move headers from $out/include to $out/usr_include and add a custom hook to add these headers via -I.
2014-06-23 06:11:34 -07:00
..
5.5.nix
If cuda headers are presented to nix in $out/include they are added to future gcc calls via a -isystem flag. However, cuda does not allow kernel calls from template function if these are located in system-headers. We thus move headers from $out/include to $out/usr_include and add a custom hook to add these headers via -I.
2014-06-23 06:11:34 -07:00
6.0.nix
If cuda headers are presented to nix in $out/include they are added to future gcc calls via a -isystem flag. However, cuda does not allow kernel calls from template function if these are located in system-headers. We thus move headers from $out/include to $out/usr_include and add a custom hook to add these headers via -I.
2014-06-23 06:11:34 -07:00
setup-hook.sh
If cuda headers are presented to nix in $out/include they are added to future gcc calls via a -isystem flag. However, cuda does not allow kernel calls from template function if these are located in system-headers. We thus move headers from $out/include to $out/usr_include and add a custom hook to add these headers via -I.
2014-06-23 06:11:34 -07:00