> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf Of Carl Eugen Hoyos
> Sent: Monday, November 21, 2016 8:12 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] Avoi
2016-11-21 19:52 GMT+01:00 Gregory J. Wolfe :
> (2) When ALL threading support is disabled, the build should not create a
> dependency on ANY thread library.
If this done through "#if HAVE_THREADS", it would be preferable to
split the patches imo.
Carl Eugen
_
(1) Multi-threading support requires knowing the number of CPUs available.
When building with MinGW on a Windows system, both Windows and gcc run
time functions are available to get this information. If available,
the Windows function should be used, not the gcc function. This avoids
creating an
On Mon, Nov 21, 2016 at 5:23 PM, Gregory J Wolfe
wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
>> Behalf Of wm4
>> Sent: Monday, November 21, 2016 10:05 AM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [
ct: Re: [FFmpeg-devel] [PATCH] Avoid creating unecessary
> > dependencies on thread libraries.
> >
> > On Mon, 21 Nov 2016 09:58:33 -0500
> > "Gregory J. Wolfe" wrote:
> >
> > > (1) Multi-threading support requires knowing the number of CPU
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf Of wm4
> Sent: Monday, November 21, 2016 10:05 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] Avoid creating unecessary
> dependencies on thread libra
On Mon, 21 Nov 2016 09:58:33 -0500
"Gregory J. Wolfe" wrote:
> (1) Multi-threading support requires knowing the number of CPUs available.
> When building with MinGW on a Windows system, both gcc and Windows run
> time functions are available to get this information. However, when Windows
> threa
(1) Multi-threading support requires knowing the number of CPUs available.
When building with MinGW on a Windows system, both gcc and Windows run
time functions are available to get this information. However, when Windows
threading has been selected, the Windows function should be used, not the
gc
