On Mon, 18 Jun 2012, Alex Converse wrote:
On Mon, Jun 18, 2012 at 9:33 AM, Måns Rullgård <[email protected]> wrote:
Diego Elio Pettenò <[email protected]> writes:
> Il 18/06/2012 18:28, Måns Rullgård ha scritto:
>> So what does this mean in terms of which systems a binary built
>> with/without that flag will run on?
>
> As far as I can tell, even version 7 is compatible with 2k and later.
If that's the case, we should consider adding that flag by default.
IIRC we already require 2k for something else.
I'm not trying to advocate a particular position here, but here is a
little bit of background on msvcrt vs versioned runtimes:
http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.71).aspx :
What is the difference between msvcrt.dll and msvcr71.dll?
The msvcrt.dll is now a "known DLL," meaning that it is a system
component owned and built by Windows. It is intended for future use
only by system-level components. An application should use and
redistribute msvcr71.dll, and it should avoid placing a copy or using
an existing copy of msvcr71.dll in the system directory. Instead, the
application should keep a copy of msvcr71.dll in its application
directory with the program executable. Any application built with
Visual C++ .NET using the /MD switch will necessarily use msvcr71.dll.
That does make sense and fits my picture on how one is supposed to do
things on windows. The mingw default of using the plain msvcrt.dll matches
the unix style more then, where you use whatever libc the system happens
to have. Mingw seems to have link libraries for all those versioned
runtimes, too, so I guess it's possible to choose the runtime to link to,
in some way.
Anyway, I guess nobody is opposed to this patch going in as is, the
default targeted version would be a separate patch.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
