----- Original Message ----- From: "Jan Dubois" . . > > * On Windows ActivePerl will automatically use MinGW to compile modules > if Microsoft VC++ is not installed, but MinGW and dmake are. >
Excellent move !! Presumably a fresh Config.pm, containing values appropriate for MinGW/dmake, gets written first time you try to build an extension. How did you get around the problem that there's no 'libperl58.a' ? ExtUtils::FakeConfig solves this problem by building a 'libperl58.a', but it occurs to me that since gcc can link directly to a dll, it is perhaps unnecessary to create a 'libperl58.a' at all. Rather, simply modify the appropriate Config.pm values so that gcc does, in fact, link directly to 'perl58.dll'. I just tested that concept out by building Math::FFT (having renamed 'libperl58.a' so it couldn't get found), and linking directly to 'perl58.dll' worked fine. However, I can't provide any arguments in support of doing it that way (as opposed to the 'ExtUtils::FakeConfig' way). In addition, faik, that approach might not work *all* of the time, and I'm not even sure that it can be effected simply by amending Config.pm values - there may be some EU::MM amendments necessary, too. Cheers, Rob _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
