[Ffmpeg-devel] [PATCH] Correct inttypes.h emulation for Visual Studio
Tue Dec 5 12:04:50 CET 2006
Steve Lhomme said:
> Diego Biurrun wrote:
>> Portable programming is not accumulating special cases for every
>> imaginable combination of CPU architecture, operating system and
>> development environment.
> It is actually the case every time I saw portable code in the hardware
> industry. What you're talking about can probably be called compatibility
> (with all the flavors of a single OS: UNIX). Doing "portable" code
> usually involves having an abstraction layer for all the different
> architectures you want to support. And it's often put in "port"
> directories (one for each architecture).
I don't know where you've seen that "portable" code, but I'm sure I wouldn't
want to work there. Where I work, the exact same code compiles and runs on
a dozen different architectures, each with their own compiler and C library.
The low-level hardware drivers differ, that's all.
> In the case of FFMPEG, being compatible with windows seem more and more
> like a bug and less and less like a feature. If you're an MSVC dev (or
> borland, maybe Intel too) you can't simply download MinGW, MSys and
> build FFMPEG from SVN anymore. It used to be the case.
MSVC support in ffmpeg has never been official. If it happens to work at
some time, that's no promise that it will continue to work.
mru at inprovide.com
More information about the ffmpeg-devel