[FFmpeg-devel] libossupport status
Wed Dec 26 14:26:59 CET 2007
> On Mon, Dec 24, 2007 at 11:15:04PM +0900, Jonathan Wilson wrote:
> > > That's what I suspected. On windows actually both are pointers
> > > (or
> > > rather HANDLE) if you use the win api functions, and mingw
> > > nonsensically translates disk files to small integers starting at
> > > 0
> > > (necessary) but without doing the same for sockets. This is why I
> > > think they should fix their broken crap..
> > Is this an issue with MingW or an issue with the C runtime they use
> > (i.e.
> > msvcrt.dll)? Or is it a problem in the ffmpeg code?
> Mingw's claim to just use the MS "C runtime" (msvcrt.dll) is not
> entirely true. They wrap it to fix some of the worst deficiencies
> (e.g. providing 0-based fds in place of windows HFILE crap), but stop
> short and don't fix all the problems...
I suppose they didn't want to grow too big like cygwin...
> Another major area they need to fix is doing away with the 8bit
> locale-based filesystem calls and WinMain entry code and instead use
> the corresponding unicode functions, then provide a UTF-8 environment
> to the application. This would allow mingw apps to access all files
> rather than just ones whose names are representable in latin-1 or
> whatever the local "ansi codepage" happens to be.
Ah yes, VLC has (or had at least) that problem...
> Since they're already wrapping the filesystem calls for converting
> handles, doing this would not be much additional work..
It's Free Software, you can send them patches ;)
More information about the ffmpeg-devel