----- Original Message ----- From: "Sisyphus" <[EMAIL PROTECTED]> To: "Jay Blanchard" <[EMAIL PROTECTED]>; <inline@perl.org> Sent: Thursday, October 20, 2005 6:24 PM Subject: Re: Compiler question...
> > ----- Original Message ----- > From: "Jay Blanchard" <[EMAIL PROTECTED]> > > > > > I will install MinGW. How do I make Inline 'aware' of the location? > > It should pretty much take care of itself. > > 1) Install dmake into a location in your path: > http://search.cpan.org/dist/dmake/ (Check the Readme.) > > 2) Install MinGW, and add MinGW/bin to your path: > http://prdownloads.sourceforge.net/mingw/MinGW-3.1.0-1.exe?download > > 3) Install ExtUtils::FakeConfig from CPAN according to the instructions in > the Readme. > > 4) Install Inline-0.44 from CPAN by running: > perl -MConfig_m Makefile.PL (Inline should report that it has found > gcc.exe. Accept the prompt to install Inline::C.) > dmake test > dmake install > I finally managed to test this out and step 4) is not quite right. It should be as follows: 4) Install Inline-0.44 from CPAN by running: set perl5opt=-MConfig_m perl Makefile.PL dmake test dmake install Similarly, when you run an Inline script for the first time the 'perl5opt' environment variable needs to be set to '-MConfig_m'. After the C code has been successfully compiled, it doesn't matter whether the perl5opt environment variable is set or not. Setting that environment variable just means that *whenever* 'perl' is called, 'perl -MConfig_m' is actually called - which means that the %Config::Config values from Config_m.pm are loaded. There are also times when that environment variable needs to be *unset* - eg, if you were to build the PAR module from CPAN, I think you would find that perl5opt needs to be unset, and you would then build PAR by running: perl -MConfig_m Makefile.PL dmake test dmake install But most of the time it won't make any difference whether perl5opt is set or not. Cheers, Rob
