Swig is very easy as long as your c code is broken into separate subroutines. You just add the subroutine descriptions to the .i file, and run it thru swig, then compile. Here is an example of controlling your cdrom tray with swig. cdrom with swig

If you do a search on perlmonks for cdrom, I have the same code as inline C. You can look at them for comparison.

The advantage to using swig is that it precompiles the c into a .so shared object file, thereby increasing speed. Inline c needs to compile the code at each calling of the script.

I havn't tried xs, it just seemed to much complexity for the task at hand.

In reply to Re: Inline::C vs. XS vs. SWIG by zentara
in thread Inline::C vs. XS vs. SWIG by Anonymous Monk

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.