2014/07/21 22:32、David Favor <david <at> davidfavor.com> wrote：
> Kimio Miyamura wrote: >> 2014/07/20 1:26、David Favor <david <at> davidfavor.com> wrote： >>> Or if you'd like to build shared, here's the correct incantation... >>> >>> cmake -DCMAKE_INSTALL_PREFIX:PATH=$prefix ../../source >>> >>> You know everything is correct, when the output of otool shows >>> absolute paths for all objects. >> To execute x265 as shared library with in a non-standard library path, We >> need export "DYLD_LIBRARY_PATH". >> $ export DYLD_LIBRARY_PATH=$prefix >> This is same with ffmpeg which uses x265 as shard library. > > Or add ... > > cmake -DCMAKE_INSTALL_PREFIX:PATH=$prefix > > which is preferred, as if you begin doing things like... > > export DYLD_LIBRARY_PATH=$prefix > > Everything's rainbows + unicorns, till you try running a > task out of cron or at the system level... > > Then you have to determine how you'll set this so all processes > pickup this path... and if this path ever changes... or requires > multiple values... you'll have to keep all this straight... > > I've tried this... It becomes complex... > > For me, better to just use the cmake facility for setting this > for each $prefix path that's used. In fact, I don't have any interest with shared library. When I don't know how to configure ffmpeg static binary with x265 support, I just wondered that shared library x265 can configure and build ffmpeg. Except ffmpeg can't be execute at non-standard library path, and for me, adding "export DYLD_LIBRARY_PATH=$prefix" is the solution. I think wrong information is bad for someone who refers this thread. So I write again same thing. Are you really using Mac OS X? Or just talking about your theory which is not confirmed in a real environment? I have tested again your mention "cmake -DCMAKE_INSTALL_PREFIX:PATH=$prefix" solves the non-standard library path issue. Then found that even though use "cmake -DCMAKE_INSTALL_PREFIX:PATH=$prefix" does not solve the issue. In my thinking, your "cmake -DCMAKE_INSTALL_PREFIX:PATH=$prefix" is just define install path of x265, which is same as "./configure --prefix=$prefix". Not related with non-standard library path execution. Attached text file is my test log. I have modified just my Computer name and my user account name. You may see in *real* Mac OS X, if build ffmpeg and x265 as shard library x265, "export DYLD_LIBRARY_PATH=$prefix" is *required*. // Miya _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
