No problem for me with relative paths to 2 C files in the same directory: 
C:\>type a.c

void foo() {
 printf("Hello from foo\n");
}


C:\>type b.c

void bar() {
 printf("Hello from bar\n");
}


C:\>type try.pl
use warnings;

use Inline C => "./a.c";
use Inline C => "./b.c";

foo();
bar();

C:\>perl try.pl
Hello from foo
Hello from bar

C:\>

[download]
It may well be that relative paths need to begin with "./".

For LIBS and INC I think you do need to specify an absolute path which, for the cwd, should just be File::Spec->rel2abs('.')
And, yes, that would need to be done in a BEGIN block.

To me, that doesn't seem so bad - I guess it could always be improved.

Cheers,
Rob

In reply to Re: Inline::C with multiple *.c by syphilis
in thread Inline::C with multiple *.c by gri6507

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.