[FFmpeg-devel] [PATCH] configure: enable libavresample by default

[Michael Niedermayer]

On Mon, Oct 21, 2013 at 08:33:51PM +0200, wm4 wrote:
> On Mon, 21 Oct 2013 20:05:37 +0200
> Michael Niedermayer <michaelni at gmx.at> wrote:
> 
> > On Mon, Oct 21, 2013 at 05:47:56PM +0200, wm4 wrote:
> > > On Mon, 21 Oct 2013 17:17:43 +0200
> > > Clément Bœsch <u at pkh.me> wrote:
> > > 
> > > > On Sun, Oct 20, 2013 at 07:23:23PM +0200, wm4 wrote:
> > [...]
> > 
> > > 
> > > > I don't have a good or simple solution for the problem you raise, but I
> > > > don't agree with that patch, because I find this reckless for the future
> > > > of the project.
> > > 
> > > I really find this funny. Look at all the crappy ABI hacks Michael is
> > > adding to all libav* libraries just to be ABI compatible to Libav, and
> > 
> > if you have suggestions on how code can be made less crappy, these are
> > always welcome
> 
> It's sort of inherent to achieving ABI compatibility with a foreign,
> non-cooperating project. Though I still don't get why users are
> supposed to use setters and getters for fields that are accessed
> directly in Libav. (Perhaps to make it possible that a ffmpeg with
> Libav ABI hacks enabled is compatible to a ffmpeg without Libav ABI?)

fields existing in both projects should be aligned at the same
position in the structs and not need setters or getters, though we
must keep the setters & getters for backward compatibility at least
till the next major ABI bump but IMHO preferrably longer


> 
> > leaving the political stuff and the main subject of this thread for a
> > moment aside
> > technically you should be able to use swresample with libav.
> > If that doesnt work, iam quite interrested in bug reports
> > the only issue i could imagine is that you might need libavutil from
> > ffmpeg too, but thats compatible with libavs so it can be safely
> > droped in if its needed and iam not sure it is
> 
> I think the possibility of distros just packaging ffmpeg proper is
> infinitely higher than doing such a weird, intrusive hack.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20131021/5d08e78e/attachment.asc>