Note: This is a non conflicting version of blender v3.0 Beta package with GPU architecture detected at build time.
This package is also hosted on GitHub.
- Please report
issuesandpatchesat GitHub.
Use env vars to control build process:
DISABLE_CUDA=1to skip cuda kernel build (cycles+compositor+optix)DISABLE_NINJA=1to switch build system to make (default:ninja)DISABLE_OPTIX=1to skip optix device build.DISABLE_USD=1to skip universal scene descriptor build.FRAGMENT="#{commit,tag,branch}=..."for making bisect build.CUDA_ARCH="sm_xx sm_yy"to build for a specific Cuda arch, supports multiple values.MAKEFLAGS="xxx"to override default make flags (check oom-killer disclaimer below)
Usage cases:
export DISABLE_CUDA=1before buildDISABLE_CUDA=1 ~your-aur-helper~makepkg DISABLE_CUDA=1yay -S blender-3.0-git --mflags "DISABLE_CUDA=1"
Yay users warning:
Since yay relies solely on aur-rpc to solve dependencies instead of calling makepkg --sync it can't follow dependencies logic defined in PKGBUILD. That's why it's up to the user to provide dependencies to enable desired features. Optional features includes cuda/optix/usd.
tl;dr; If you want to prebuild cycles kernels, you have to install CUDA beforehand. If you don't have CUDA installed, PKGBUILD will fail unless you disable cuda with DISABLE_CUDA=1, same for optix and usd.
Out of memory killer.
You may use ninja-mem to prevent oom-killer when building on system with low memory to core ratio.
To activate use MAKEFLAGS+=" -m75" where 75 is the percentage upper threshold of memory usage when new build jobs is postponed.
Or simply lower the make jobs count in "MAKEFLAGS" variable, but this will prolong your build process.
Pinned Comments
bartus commented on 2021-11-01 14:06 (UTC)
Note: This is a non conflicting version of blender v3.0 Beta package with GPU architecture detected at build time.
This package is also hosted on GitHub.
issuesandpatchesat GitHub.Use env vars to control build process:
DISABLE_CUDA=1to skip cuda kernel build (cycles+compositor+optix)DISABLE_NINJA=1to switch build system to make (default:ninja)DISABLE_OPTIX=1to skip optix device build.DISABLE_USD=1to skip universal scene descriptor build.FRAGMENT="#{commit,tag,branch}=..."for making bisect build.CUDA_ARCH="sm_xx sm_yy"to build for a specific Cuda arch, supports multiple values.MAKEFLAGS="xxx"to override default make flags (check oom-killer disclaimer below)Usage cases:
export DISABLE_CUDA=1before buildDISABLE_CUDA=1 ~your-aur-helper~makepkg DISABLE_CUDA=1yay -S blender-3.0-git --mflags "DISABLE_CUDA=1"Yayusers warning:Since yay relies solely on
aur-rpcto solve dependencies instead of callingmakepkg --syncit can't follow dependencies logic defined inPKGBUILD. That's why it's up to the user to provide dependencies to enable desired features. Optional features includes cuda/optix/usd.tl;dr; If you want to prebuild cycles kernels, you have to install CUDA beforehand. If you don't have CUDA installed,
PKGBUILDwill fail unless you disable cuda with DISABLE_CUDA=1, same for optix and usd.Out of memory killer.
You may use ninja-mem to prevent oom-killer when building on system with low memory to core ratio.
To activate use MAKEFLAGS+=" -m75" where 75 is the percentage upper threshold of memory usage when new build jobs is postponed.
Or simply lower the make jobs count in "MAKEFLAGS" variable, but this will prolong your build process.