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

[Ralf Wildenhues]

Hi Peter,

* Peter Rosin wrote on Tue, Jun 22, 2010 at 03:07:30PM CEST:
> Den 2010-06-22 13:54 skrev Gary V. Vaughan:
> >But compile_tag is never set, so the patch is a NOP!

> >If this has to be fudged into the libtool tag settings by hand to
> >support MSVC (or some other nefarious means I'm missing), then
> >please document that.
> 
> It happens in a later patch. Way-back-when I did it that way to
> not get one big unwieldy monster patch. I.e. first add all parts
> needed, then a final patch that just switches it all on.

> So, it's not a bit deal for me to have this one dangling. But that
> said, it is nice to "fire and forget"...

This one is not fire and forget.  I can live with "fire", but not with
forget, because the right place to fix this issue is not within Libtool.

The issue is similar to what Fortran solves with AC_FC_SRCEXT in
Autoconf, whose result automake uses to to put right before the source
file name.  Here, the same could be done for -Tc or -Tp, respectively.
One difference is that the flag is not specific to the file name
extension, just to the language.

What am I missing?  Ah yes, someone would need to call such a macro;
probably the cleanest way would be call it from AC_PROG_CC.  One cheaper
way could be to hard-code known extensions into 'compile' now, but that
means this script is getting more uglier.

And yes, I should apologize for not seeing this four years ago ...
Comments?

Thanks,
Ralf