On Tue, Aug 12, 2014 at 10:11:08AM +0200, Hendrik Leppkes wrote: > On Tue, Aug 12, 2014 at 5:48 AM, spanknebel.bor...@t-online.de > <spanknebel.bor...@t-online.de> wrote: > > From 48e4da7d6476ac2a62cc462478b8ccf4d0c45361 Mon Sep 17 00:00:00 2001 > > From: Youka <spanknebel.bor...@t-online.de> > > Date: Tue, 12 Aug 2014 04:32:02 +0200 > > Subject: [PATCH] fix: 'make' with mingw32 > > > > Older mingw32 compilers (not mingw-64, but tdm [default by IDE C::B]) don't > > auto-include pthread headers, so struct timespec & nanosleep are missing > > for compilation of libavutil/time.c. > > --- > > libavutil/time.c | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/libavutil/time.c b/libavutil/time.c > > index ce4552e..a286fca 100644 > > --- a/libavutil/time.c > > +++ b/libavutil/time.c > > @@ -31,6 +31,10 @@ > > #endif > > #if HAVE_WINDOWS_H > > #include <windows.h> > > +#if HAVE_NANOSLEEP > > +#include <pthread.h> > > +#include <pthread_time.h> > > +#endif > > #endif > > > > #include "time.h" > > -- > > 1.8.4.msysgit.0 > > Since when is nanosleep a pthread function? > > If its not the usual posix nanosleep, maybe configure should just be > fixed to disable it instead? > I saw a patch on the libav side that did just that, seems like a
> better solution to me, since Windows has other sleep functions which > get used instead then. do these other functions provide the same performance on windows ? googling a bit doesnt lead to a conclusive awnser to that but at least one page claimed usleep() to be only millisecond precission and one that its "obsolete" (on windows) [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB it is not once nor twice but times without number that the same ideas make their appearance in the world. -- Aristotle
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel