Package Details: blender-develop-git 4.4.r143685.gc51615923b3-1

Git Clone URL: https://aur.archlinux.org/blender-develop-git.git (read-only, click to copy)
Package Base: blender-develop-git
Description: Development version of Blender (non-conflicting version)
Upstream URL: https://blender.org/
Licenses: GPL
Conflicts: blender
Provides: blender
Submitter: bartus
Maintainer: bartus
Last Packager: bartus
Votes: 12
Popularity: 0.000000
First Submitted: 2020-05-04 01:47 (UTC)
Last Updated: 2024-11-20 15:48 (UTC)

Dependencies (43)

Required by (63)

Sources (10)

Pinned Comments

bartus commented on 2020-01-16 16:01 (UTC) (edited on 2021-11-01 14:05 (UTC) by bartus)

Current packages state (non-conflicting ones):

bartus commented on 2019-04-10 11:40 (UTC) (edited on 2024-03-01 09:41 (UTC) by bartus)

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 the build process:
  • DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor+optix,requires:cuda)
  • DISABLE_HIP=1 to skip amdgpu kernel build (requires:hip-runtime-amd)
  • ENABLE_PYTHON_INSTALL include bundled python (default:off)
  • DISABLE_NINJA=1 to switch the build system to make (default:ninja)
  • DISABLE_OPTIX=1 to skip Optix device build.
  • DISABLE_DRACO=1 to skip gltf exporter draco mesh compression extension.
  • FRAGMENT="#{commit,tag,branch}=..." for making bisect build.
  • CUDA_ARCH="sm_xx sm_yy" to build for a specific Cuda arch, supports multiple values.
  • HIP_ARCH="gfx900 gfx1103" to build for a specific amdgpu arch, supports multiple values.
  • MAKEFLAGS="xxx" to override default make flags (check oom-killer disclaimer below)
  • MAKEFLAGS="xxx:yyy" to override default make flags (colon-separated list)
Usage cases:
  • export DISABLE_CUDA=1 before build
  • DISABLE_CUDA=1 ~your-aur-helper~
  • makepkg DISABLE_CUDA=1
  • yay -S blender-develop-git --mflags "DISABLE_CUDA=1 DISABLE_HIP=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 9 Next › Last »

novemberist commented on 2019-11-29 09:40 (UTC)

openimagedenoise is now in [community]. So the oidn dependency should be changed to openimagedenoise to avoid conflicts.

bartus commented on 2019-11-25 20:26 (UTC) (edited on 2020-01-16 15:57 (UTC) by bartus)

As blender:2.81 landed in [community] repository I've added bledner-2.80-git maintenance package to AUR

bartus commented on 2019-11-18 23:46 (UTC) (edited on 2019-11-18 23:47 (UTC) by bartus)

@AndrewGura: I've just build inside manjaro lxc container with both yay and stable-x86_64-build without any issues. Perhaps there is some problem with your local system intallation.

Please try setting up chroot with mkmanjaroroot /tmp/root base-devel and running it with manjaro-nspawn /tmp/root and build form there.

AndrewGura commented on 2019-11-18 15:34 (UTC) (edited on 2019-11-18 15:34 (UTC) by AndrewGura)

@bartus sorry for being unclear and not providing important info. The issue I reported happens when installing with makepkg -sri, and I'm using Manjaro rather than Arch, so I don't have extra-x86_64-build.

I tried to do it with stable-x86_64-build, but it failed:

==> Creating chroot for [stable] (x86_64)...
==> Creating install root at /tmp/stable-x86_64/root
==> Installing packages to /tmp/stable-x86_64/root
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from disk : Couldn't open file /var/cache/pacman/pkg/devtools-20180531-1-any.pkg.tar.xz/core.db
error: failed to update core (download library error)
error: failed retrieving file 'extra.db' from disk : Couldn't open file /var/cache/pacman/pkg/devtools-20180531-1-any.pkg.tar.xz/extra.db
error: failed to update extra (download library error)
error: failed retrieving file 'community.db' from disk : Couldn't open file /var/cache/pacman/pkg/devtools-20180531-1-any.pkg.tar.xz/community.db
error: failed to update community (download library error)
error: failed to synchronize all databases
==> ERROR: Failed to install packages to new root
==> ERROR: Failed to install all packages
==> ERROR: Aborting...

bartus commented on 2019-11-17 00:03 (UTC) (edited on 2019-11-17 00:03 (UTC) by bartus)

@AndrewGura: Can you please test if it works in clean chroot.

sudo mount -o remount,suid /tmp/
sudo pacman -S devtools
cd /tmp
git clone https://aur.archlinux.org/blender-2.8-git.git
cd blender-2.8-git
extra-x86_64-build -r /tmp/

AndrewGura commented on 2019-11-15 23:01 (UTC)

Hello!Facedwith issue with latest version:

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

    "/include"

  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
  provide.

Can someone help me with that? Thanks!

bartus commented on 2019-11-02 08:09 (UTC) (edited on 2019-11-02 11:12 (UTC) by bartus)

@sausix:

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
        libosdGPU.so.3.4.0 => /usr/lib/libosdGPU.so.3.4.0 (0x00007fb2c936c000)
        libosdCPU.so.3.4.0 => /usr/lib/libosdCPU.so.3.4.0 (0x00007fb2c92af000)

sausix commented on 2019-11-01 21:09 (UTC)

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)

Thanks!

omgold commented on 2019-10-22 12:44 (UTC)

Again, thanks. Yes, that is perfect.

bartus commented on 2019-10-22 12:41 (UTC) (edited on 2019-10-22 12:42 (UTC) by bartus)

@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.

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