diff options
author | Christoph Willing <chris.willing@linux.com> | 2019-04-23 21:05:45 +1000 |
---|---|---|
committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2019-04-27 08:28:06 +0700 |
commit | dae55242c07b7907fe37ff38346a7ea4affd01a3 (patch) | |
tree | 06c7bdf856f41d656a5f418c77d801de563e0bf7 /graphics/Blender/README.Slackware | |
parent | bfdfacdd742124d30fd8315c7a0a54f6e5d09efa (diff) | |
download | slackbuilds-dae55242c07b7907fe37ff38346a7ea4affd01a3.tar.xz |
graphics/Blender: Add CUDA support
Signed-off-by: Christoph Willing <chris.willing@linux.com>
Diffstat (limited to 'graphics/Blender/README.Slackware')
-rw-r--r-- | graphics/Blender/README.Slackware | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/graphics/Blender/README.Slackware b/graphics/Blender/README.Slackware index 7eed585509e6..669253f6c768 100644 --- a/graphics/Blender/README.Slackware +++ b/graphics/Blender/README.Slackware @@ -58,6 +58,14 @@ If resources allow, the very large cudatoolkit package is another possible package which may be preinstalled and be utilised by the opencv build process. +Blender itself can also use cudatoolkit to provide GPU rendering in +systems with NVidia GPU cards. In this case, the SlackBuild will +enable CUDA support if a cudatoolkit installation is detected at +build time. In the unlikely CUDA support is not wanted despite cudatoolkit +being available at build time, set the CUDA environment variable to "no" +when running the SlackBuild e.g. + CUDA=no sh ./Blender.SlackBuild + 2. the ffmpeg package could/should first be built with additional features by preinstalling some other packages e.g. REQUIRES="lame x264 |