[FFmpeg-trac] #3394(avformat:new): mp4 -> mkv produces broken file
FFmpeg
trac at avcodec.org
Wed Feb 19 07:19:43 CET 2014
#3394: mp4 -> mkv produces broken file
-------------------------------------+-------------------------------------
Reporter: tessus | Owner:
Type: defect | Status: new
Priority: important | Component: avformat
Version: git-master | Resolution:
Keywords: mkv | Blocked By:
regression | Reproduced by developer: 0
Blocking: |
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by tessus):
That is why I said that they are '''considered static on MacOSX'''.
Technically they are not, but since there is not static version of
libSystem.B.dylib, there are no static binaries on MacOSX, because all
binaries require this lib.
So the term static on MacOSX means that nothing else is required to run
this executable.
So this is as close as you can get on MacOSX.
But 'all-dependend-libraries-to-run-on-MacOSX-are-included' binary is a
tongue twister and that's why people adapted the term static for binaries
that only show system libs in the otool output.
So my binary has all the libs included in the binary to run it on all
MacOSX version > 10.6.8. (e.g. libbluray, libopus, and about 20 more).
It doesn't make any sense to compile it on a system that has Homebrew or
Macports installed where the binary links to files which are only
available on my box and do not exist on a standard MacOSX machine.
The first thing they get is a library missing error when they try to run
it.
But this has nothing to do with the ticket, I just wanted to explain what
people '''consider''' static on MacOSX. I'm not saying that it is
technically correct.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3394#comment:29>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list