On Thu, 27 Sep 2012, Derek Buitenhuis wrote:

This practice is not supported by the MinGW developers, and even requires

Hmm, that was news to me (although I might not be too up to date on those matters).

patching the MinGW runtimes in newer versions. Furthermore, we now support
build with MSVC, so this section is rendered useless.

It's not useless even though you can build with MSVC, you might still have other reasons to do it.

Signed-off-by: Derek Buitenhuis <[email protected]>
---
doc/platform.texi |   59 -----------------------------------------------------
1 file changed, 59 deletions(-)

This doesn't look right to me. Static linking itself might not be supported any longer, but 96% of that section is about how to set up so that a MSVC project can link to mingw-built libs in general, unrelated to static libs in particular. Likewise the section on using mingw-built DLLs with MSVC below say "To use those files with MSVC++, do the same as you would do with the static libraries, as described above. But in Step 4..."

So instead of nuking it, the mentions of static libs perhaps can be scrapped and merged with the section on using mingw-built DLLs below.

// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to