>
> >Tim Bunce wrote:
> >> If vcvars32.bat should always be run when using visual C (as I
> >> presume it should be in this case) then I'd love someone
> to post some
> >> code that detects when it should be run ($Config{cc} eq 'cl'?) but
> >> hasn't been (!$ENV{foo}) and gives an clear message about it.
> >
> >VSINSTALLDIR and/or VCINSTALLDIR look like good candidates from the
> >Visual
> Studio.NET 2003 version of it.
> >Anyone got VC++6.0 handy to see if vcvars32.bat sets them both? (I've
> uninstalled it since upgrading).
>
> Attached is a patch, on the assumption that VCINSTALLDIR is
> OK for Visual Studio 6.0 as it is in .NET 2003. (If nobody
> has 6.0 handy to confirm it, I can reinstall it on another
> machine sometime this weekend to make sure)
>
Actually, I'd recommend against this. That's what the MakeMaker warning is
for...
My $0.02...
Jeff
