Arch Linux User Repository

Please report issues and patches to blender-2.7/github.com

<img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-blender-2.7.svg?branch=master" />

Use env vars to control build process:

• DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor)
• 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.7 --mflags "DISABLE_CUDA=1"

Note for yay users:

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.

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.

@lehthanis: try this out.

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

It works in docker:arch the most pristine version of Arch out there, you just need to look harder :)

Perhaps just cleanning the sources before build will help makepkg -C :thinking:

misconfigured? where is the config? I just downloaded the package and makepkg -si

@lehthanis: Nope, you have misconfigured sources, addons_contrib are set to trace blender2.7 branch witch doesn't contains that change.

#.gitmodules
...
[submodule "release/scripts/addons_contrib"]
        path = release/scripts/addons_contrib
        url = ../blender-addons-contrib.git
        ignore = all
        branch = blender2.7

@bartus I just did a system update and can no longer rebuild this package. Error is: Checking patch release/scripts/addons_contrib/object_facemap_auto/auto_fmap_widgets.py... error: while searching for:

    # foo;bar=baz;bonzo=bingo --> {"bar": baz", "bonzo": bingo}
    mpr.fmap_target_rules = dict(
        item.partition("=")[::2] for item in fmap_rules,
    )

    # XXX, we might want to have some way to extract a 'center' from a face-map

error: patch failed: release/scripts/addons_contrib/object_facemap_auto/auto_fmap_widgets.py:324 error: release/scripts/addons_contrib/object_facemap_auto/auto_fmap_widgets.py: patch does not apply ==> ERROR: A failure occurred in prepare(). Aborting...

@lehthanis: Perhaps there is an AUR helper out there that can pull this trick, but I'm not aware of one.

Edit: rebuild-detector is the one ;)

@bartus. I'm not using a helper...could that be my problem? I mean, I use auracle to download and check for aur package updates, but I just use makepkg -si for building aur packages...should I do this differently for reliable results? Thanks much for keeping this updated though!

@lehthanis: I understand your frustration, bumped on the same issue plenty times myself. But correct solution's laying in scope of AUR helpers. If package gets updated it should trigger rebuild of all AUR packages that links to it...

Currently I'm testing Travis script that's pushing changes to AUR for gimp but this is a special case when both package and deps are form AUR.

Every so often I get errors after doing updates on my system...looks like as Arch moves things around, it breaks blender...last week it was boost...this week its:

blender-2.7: error while loading shared libraries: libopenvdb.so.6.1: cannot open shared object file: No such file or directory

Please report issues and patches to blender-2.7/github.com

<img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-blender-2.7.svg?branch=master" />

Use env vars to control build process:

• DISABLE_CUDA=1 to skip cuda kernel build (cycles+compositor)
• 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.7 --mflags "DISABLE_CUDA=1"

Note for yay users:

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.

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.

@hugegameartgd: OK, made some polish out:

User can now use DISABLE_CUDA=1 to exclude cuda from makedepends,