Blender Git Loki

Buildbot: Ensure proper ABI is used

This wasn't an issue in the real buildbot environment since the
precompiled libraries are compiled with same ABI as the compiler
used for Blender build. But it was causing issues when building
Blender using buildbot scripts (for troubleshooting purposes)
on a machine with different default compiler ABI.

Usually ABI detection is happening in platform_unix.cmake when
detecting whether there are any precompiled libraries folder
available. This detection is not happening when library folder
is provided explicitly, expecting ABI to be setup explicitly
as well.

Constraints: remove special meaning of Local Space for parentless Objects.

In 2011 special handling was introduced, apparently for no other
reason than to address a complaint in T25707 that World and Local
space are equivalent for objects without parent. This causes issues
and confusion, as mentioned in rB599c8a2c8e4.

This special meaning of Local Space is not documented in the manual,
and is not known to experienced riggers, so removing it should not
be a problem.

Differential Revision: https://developer.blender.org/D6095

Fix compilation error

Merge remote-tracking branch 'origin/master' into temp-lanpr-cleanup2

simplify naming

Fix crash when adding Scene variable to a driver

When a Scene variable is added to a driver, and the RNA path is still NULL,
it no longer crashes Blender.

Merge branch 'master' into temp-graph-select-changes

Fix rotation and scaling broken in graph editor [insert poo emoji here]

Alembic: improved import/export of mesh normals

This commit implements the change in behaviour described in T71246.
In short:

For export, per mesh:
- Custom loop normals are defined ? loop normals are exported.
- One or more polys are marked flat ? loop normals are exported.
- Otherwise, no normals are exported.

For import, when the Alembic mesh contains:
- loop normals (kFacevaryingScope) ? use as custom loop normals, and
enble Auto Smooth to have Blender actually use them.
- vertex normals (kVertexScope or kVaryingScope) ? convert to loop
normals, and handle as above.
- no normals ? mark mesh as smooth.
- unsupported normal types (kConstantScope, kUniformScope,
kUnknownScope) ? handle as 'no normals'.

This also fixes T71130: Alembic split normal export issue

Previously the mesh flag `ME_AUTOSMOOTH` was used in conjunction with
the poly flag `ME_SMOOTH` to determine whether loop normals or vertex
normals were exported. This behaviour was hard to predict for artists,
and hard to describe in the manual. Instead, Blender now only exports
loop normals, computing them if necessary. This way, the mesh in Alembic
should always have the same loop normals as in Blender.

Maniphest Tasks: T71130

Differential Revision: https://developer.blender.org/D6197

Mathutils: expose the utility to find the closest point of a triangle.

This computation is complex and useful enough to expose the existing
C math utility used by BVH nearest to Python. Otherwise this requires
the use of intersect_point_tri and multiple intersect_point_line calls
with some added vector math.

Differential Revision: https://developer.blender.org/D6200

Merge branch 'master' into greasepencil-object

GPencil: Use parent matrix in Vertex Color modifier

Merge branch 'blender-v2.81-release'

Cleanup: remove unused game engine variable

Overlay Engine: Add Lamps

Merge branch 'blender-v2.81-release'

Cleanup: remove EditNurb from DNA

Merge branch 'master' into soc-2019-bevel-profiles

Remove final print statement

Merge branch 'soc-2019-bevel-profiles' of git.blender.org:blender into soc-2019-bevel-profiles