I use Inline::C for some production code, and had to work around the issues you described. My solution was to create some infrastructure for precompiling the XS generated by Inline::C when requested. So when developing, I run using Inline::C, and get automatic recompiles when I change the C code. To release, I run make precompiled, which is a target I defined to force compilation of all of the Inline::C code and copy it over to the installation location. At runtime, the module chooses based on an environment variable whether to use Inline::C or the prebuilt stuff (on a production machine, you don't need to install the Inline module at all.)

In more detail:

Each of my Inline-using scripts looks like: 

package Whatever;
BEGIN {
  do ($ENV{DEVEL_MODE} ? 'MyMagicInline' : 'MyMagicDirect') or die $@
}
...perl code...
__DATA__
__CPP__
...C++ code... (ok I lied; I'm using Inline::CPP, not Inline::C)

[download]

$ENV{DEVEL_MODE} is set automagically by something else, but don't worry about that. Just always have it set while you're developing.

MyMagicInline contains something like: 

use Inline with => 'MyScriptInline';
BEGIN {
  $inline_code_file = abs_path($INC{__PACKAGE__ . ".pm"});
}

sub find_code {
  local $_ = shift;
  s/^.*?__CPP__\n//s;
  return $_;
}
use Inline(CPP => $inline_code_file, FILTERS => \&find_code);
Inline->init;

[download]
The MyScriptInline file contains a single subroutine named Inline that returns a hash ref of Inline settings (eg { INC => '-I/my/path' }). (This is how Inline implements its with magic.)

RxMagicDirect contains only 

require DynaLoader;
{
        my ($pkg) = caller(0);
        push @{$pkg . "::ISA"}, "DynaLoader";
        bootstrap $pkg;
}

[download]
Ok, so that's just a sketch of what's going on; there are details about where the files are found and the precompilation target that runs everything under Inline and then copies the generated *.so files to the appropriate lib/ directory, but the end result is that I can install onto a production machine and not have to install Inline there.

I'm sure this isn't the cleanest way to do this. I never really bothered to go back and clean it up after I got it to work, but it seems to work quite well for what I need.

In reply to How to use Inline::C for production code by sfink
in thread In praise of h2xs: A tool you gotta have by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.