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

Luca Abeni lucabe72
Tue Dec 5 13:35:17 CET 2006

Hi all,

sorry for replying to this message even if I never used msvc, but...
On Tue, 2006-12-05 at 12:03 +0100, Michel Bardiaux wrote:
> M?ns Rullg?rd wrote:
> > Michel Bardiaux said:
> >> M?ns Rullg?rd wrote:
> >> [snip]
> >>> It did not in any way guarantee that the typedefs supplied were
> >>> correct.  Doing so is rather tricky business, and is best left to the
> >>> compiler/libc, which is where system-dependent things belong.
> >>>
> >> Now, now, you cant spit in the soup and drink it too. If the gnomes of
> >> Redmond are so incompetent, surely it cant be a good idea to leave a
> >> 'tricky business' to them? :-)
> > 
> > Of course not.  That's why using msvc is a bad idea.
> > 
> Well, we have quite a large amount of MSVC-only code, call it legacy if 
> you want, and we dont have a choice, we have to support it, because 
> there is no way I will ever convince my PTBs to redevelop it. The only 
> choice left is to use either an open-source multimedia lib, that's 
> ffmpeg; or a closed-source, Wintel-only multimedia gizmo. What would you 
> have me do?
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
And, unless I misunderstand something, this is perfectly possible
without having to modify ffmpeg (just add a proper .h file somewhere).
So, why is the whole list receiving this big amount of emails? (maybe
it's really time for an ffmpeg-windows mailing list? :-)

Copy this in your signature, if you think it is important:
                               N O    W A R ! ! !

More information about the ffmpeg-devel mailing list