I managed to get Inline::C to work OOTB with a local crypt library. I have a few questions/comments:
1) I use $VERSION = qw($Revision 1.2$)[1] to generate my version numbers from the CVS version number. Why doesn't this expression work as the value of the VERSION argument to use Inline C =>.... For that matter, if I define our $VERSION = qw($Revision 1.2$)[1]; why can't I just stick that in Inline C VERSION? 2) I tried hard-coding 1.2 as the valid id number, but Inline didn't like it. Why is the regexp for valid Inline Versions /\d.\d\d/? 3) I know what I am doing and the module I am building is not going on CPAN. Is there any way to turn off the checks? 4) If I hand-craft the MANIFEST file to include the .bs and .so generated by Inline, what else would I have to include to avoid a recompile on a target machine (that may not have a compiler). 5) There is a typo in the module - Prepocess is spelled incorrectly. [313] $ make test cp Crypt.pm blib/lib/LF/Crypt.pm AutoSplitting blib/lib/LF/Crypt.pm (blib/lib/auto/LF/Crypt) /opt/perl/bin/5.6.1/perl -Mblib -MInline=NOISY,_INSTALL_ -MLF::Crypt -e1 1.02 blib/arch Using /home/persicom/cvs/SANDBOX/sa/common/src/perl/LF/Crypt/blib Starting Build Prepocess Stage Finished Build Prepocess Stage Thanks -- Matthew O. Persico
