Martin Storsjö <[email protected]> writes:

> On Mon, 18 Jun 2012, Måns Rullgård wrote:
>
>> Martin Storsjö <[email protected]> writes:
>>
>>> On Mon, 18 Jun 2012, Måns Rullgård wrote:
>>>
>>>> Martin Storsjö <[email protected]> writes:
>>>>
>>>>> From: "Ronald S. Bultje" <[email protected]>
>>>>>
>>>>> The check uses check_func_header, since this function is
>>>>> conditionally available depending on the targeted MSVCRT
>>>>> version.
>>>>> ---
>>>>>  configure       |    4 +++-
>>>>>  libavutil/mem.c |    6 ++++++
>>>>>  2 files changed, 9 insertions(+), 1 deletion(-)
>>>>
>>>> LGTM
>>>>
>>>> Were you able to test this both with and without the function visible?
>>>
>>> Yes, if I added --extra-cflags=-D__MSVCRT_VERSION__=0x700, the
>>
>> What does that version number signify?
>
> MS Visual C runtime version, which corresponds to the Visual C++
> version that provided that runtime. The default runtime for mingw is
> 6.0, implemented by "msvcrt.dll", from Visual C++ 6.0 (from just
> around the stone age). Visual C++ 7.0 (2003 I think) seems to have
> added this function.

So what does this mean in terms of which systems a binary built
with/without that flag will run on?

-- 
Måns Rullgård
[email protected]
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to