Package Details: blender-develop-git 3.0.r107522.gaa321211747-1

Git Clone URL: (read-only, click to copy)
Package Base: blender-develop-git
Description: Development version of Blender (non-conflicting version)
Upstream URL:
Licenses: GPL
Conflicts: blender=3.0
Provides: blender=3.0
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 12
Popularity: 0.000616
First Submitted: 2020-05-04 01:47
Last Updated: 2021-07-25 15:14

Dependencies (34)

Required by (54)

Sources (9)

Pinned Comments

bartus commented on 2020-01-16 16:01

Current packages state (non-conflicting ones):

bartus commented on 2019-04-10 11:40

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

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

bartus commented on 2019-01-04 16:57

@MirandaStreeter: can't reproduce the issue. My build looks fine.

ldd /usr/bin/blender-2.8|grep vdb => /usr/lib/ (0x00007f6340265000)

Perhaps your aur helper has old cache. please build directly and check again.

MirandaStreeter commented on 2019-01-02 03:05

@rigred After making the change, it compiles, But then when attempting to open, I'm seeing this error:

blender-2.8: error while loading shared libraries: cannot open shared object file: No such file or directory

It looks like this may be related to openvdb having been updated to v6.0 recently? I'm not entirely sure if this is an issue upstream or if something was missed in the PKGBUILD.

rigred commented on 2018-12-29 18:32

For those wondering why it doesn't build anymore. Blender has moved the blender-2.8 branch into master as the active tree now. So in the PKGBUILD just change this line

source=('git://' \

To this:

source=('git://' \

Until a 2.8 release is tagged/branched again this is the only solution.

Yosh commented on 2018-12-28 11:34

Please update the master branch.

mowcat commented on 2018-12-23 03:13

The master branch is now blender 2.8.

wojtex commented on 2018-12-06 03:34

@bartus: I was unable to build Blender without llvm6-libs. But they had to fix it, because now it builds well.

bartus commented on 2018-12-02 15:22

@hugegameartgd: Can't help you, sorry. You should report bug upstream.

bartus commented on 2018-12-02 06:38

@nonoesimposible: When there is a straight beta release, for now we stays with rolling beta ;)...

nonoesimposible commented on 2018-12-02 01:08

Is Blender 2.8 Beta coming here soon?

hugegameartgd commented on 2018-12-01 10:18

@bartus blender-2.8 --debug-gpu Using OpenGL 4.3 debug facilities GL application marker: Successfully hooked OpenGL debug callback. GL API performance: GTT mapping a busy "isl-miptree" BO stalled and took 1.131 ms.

GL API performance: GTT mapping a busy "isl-miptree" BO stalled and took 0.041 ms.

GL API performance: GTT mapping a busy "isl-miptree" BO stalled and took 0.036 ms.

GL API performance: GTT mapping a busy "isl-miptree" BO stalled and took 0.045 ms. [...] GL shader compiler other: FS SIMD8 shader: 14 inst, 0 loops, 106 cycles, 0:0 spills:fills, Promoted 0 constants, compacted 224 to 144 bytes. GL shader compiler other: FS SIMD16 shader: 14 inst, 0 loops, 118 cycles, 0:0 spills:fills, Promoted 0 constants, compacted 224 to 144 bytes. Saved session recovery to '/tmp/quit.blend'

Blender quit