<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello, <div><br></div><div>I have a problem with linking x265 and ffmpeg. </div><div><br></div><div>Let me describe outline of problem here…</div><div><br></div><div>I’ve got an error while trying to configure ffmpeg with —enable-libx265. With static x265 library (libx265.a), ffmpeg fails to configure with error “x265 not found”. </div><div>I have upload part of config.log of ffmpeg which related with this error at <a href="http://www10.plala.or.jp/pipedream/config_log.html">http://www10.plala.or.jp/pipedream/config_log.html</a></div><div>This error suspects me that libx265.a is broken or not properly build.</div><div><br></div><div>I’ve made a contact with a person who build ffmpeg with libx265 via web and received his compile environment (Called disk image). With this environment, I have tried the following.</div><div><br></div><div><div>1.pkg-config source is copied from disk image which he sent me. Also, tried x265.pc which he sent to me, so the difference is not exists.</div><div><br></div><div>2.yasm source is copied from disk image which he sent me. I compiled yasm based on his article’s procedure.</div><div><br></div><div>3.cmake source is copied from disk image which he sent me. I compiled yasm based on your article’s procedure. Also tried x265.a which he sent me, so the difference is not exists.</div><div><br></div><div>4.for the purpose of comparing, I downloaded x264 and build it based on his article’s procedure.</div><div><br></div><div>The result is x264′s configure check have passed and x265′s configure check have failed.</div><div>In addition, I can build ffmpeg with –enable-libx264 successfully. </div></div><div><br></div><div>I’ve confirmed both (his libx265.a and my build libx265.a) with ffmpeg configure script log. Then there are no difference except ffmpeg’s temp file name.</div><div><br></div><div>Now I’d like let someone to check these libx265.a is properly build or not. </div><div><br></div><div><br></div><div>On the other hand, I’ve tried to build ffmpeg with shard x265 library (libx265.0.9.dylib, libx265.16.dylib, libx265.dylib) This time, I can build ffmpeg successfully, but shard x265 library’s dependency is incorrect. So I can’t execute ffmpeg without put shard x265 library and ffmpeg binary. Of course I’ve set proper prefix to build x265 and ffmpeg.</div><div><br></div><div>I’d like let someone to check this shard x265 library (libx265.0.9.dylib, libx265.16.dylib, libx265.dylib) is properly build or not. </div><div><br></div><div><br></div><div>I have uploaded x265 libraries at <a href="http://www10.plala.or.jp/pipedream/libx265.zip">http://www10.plala.or.jp/pipedream/libx265.zip</a> (3.7MB)</div><div><br></div><div><br></div><div>Finally, I’ve noticed size of libx265.a is different with camake’s version. cmake-2.8.12.2 creates a bit bigger library than cmake-2.8.12.1. Dose it meaningful or not?</div><div><br></div><div><br></div><div>I appreciate your strong help!!</div><div><br></div><div><br></div><div>// Miya</div></body></html>