[Bug 228531] graphics/blender: fails to link with CYCLES

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228531

--- Comment #3 from Shane <FreeBSD at ShaneWare.Biz> ---
Created attachment 193808
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193808&action=edit
build fix workaround for graphics/blender

Adding LLD_UNSAFE=yes does not fix this. The quick workaround is to add
WITH_CYCLES_LOGGING to CMAKE_OFF. When enabled this allows blender to be
started with extra debugging output while rendering, unless gathering info for
a bug report disabling this makes no difference to the user.

For a proper fix I'm not sure why this is happening. The conflict only happens
if devel/gflags is installed when building blender, which includes its own copy
of gflags source in extern/gflags.

devel/gflags is now being installed via graphics/opencv.

Both the port installed and blender included files have
SetCommandLineOption(const char* name, const char* value)

but lld is giving an error looking for 
gflags::SetCommandLineOption(char const*, char const*)

Both sources use "const char*" but lld is looking for "char const*" - but only
when gflags is installed from ports.

Matching code to use SetCommandLineOption is also used in blenders intern/libmv
which doesn't get this error - libmv logging is always enabled and builds if
CYCLES_LOGGING is disabled per the patch.

The two blender sources using SetCommandLineOption are
intern/libmv/intern/logging.cc  -- this builds
intern/cycles/util/util_logging.cpp  -- this fails if gflags port is installed

-- 
You are receiving this mail because:
You are the assignee for the bug.