Package Details: blender-2.8-git 2.83.r93560.e2722aec6bc-1

Git Clone URL: (read-only, click to copy)
Package Base: blender-2.8-git
Description: Development version of Blender 2.8 branch
Upstream URL:
Keywords: 3d animation mesh modeling pathtracing render vfx
Licenses: GPL
Conflicts: blender-2.83
Provides: blender-2.83
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 10
Popularity: 0.21
First Submitted: 2017-07-14 12:39
Last Updated: 2020-02-20 11:24

Dependencies (30)

Required by (0)

Sources (8)

Pinned Comments

bartus commented on 2020-01-16 16:01

Current packages state:

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_OPTIX=1 to skip optix device build.
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix)
  • DISABLE_NINJA=1 to switch build system to make (default:ninja)
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 features. Optional features includes cuda and optix.

tl;dr; If you want to prebuild cycles kernels, you have to install CUDA beforehand. If you don't have CUDA installed, PKGBUILD will silently skip cycles kernel build, same with the Nvidia Optix support.

Latest Comments

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

AndrewGura commented on 2019-11-15 23:01

Hello!Facedwith issue with latest version:

CMake Error in source/creator/CMakeLists.txt:
  Imported target "Boost::filesystem" includes non-existent path


  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not

Can someone help me with that? Thanks!

bartus commented on 2019-11-02 08:09


Never seen such a complicated PKGBUILD

Finally someone appreciates ;) .

  • You shouldn't have to limit build jobs as your GPU architecture should be detected by cmake using SelectCudaComputeArch.patch. If the detection fails you can also specify your GPU arch manually by passing _cuda_capability=sm_xx to the makepkg (details in the pinned comment).

  • If you still want to limit the concurrent jobs you can switch off ninja, as it doesn't allow to pass flags by environment variable, by passing DISABLE_NINJA=1 to the makepkg (details in the pinned comment) and masking makeflags in the options array in /etc/makepkg.conf (or simply append -j1 to the ninja call in PKGBUILD)

  • Optix won't build without cuda, if you don't need Optix, you can disable it by passing DISABLE_OPTIX=1 to the makepkg (details in the pinned comment)

  • OpenSubdive seams to be included in my build, can't really understand what's your problem there.

ldd /usr/bin/blender-2.82|grep osd => /usr/lib/ (0x00007fb2c936c000) => /usr/lib/ (0x00007fb2c92af000)

sausix commented on 2019-11-01 21:09

Never seen such a complicated PKGBUILD. This really need a manual.

How to restrict thread count for building? Parallel Cuda kernel compilation always kills all my ram and swap. Affects laptop: 8 Threads with 8GB Ram and my Ryzen 16 Threads with 16GB Ram.

MAKEFLAGS="-j1" does not work, also not in combination with DISABLE_NINJA="1".

These also do not work: NINJA_PARALLEL_JOBS="1" NINJA_FLAGS="-j1"

Does CUDA absolutely need optix? Optix should be optional then.

I'm not sure if this affected this PKGBUILD, but opensubdiv was not compiled in even if it was installed before compilation. May be you already fixed this (can't check yet) or it affected blender-git (has opensubdiv support now)


omgold commented on 2019-10-22 12:44

Again, thanks. Yes, that is perfect.

bartus commented on 2019-10-22 12:41

@omgold: blender-2.81-git

We have:

  • blender=2.80 in arch/extra
  • blender=2.81 in aur/blender-2.81-git
  • blender=2.82 in aur/bledner-2.8-git and aur/blender-git
  • blender=2.79 in aur/bledner-2.7-git

When blender=2.80 falls off aur/extra I would add aur/blender-2.80-git

Is this scheme satisfying :)

perhaps. I'll rename this package to bledner-2.8x-git for clearness.

omgold commented on 2019-10-22 09:13

Thanks. It should still be useful later, I assume, as it can be adjusted to install other older versions, then.

bartus commented on 2019-10-22 09:04

@omgold: ok, I'll made one but it would be rether short lived PKGBUILD, as in a week blender 2.81 will land in arch/extra repo (after blender con I assume).

omgold commented on 2019-10-22 07:18

I would have a feature request. It would make sense, IMHO, to name the package and the installed files/dirs 2.81/2.82 instead of just *2.8. Currently blender has 3 versions of 2.8x, which people might want to have installed (2.80 stable, 2.81 beta and 2.82 alpha). Also in general it would be a good thing to allow installing multiple versions in parallel (as new versions tend to break old blend files).

kureta commented on 2019-10-21 08:22

@Humar if you are using yay you can run yay --gendb once and use yay -Syu --devel for system updates, instead of plain yay or yay -Syu. yay --gendb command will store hashes of current commits of your -git packages. yay -Syu --devel will check if any of those saved hashes have changed at the repo origin, meaning there is a new commit, then update if they have.

bartus commented on 2019-09-30 12:04

Nvidia optix backend landed in cycles.
  • Requires precompiled cuda kernel (cuda and optix installed)
  • You need a RTX Nvidia GPU.