[FFmpeg-devel] [PATCH 5/5] Add Windows Resource File support for shared libraries

Alexander Strasser eclipse7 at gmx.net
Fri Sep 28 01:17:32 CEST 2012

jamal wrote:
> On 27/09/12 6:24 PM, Alexander Strasser wrote:
> These descriptions were taken verbatim from the pkgconfig files.
> I thought "Audio rescaling" didn't seem right, but decided against changing it for consistency's sake.
> lavr does use "resampling" instead of "rescaling", so if you think it's a good idea to change libswr's description (And lavfi/libsws as well) i can submit a separate patch changing the corresponding lines in configure, plus a new version of this patch with the rc files updated as well.

  Yeah, you are right then. If we change it, it should be separate
from this patchset. But no need to hurry, maybe we can accumulate
some more description changes.

> > [...]
> > 
> >   Those were all just suggestions, maybe other developers can state their
> > preferences too. Also I guess this can be changed at any time later. No
> > need to do any changes yet. I just think it is always a good idea to think
> > about terminology and to try to come up with a consistent one. It makes
> > it much easier to talk and communicate about FFmpeg, especially to users
> > that normally do not closely follow the development of FFmpeg.
> > 
> > 
> >   Also something slightly OT. I guess you volunteer to maintain this stuff
> > (looks like it will need updates from time to time). Would you like to be
> > the build system maintainer? I think the people currently listed in MAINTAINERS
> > do not maintain our version of the build system anymore which has diverged
> > from their fork. So if you would like to step up to that task, please send
> > a patch to replace the entries in MAINTAINERS with your full name; if you
> > do not want to be listed alone you can write my name after yours.
> I'll think about it.


> I do plan to maintain the rc files nonetheless (Things like copyright date, and potential new libraries or future changes in descriptions). Or better yet, try to find a reliable way to create them with the configure script.

  That's good news!

> >   If you want to, you can also maintain a publicly accessible FFmpeg
> > git repo with your proposed changes. This would make it easier for you to
> > get testers prior to inclusion in the official repo and it is easy to merge
> > it into the official repo as soon as it is ready.
> I'll give github/bitbucket a look then.

Thanks for your help,

More information about the ffmpeg-devel mailing list