On Sat, Jul 26, 2003 at 10:33:03PM +0100, Ed Avis wrote: > Maybe MakeMaker should do a check to see that the make program (be it > nmake or whatever) is in the PATH? And if not, print some message > about how to get it (for nmake, the above URL). Or simply an 'RTFM' > message.
Here is your receipt. https://rt.cpan.org/NoAuth/Bug.html?id=3050 > >Currently we look at $Config{make} but that is inherently flawed > >since its the make Perl was compiled with and while that's usually a > >good guess on Unix, its a very poor one on Windows. > > It seems reasonable enough on Windows - aren't there two main choices, > Microsoft style and GNU style? Since both are equally unlikely to be > available you might as well pick what perl was built with :-(. This isn't a style issue, its a syntax issue. gmake, nmake and dmake all use slightly different syntaxes thus we have to generate slightly different Makefiles. In the end, all that matters is what the user types after "perl Makefile.PL". Will it be gmake, nmake or dmake? That's what must be predicted. -- The beatings will continue until your style improves.
