I tracked down the source of the confusion. The Chromium team has a repo that sits between Chromium and the main ffmpeg repo. This repo is discussed here:
https://chromium.googlesource.com/chromium/third_party/ffmpeg.git The trouble is that this page shows README instead of README.chromium, so it shows contributing instructions that are applicable to git:// source.ffmpeg.org/ffmpeg.git ffmpeg, but aren't applicable to the repo it links to. I'm mentioning this just in case some other lost soul shows up trying to contribute a patch to a Chromium only file. I'll get my patch landed in the right place. Thanks for the help. On Wed, Nov 25, 2015 at 5:46 AM, Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 11/25/2015 12:05 AM, Bruce Dawson wrote: > > This would make ffmpeg fail on VS versions prior to VS 2013, for those > > using the BUILD.gn file, which I assume is not many. It would be easy to > > add additional conditionals for earlier versions, but if it's just for > > Chromium then 2013/2015 is sufficient. > > If directed to the Chromium team, as noted elsewhere, I doubt this is an > issue, > since they only ever support a single compiler for Windows, at once, as far > as I know. > > - Derek > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > -- Bruce Dawson _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
