Blender: Difference between revisions
→HIP: Rephrased to hopefully be more clear. Fixed minor spelling error. |
Replaced #Alternative Binary Packages -> #Binary Packages and changed how it's referred to for hopefully greater clarity |
||
| Line 22: | Line 22: | ||
== Advanced Installation == | == Advanced Installation == | ||
* [[# | * [[#Binary Packages]] for Blender binary packages with support for all APIs | ||
* [[#CUDA & OptiX]] for support for NVIDIA's CUDA & OptiX | * [[#CUDA & OptiX]] for support for NVIDIA's CUDA & OptiX | ||
* [[#HIP]] for support for AMD's HIP | * [[#HIP]] for support for AMD's HIP | ||
* [[#oneAPI]] for support for Intel's oneAPI | * [[#oneAPI]] for support for Intel's oneAPI | ||
* [[#Last Resorts]] if all other methods don't work for your situation | * [[#Last Resorts]] if all other methods don't work for your situation | ||
=== | === Binary Packages === | ||
These are alternative distribution methods that package the Blender binaries, meaning they have support for all APIs. | These are alternative distribution methods that package the Blender binaries, meaning they have support for all APIs. | ||
==== Steam ==== | ==== Steam ==== | ||
| Line 86: | Line 86: | ||
=== HIP === | === HIP === | ||
With the deprecation of the <code>blender-hip</code> package,<ref name="deprecate-hip"> {{pull|463064}}</ref> the easiest way to add Blender with HIP support is now with the <code>rocmPackages.blender</code> package. Other methods are to use the <code>rocmSupport</code> flag the same way as [[#The cudaSupport Flag|#The cudaSupport Flag]], or to use | With the deprecation of the <code>blender-hip</code> package,<ref name="deprecate-hip"> {{pull|463064}}</ref> the easiest way to add Blender with HIP support is now with the <code>rocmPackages.blender</code> package. Other methods are to use the <code>rocmSupport</code> flag the same way as [[#The cudaSupport Flag|#The cudaSupport Flag]], or to use a [[#Binary Packages|#Binary Package]]. | ||
Unlike <code>cudaSupport</code>, most if not all packages with <code>rocmSuppport</code> are built by Hydra and cached into cache.nixos.org. That said, it is still recommended to enable <code>rocmSupport</code> only as much as you will need it, to avoid that chance of unnecessary recompilation on your machine. | Unlike <code>cudaSupport</code>, most if not all packages with <code>rocmSuppport</code> are built by Hydra and cached into cache.nixos.org. That said, it is still recommended to enable <code>rocmSupport</code> only as much as you will need it, to avoid that chance of unnecessary recompilation on your machine. | ||
=== oneAPI === | === oneAPI === | ||
Currently, Nixpkgs has extremely limited oneAPI support, (see: {{issue|367722|oneAPI Tracking}}), which is explicitly blocking oneAPI integration into the Blender package (see: {{issue|447245|Blender oneAPI Support}}). As such, the current only way to have oneAPI support on NixOS is through one of the [[# | Currently, Nixpkgs has extremely limited oneAPI support, (see: {{issue|367722|oneAPI Tracking}}), which is explicitly blocking oneAPI integration into the Blender package (see: {{issue|447245|Blender oneAPI Support}}). As such, the current only way to have oneAPI support on NixOS is through one of the [[#Binary Packages|#Binary Packages]] | ||
=== Last Resorts === | === Last Resorts === | ||