summaryrefslogtreecommitdiffstats
path: root/graphics/Blender/README.Slackware
diff options
context:
space:
mode:
Diffstat (limited to 'graphics/Blender/README.Slackware')
-rw-r--r--graphics/Blender/README.Slackware8
1 files changed, 8 insertions, 0 deletions
diff --git a/graphics/Blender/README.Slackware b/graphics/Blender/README.Slackware
index 7eed585509..669253f6c7 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