Package Details: blender-2.92-git 2.92.r102890.gf24992d2ec7-1

Git Clone URL: https://aur.archlinux.org/blender-2.92-git.git (read-only, click to copy)
Package Base: blender-2.92-git
Description: Maintenance version of Blender v2.92 branch
Upstream URL: https://blender.org/
Licenses: GPL
Conflicts: blender=2.92
Provides: blender=2.92
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 0
Popularity: 0.000000
First Submitted: 2021-01-21 22:35
Last Updated: 2021-01-21 22:35

Dependencies (27)

Required by (52)

Sources (8)

Pinned Comments

bartus commented on 2021-01-21 22:54

Note: This is a non conflicting version of blender-git package with GPU architecture detected at build time.
This package is also hosted on GitHub.
Use env vars to control build process:
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix)
  • DISABLE_NINJA=1 to switch build system to make (default:ninja)
  • DISABLE_OPTIX=1 to skip optix device build.
  • DISABLE_USD=1 to 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=1 before build
  • DISABLE_CUDA=1 ~your-aur-helper~
  • makepkg DISABLE_CUDA=1
  • yay -S blender-2.8-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.

Latest Comments

bartus commented on 2021-02-01 09:04

@restique: Nope, till 2013 they can go with makepkg call same like with make.

Putting them inside PKGBUILD only results in merge conflicts when doing git pull.

And don't even start me on interactive PKGBUILD's, they're cancer and need to be doubt with ●~* ( >_<)

I think I could add some pop up warning, but most mundane users just spam comment section instead of reading PKGBUILD. And if they knowledgeable enough to dive inside PKGBUILD they don't need no over explanations.

ruestique commented on 2021-02-01 08:26

env vars my man, they should be incide PKGBUILD, just like in many others AUR packages ~_~

bartus commented on 2021-01-31 09:32

this f*g keys

What the fuck is your problem mate. (っ´ω`)ﾉ(╥ω╥)

ruestique commented on 2021-01-31 01:10

why this f*g keys is not in PKGBUILD file ???

bartus commented on 2021-01-21 22:54

Note: This is a non conflicting version of blender-git package with GPU architecture detected at build time.
This package is also hosted on GitHub.
Use env vars to control build process:
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix)
  • DISABLE_NINJA=1 to switch build system to make (default:ninja)
  • DISABLE_OPTIX=1 to skip optix device build.
  • DISABLE_USD=1 to 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=1 before build
  • DISABLE_CUDA=1 ~your-aur-helper~
  • makepkg DISABLE_CUDA=1
  • yay -S blender-2.8-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.