[x265] Problem with linking x265 and ffmpeg

[宮村 公男]

2014/04/23 2:29、Steve Borho <steve <at> borho.org> のメール：

> Libs.private is populated at compile time from
> CMAKE_CXX_IMPLICIT_LINK_LIBRARIES, which is how we learn the proper
> name of the stdc++ library and other possible link requirements.  In
> other words, statically linking with libx265 should require linking
> against that library.
> 
> Does libclang_rt.osx.a exist at that path?

Yes “libclang_rt.osx.a” is located in that path.

> I don't know why ffmpeg fails to link with it; perhaps the linker does
> not like absolute paths.  Perhaps you're compiling ffmpeg with gcc but
> compiled libx265 with clang and statically linking them together is
> problematic.  Perhaps we should blacklist libclang_rt.osx.a.

I compiled ffmpeg and x265 with same environment, clang.

>> 2.Even though other third party libraries does not require to be add
>> "--pkg-config-flags=—static” option, why x265 only need to be added?
> 
> Probably for the same reason the x265 cli did not work at first,
> libx265.16.dylib was not found in $DYLD_LIBRARY_PATH

Derek-san explained me and I understand.


// Miya