[Ffmpeg-devel] [PATCH] Correct inttypes.hemulation for VisualStudio

Diego Biurrun diego
Tue Dec 5 19:57:35 CET 2006

On Tue, Dec 05, 2006 at 01:39:51PM +0100, Michel Bardiaux wrote:
> Luca Abeni wrote:
> >
> >What's the problem with copying some "stdint.h" approximation somewhere
> >in the include path? (some windows users are saying that the typedefs
> >proposed in the patch that originated this thread work ok... So why not
> >putting them in the include path, but _outside_ ffmpeg's libraries?)
> >I think something like this has been proposed in this tread, but I am
> >failing to see why this solution would not fix the problem.
> >
> >I am serious: I understand that there are people that want to use libav*
> >in msvc projects, and I think this is not an unreasonable expectation
> >(of course, it is unreasonable to expect that other people will do the
> >work).
> The whole point of the thread is whether it is reasonable or not to wish 
> for this work to be integrated in the main tree.

It will not be done.

So will somebody step forward and create an inttypes emulation for MSVC
that can be used by more than just FFmpeg or will the MS crowd just
continue lobbying for the easy way out in vain?

I'm serious, will somebody provide a constructive solution or will there
be just more complaints?

We had a similar situation with Intel Mac support.  Michael stood firm and
rejected the hacky solutions until finally somebody came up with an
acceptable patch.  The inttypes issue will be no different.


More information about the ffmpeg-devel mailing list