Quoting Dave Yeo (2014-11-29 06:11:20)
On 11/23/14 12:31 PM, Anton Khirnov wrote:
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are used
in such
On 11/23/14 12:31 PM, Anton Khirnov wrote:
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are used
in such configurations, doing nothing is ok by definition.
On Sun, 23 Nov 2014 21:31:33 +0100
Anton Khirnov an...@khirnov.net wrote:
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are used
in such configurations,
On 25/11/14 14:22, wm4 wrote:
On Sun, 23 Nov 2014 21:31:33 +0100
Anton Khirnov an...@khirnov.net wrote:
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are used
in such configurations, doing nothing is ok by definition.
Based on a patch by wm4
On 23/11/14 21:31, Anton Khirnov wrote:
Also add no-op fallbacks when threading is disabled.
This helps keeping the code clean if Libav is compiled for targets
without threading. Since we assume that no threads of any kind are used
in such configurations, doing nothing is ok by definition.
