Mik Firestone wrote:
[...]
Finally, I am wondering if I want to distribute the package with Inline::C as a prereq or if it is possible to take the output from Inline::C and make a "pure" XS module from it.
Yes - just grab the XS file that Inline::C generates (by building with the Config option CLEAN_AFTER_BUILD => 0), and use it to build the module in the normal way. Obviously, you then need to amend the .pm file - and if you use the Inline Stack vars, then you'll need Inline.h (also found in the build folder).
It occurred to me recently that it would be nice if Inline had an option whereby all it did was output the XS file. I find I frequently use Inline::C simply to autogenerate the XS file - and in such situations the compilation that inevitably ensues is pretty much a waste of time.
I would like to allow a user to do the "perl
Makefile.pl; make; make test" on one machine and the "make install" on another
machine. If I make Inline::C a prereq, will this be possible if Inline::C is
not installed on the second machine?
No. (Probably possible to *install*, but the module won't work.)
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.