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

Michel Bardiaux mbardiaux
Tue Dec 5 13:39:51 CET 2006

Luca Abeni wrote:
> 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:

> 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.

> 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? :-)
> 				Luca

Michel Bardiaux
R&D Director
T +32 [0] 2 790 29 41
F +32 [0] 2 790 29 02
E mailto:mbardiaux at mediaxim.be

Mediaxim NV/SA
Vorstlaan 191 Boulevard du Souverain
Brussel 1160 Bruxelles

More information about the ffmpeg-devel mailing list