MSVC: MSVC needs a hint to force it to compile either as C or C++.

[Peter Rosin]

Next patch in the MSVC series...

This is
"MSVC needs a hint to force it to compile either as C or C++."
abfb96f4c44b3e38fcf960c876e17fc252e9712c

and the relevant part of

"patch msvc-documentation.patch"
06cfce005204bb8ca212aadab38b38c0202ea04e

with @var changed to @code

This was originally suggested by Ralf here:
http://lists.gnu.org/archive/html/libtool-patches/2006-02/msg00067.html

and first posted here (I think):
http://lists.gnu.org/archive/html/libtool-patches/2007-07/msg00042.html

If you want to see how it is intended to be used, look in
"Add MSVC support"
9c848f1e8acdf435d019aa80f3f0b0aeb45613f7

I don't remember any feedback on this patch, but it seems pretty
benign to me.

Cheers,
Peter

2010-06-22  Peter Rosin  <address@hidden>

        MSVC needs a hint to force it to compile either as C or C++.
        * libltdl/m4/libtool.m4: Add tag variable compile_tag to
        enable tag specific compiler options that are bad in the
        linking phase.
        * libltdl/config/ltmain.m4sh: Add the tag specific options
        to the compile command line.
        * doc/libtool.texi (libtool script contents): Document
        new variable.

compile-tag.patch
Description: Source code patch