David Cantrell wrote: > CPANTS is something else entirely: > http://cpants.perl.org/ > http://cpantesters.perl.org/ > > Unfortunately the T in CPANTS stands for Testing, which is terribly > confusing, but it is static tests without actually running any of a > module's code. >
I had a feeling they were different. Thanks for the clarification :) > My motivation is that it's a really easy way to give back to the > community. > Good, I hoped as much. Now I'm wondering, as the CPAN testers (not CPANTS) are building XS modules against the C libraries, in your opinion, how hard would it be to get some of them to build a ppm package afterward? > Make, yes. gcc, no. The build tools (such as ExtUtils::MakeMaker) will > use the same compiler as was used to build perl. This will normally be > gcc on Linux and *BSD, but could be icc (Intel's compiler) and on other > platforms is more likely to be one supplied by the vendor. eg on Irix > it'll be the MIPSpro compiler, and on Windows it'll normally be MS C but > could be Borland. > Or MinGW with Strawberry Perl :) > PERL5LIB. See perldoc perlrun. > > And you mean -MCPAN, not -mCPAN. The difference is that using -m > doesn't call the module's import() subroutine, and so the shell() > function won't be available. > Thanks. >> Their account may not have >> access to gcc and make? >> > > That's very rare. If make and a compiler are installed, they're > normally available to everyone who is authorised to install software. > I see. >> I've heard that if you build the module on a similar >> system, you can just upload the Perl modules and c libraries, with a bit >> of tweeking it'll work? Can someone verify this? >> > > Yes, it'll work, provided that you set any paths that need encoding into > the binaries correctly for the target system, and you build against the > right ABI. The easiest way to ensure this is to replicate the target > environment on your own machine - build perl with all the same options > (ie the same Config.pm or perl -V), same compiler, same word length etc. > I'm guessing that once the libraries are built it doesn't matter what compiler was used? I.e. you could build some modules with Borland C and install them on a Perl built with Visual C? Thanks for your responses. They have been most helpful :) Lyle _______________________________________________ BristolBathPM mailing list [email protected] http://mailman.bristolbath.org/mailman/listinfo/bristolbathpm
