On Tue, Feb 03, 2004 at 09:49:35PM +0000, Andy Hassall wrote:
> On Tue, 3 Feb 2004 10:42:16 -0500, [EMAIL PROTECTED] (Jeff Urlwin) wrote:
>
> >>>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 ...
> >>
> >> Attached is a patch, on the assumption that VCINSTALLDIR is ...
> >
> >Actually, I'd recommend against this. That's what the MakeMaker warning is
> >for...
>
> Hm, fair point, I think I agree, since checking properly devolves into
> scanning libraries; which is what MakeMaker is doing. Although it does say
> "probably harmless" - but in this case it's not harmless.
I'd like to be able to give a warning hint in this case. There are
many such hints built in already and everyone has saved time for
users, the mailing list, and myself.
Clueful people will ignore the warning if they know they have setup
sufficient env vars manually. It's the less clueful people we're
trying to help. They're the ones who barely know vcvars32.bat exists.
Tim.
