in reply to Re^2: Inline::C and Packaged Distributions
in thread Inline::C and Packaged Distributions

I'm curious about the mechanics of your procedure. It sounds like, right before packaging your distribution you must remove or comment-out the Inline::C-related code from your modules. Have I got this right? If so, have you automatated this step?

the lowliest monk

  • Comment on Re^3: Inline::C and Packaged Distributions

Replies are listed 'Best First'.
Re^4: Inline::C and Packaged Distributions
by demerphq (Chancellor) on Oct 04, 2005 at 13:08 UTC

    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.

      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;

        or the equivelent

        use Inline Config => FORCE_BUILD => 1, CLEAN_AFTER_BUILD => 0;

        IIRC, this should come before you say

        use Inline::C;

        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.