On Sat, 29 Jul 2017 11:40:30 +0200
Nicolas George wrote:
> 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 FFm
On Sat Jul 29 12:20:05 EEST 2017
Reimar Döffinger wrote:
> On 28.07.2017, at 12:07, James Le Cuirot wrote:
> > diff --git a/ffbuild/libffmpeg.mak b/ffbuild/libffmpeg.mak
> > new file mode 100644
> > index 000..992cf3c
> > --- /dev/null
> > +++ b/ffbuild/libffmpeg.mak
> > @@ -0,0 +1,21 @@
> >
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, libf
On 28.07.2017, at 12:07, James Le Cuirot wrote:
> diff --git a/ffbuild/libffmpeg.mak b/ffbuild/libffmpeg.mak
> new file mode 100644
> index 000..992cf3c
> --- /dev/null
> +++ b/ffbuild/libffmpeg.mak
> @@ -0,0 +1,21 @@
> +LIBFFMPEG = $(SLIBPREF)ffmpeg$(SLIBSUF)
> +LIBFFMPEG_LINK = $(LD) -shar
On 29.07.2017, at 01:05, Ivan Kalvachev wrote:
> On 7/29/17, Dominik 'Rathann' Mierzejewski wrote:
>> On Saturday, 29 July 2017 at 00:20, Hendrik Leppkes wrote:
>>> On Fri, Jul 28, 2017 at 12:07 PM, James Le Cuirot
>>> wrote:
>> [...]
This Makefile snippet allows libffmpeg to be created wi
On 7/29/17, Dominik 'Rathann' Mierzejewski wrote:
> On Saturday, 29 July 2017 at 00:20, Hendrik Leppkes wrote:
>> On Fri, Jul 28, 2017 at 12:07 PM, James Le Cuirot
>> wrote:
> [...]
>> > This Makefile snippet allows libffmpeg to be created without the help
>> > of Chromium's build system. It uses
On Saturday, 29 July 2017 at 00:20, Hendrik Leppkes wrote:
> On Fri, Jul 28, 2017 at 12:07 PM, James Le Cuirot wrote:
[...]
> > 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
On Fri, Jul 28, 2017 at 12:07 PM, James Le Cuirot wrote:
> Google Chrome ships with support for proprietary codecs and Chromium
> can be built with support for them, either using the bundled FFmpeg or
> a system copy.
>
> This leaves other browsers such as Opera and Vivaldi, which ship with
> a li
Google Chrome ships with support for proprietary codecs and Chromium
can be built with support for them, either using the bundled FFmpeg or
a system copy.
This leaves other browsers such as Opera and Vivaldi, which ship with
a libffmpeg that does not support proprietary codecs, presumably for
cost
