Package Details: blender-2.83-git 2.83.20.r0.ga56e2faeb7a-1

Git Clone URL: https://aur.archlinux.org/blender-2.83-git.git (read-only, click to copy)
Package Base: blender-2.83-git
Description: LTS Maintenance version of blender-v2.83-release branch
Upstream URL: https://blender.org/
Licenses: GPL
Conflicts: blender
Provides: blender
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 2
Popularity: 0.000000
First Submitted: 2020-05-04 00:28 (UTC)
Last Updated: 2024-03-23 23:16 (UTC)

Required by (61)

Sources (13)

Pinned Comments

bartus commented on 2022-03-14 10:30 (UTC)

Sorry lads, I'm at the Polish Ukraine border helping allocate refugees. Expect no update until this hell is over, wish us luck. Have no time nor access to my rig and AUR keys to test/post updates. If you have a patch, ping me on email - I'll add you as co-maintainer. Posted with my old script - https://github.com/bartoszek/aur-post

bartus commented on 2021-05-05 08:05 (UTC)

Note: This is a non conflicting version of blender-git package tracing blender-v2.83-maintnance branch for blender:2.83 LTS relaease 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 Next › Last »

bartus commented on 2020-07-30 10:05 (UTC)

@berilac: could you elaborate further on _CMAKE_FLAGS array expansion, I'm curious.

berilac commented on 2020-07-30 10:01 (UTC) (edited on 2020-07-30 10:01 (UTC) by berilac)

@bartus: thanks again! I guess you're suggesting building v2.90 then? :)

Other than that, I was echoing out $_CMAKE_FLAGS each time it was altered with +=( some_text ) and found that the parenthesis lists were not altering the flags.

I changed the lists to single-quotes (and double-quotes where it included as expression) and now it compiles further than before, but ends up hitting a similar error later.

Gonna try v2.90

bartus commented on 2020-07-30 09:33 (UTC) (edited on 2020-07-30 09:57 (UTC) by bartus)

@berilac: I found the problem - after cuda:11 landed in Arch/community it has deprecated sm_30, which is the default build arch for optix device. It's already fixed in blender-v2.90-release

I've cherry-picked the beforemention commit, it should now work with cuda:11 (tested with makepkg CUDA_ARCH=sm_53

berilac commented on 2020-07-30 09:20 (UTC)

@bartus: thanks, but setting that leads to the following. I've got gtx 960M (sm_50), which apparently is now old enough to be deprecated soon :/ Looks like CUDA_ARCH is not setting correctly? and it's now first trying sm_30... I'm digging into this myself as well.

$> makepkg CUDA_ARCH=sm_50

[  3% | 151<5<4045 | 14.1bps ] Generating kernel_optix.ptx
FAILED: intern/cycles/kernel/kernel_optix.ptx 
cd /tmp/makepkg/blender-2.83-git/src/blender/intern/cycles/kernel && /opt/cuda/bin/nvcc --ptx -arch=sm_30 -I /opt/optix/include -I /tmp/makepkg/blender-2.83-git/src/blender/intern/cycles/kernel/.. -I /tmp/makepkg/blender-2.83-git/src/blender/intern/cycles/kernel/kernels/cuda --use_fast_math -o /tmp/makepkg/blender-2.83-git/src/build/intern/cycles/kernel/kernel_optix.ptx kernels/optix/kernel_optix.cu
nvcc fatal   : Value 'sm_30' is not defined for option 'gpu-architecture'
[  3% | 152<4<4045 | 4.1bps ] Generating filter_sm_50.cubin
nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).

bartus commented on 2020-07-29 23:50 (UTC)

@berilac: this looks like some strange artifact form nvcc_arch selection logic. Could you build with makepkg CUDA_ARCH=sm_xx whare xx is your GPU cuda compute capability: https://developer.nvidia.com/cuda-gpus#compute (example geforce980=sm_52)

berilac commented on 2020-07-29 22:57 (UTC) (edited on 2020-07-29 22:57 (UTC) by berilac)

Getting this odd error...

In file included from /build/blender-2.83-git/src/blender/intern/cycles/kernel/kernels/cuda/filter.cu:21:
/build/blender-2.83-git/src/blender/intern/cycles/kernel/kernels/cuda/kernel_config.h:87:4: error: #error "Unknown or unsupported CUDA architecture, can't determine launch bounds"
   87 | #  error "Unknown or unsupported CUDA architecture, can't determine launch bounds"
      |    ^~~~~
/build/blender-2.83-git/src/blender/intern/cycles/kernel/kernels/cuda/kernel_config.h:110:62: error: division by zero in #if
  110 |         (CUDA_THREADS_BLOCK_WIDTH * CUDA_THREADS_BLOCK_WIDTH * CUDA_KERNEL_MAX_REGISTERS) > \

DarkStar1997 commented on 2020-07-25 16:17 (UTC)

Hi @bartus, I think it happened because I edited the PKGBUILD to turn on -DWITH_PYTHON_MODULE=ON. On removing it fixes the issue. But then I now I am getting libosdCPU.so.3.4.0 not found, same for libosdGPU.so.3.4.0 and libGLEW.so.2.1 I am getting this error with blender-2.90-git as well and I have checked that I have libosdCPU.so.3.4.3, libosdGPU.so.3.4.3, libGLEW.so.2.2 Any way to solve this?

bartus commented on 2020-07-24 17:04 (UTC) (edited on 2020-07-24 17:05 (UTC) by bartus)

@DarkStar1997: strange, this shouldn't happen. Could you please post full package log makepkg --log; ix blender-2.83-git*package.log

You should have this line in blender-2.83-git*package.log

Installing: [...]/blender-2.83-git/pkg/blender-2.83-git/usr/share/applications/blender.desktop

DarkStar1997 commented on 2020-07-24 06:58 (UTC)

I am facing the following error during the installation:

-- Installing: /home/rohan/blender-2.83-git/pkg/blender-2.83-git/usr/lib64/python3.8/site-packages/2.83/datafiles/usd/usdImagingGL/resources/plugInfo.json
==> add -2.83 suffix to desktop shortcut
sed: can't read /home/rohan/blender-2.83-git/pkg/blender-2.83-git/usr/share/applications/blender.desktop: No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

bartus commented on 2020-05-24 08:52 (UTC) (edited on 2020-05-24 08:53 (UTC) by bartus)

blender-2.83 is the binary name in this package.

Package also provides desktop shortcut which is visible in your desktop environment.

You can always use pacman -Ql package_name|grep bin to list binaries in the package.

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