On May 12, 2019, at 4:14 PM, Reimar Döffinger wrote:
>
> On Sun, May 12, 2019 at 12:07:42PM -0700, Tim Jones wrote:
>> On May 12, 2019, at 11:54 AM, Nicolas George wrote:
>>>
>>> Tim Jones (12019-05-12):
>>>
--disable-all-proprietary/--enable-all-proprietary
>>>
>>> As for this one, on
On Sun, May 12, 2019 at 12:07:42PM -0700, Tim Jones wrote:
> On May 12, 2019, at 11:54 AM, Nicolas George wrote:
> >
> > Tim Jones (12019-05-12):
> >
> >> --disable-all-proprietary/--enable-all-proprietary
> >
> > As for this one, on the other hand, there will be opposition: we do not
> > want
On May 12, 2019, at 11:54 AM, Nicolas George wrote:
>
> Tim Jones (12019-05-12):
>
>> --disable-all-proprietary/--enable-all-proprietary
>
> As for this one, on the other hand, there will be opposition: we do not
> want encourage users to use proprietary software. In fact, there is
> currently
Tim Jones (12019-05-12):
> Has anyone previously discussed or offered up a simplified set of
> config macros for something like:
Options to have auto-detection of external libraries enabled have been
suggested in the past.
> --disable-all-proprietary/--enable-all-proprietary
As for this one, on
Hi Folks,
I've long been a fanatic for ffmpeg and now have the bandwidth to dip my toes
into the developer pool. My primary experience is in file I/O in C, C++ , and
Python, and I force my team to pay close attention to smaller-is-better
refactoring.
With the enormous number of config
