Matthew O. Persico wrote:
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).
You'll need the '.inl' file as well. (I think the '.bs' file is not required.) The other machine needs to have the Inline module installed on it - and the files have to be placed into directories with the correct location relative to the Inline script/module. If someone ever alters the C source code then the whole thing breaks (because the MD5 checksum changes, and consequently alters the names of the pertinent files and directories).
If you want to avoid the Inline dependency completely you can take the XS file autogenerated by Inline and use it to construct a "normal" perl extension (XS) module. For some hints on that see 'perldoc Inline-FAQ' - specifically 'How do I create a binary distribution using Inline'.
5) There is a typo in the module - Prepocess is spelled incorrectly.
Drives me nuts, too. I've been meaning to tell Brian for some time that the correct spelling is "Repossess" ;-)
Cheers, Rob
--
Any emails containing attachments will be deleted from my ISP's mail server before I even get to see them. If you wish to email me an attachment, please provide advance warning so that I can make the necessary arrangements.
