Ha. I got it. I needed the AUTO_INCLUDE directive, and not just for the .h, but for the .c as well. Here is the final result.

use Inline C => 'DATA', LIBS => '-logg -lvorbis -lvorbisfile', INC => '-I/inc', AUTO_INCLUDE => '#include "inc/vcedit.h"', AUTO_INCLUDE => '#include "inc/vcedit.c"', VERSION => '0.01', NAME => 'Ogg::Vorbis::Info';

Anyone think this is worth a categorized question(once I hit scribe)? I know it isn't a common question but the available docs are rather hazy on what AUTO_INCLUDE means and don't mention you need to include not only the header file but the source file.

If it is worth a catq, what category? Should there be a category for Inline:: issues?


In reply to Re: Module distribution and Inline::C by dbp
in thread Module distribution and Inline::C by dbp

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.