[FFmpeg-devel] [PATCH] build: Allow libffmpeg to be built for Chromium-based browsers

Nicolas George george at nsup.org
Sat Jul 29 12:40:30 EEST 2017

Le decadi 10 thermidor, an CCXXV, James Le Cuirot a écrit :
> This Makefile snippet allows libffmpeg to be created without the help
> of Chromium's build system. It uses the CONFIG_SHARED variable to
> decide whether to link the FFmpeg libraries statically or
> dynamically. In the latter case, libffmpeg is just a wrapper with no
> symbols of its own.

I concur with the other remarks: this is not the right approach, and it
has many flaws.

But on the other hand, I strongly support the underlying idea: having
many libraries causes no end of trouble, for users a little but for
developers mostly. See for example the proliferation of avpriv symbols
whenever code needs to be factored between libraries but too complex for
a public API.

So if you were interested in making this right: make it the default and
only library for the project, to be applied at / instead of the next
major bump, I would strongly support it, and help to the extent of my

If not, it is still something I intend to work on, but I have other more
pressing projects.


  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20170729/6435f03c/attachment.sig>

More information about the ffmpeg-devel mailing list