[FFmpeg-devel] FFmpeg status on WinCE
Mon Aug 3 22:02:04 CEST 2009
On Mon, Aug 3, 2009 at 10:51 PM, matthieu castet<castet.matthieu at free.fr> wrote:
> ?smail D?nmez <ismail <at> namtrac.org> writes:
>> 2009/8/3 M?ns Rullg?rd <mans <at> mansr.com>:
>> > ?smail D?nmez <ismail <at> namtrac.org> writes:
>> The only way to avoid hacks would be fixing arm-cegcc (WinCE POSIX
>> emulation port) and that would require deep knowledge of gcc, arm &
>> wince. I don't think there are much people with such capabilities. So
>> its not about not caring.
> That's not true.
> First arm and gcc knowledge are not really need. Lot's of missing stuff can be
> added with portable C (something similar to what have be done with libbroken OS).
> For thread you got pthreads-win32 (need some minor patch for wine CE).
> Deep knowlege is really need if you want to do a full compilant POSIX emulation
> (welcome cygwin).
> But that's not the case here. You only need to stub/implement missing part. From
> your first mail it is implementing :
> - a fake errno.h
> - a fake getenv
> - a fake signal.h
There is already implementations for those, the gcc port is broken. If
you fix it I'll fix FFmpeg problems.
More information about the ffmpeg-devel