Yeah, I comment out the inline stuff and do it all by hand. And no i havent automated the process as Ive not needed to use it that often. Basically the idea is to use Inline as a bridge to help you grok XS, and once thats done you just use XS because its easier to distribute.

IOW: Inline::C is easier to develop, but XS is easier to deploy.

My problem is that, for reasons I don't yet understand, my Inline::C does not generate *.xs files.

Read more... For example: (688 Bytes)

the lowliest monk

Ahm, shoot. My apologies. You need to enable the option that tells Inline not to clean up after itself. I think you want something like

use Inline Config =>
           ENABLE => FORCE_BUILD,
           DISABLE => CLEAN_AFTER_BUILD;
[download]

or the equivelent

use Inline Config =>
           FORCE_BUILD => 1,
           CLEAN_AFTER_BUILD => 0;
[download]

IIRC, this should come before you say

use Inline::C;
[download]

BTW, I assure you that Inline::C does indeed produce XS. :-) In fact thats exactly what Inline::C does for you: autogenerate XS bindings for the C routines you provide.

---
$world=~s/war/peace/g