Try starting with something that works, and then add to it.
For example, I have no trouble with:
use warnings;
use strict;
use Inline ('C' => 'DATA');
callback();
sub p_callback {
print "in perl callback\n";
}
__DATA__
__C__
void callback(){
dSP;
PUSHMARK(SP);
call_pv("p_callback", G_DISCARD|G_NOARGS);
}
Does that work ok for you ? Make sure there's an empty line after the end of the C code.
I don't have libwiringPi, and can't really help with the rest. (If I don't have code that I can actually test then I'm likely to end up presenting misinformation.)
Are you aware of the Inline::C configuration option
CLEAN_AFTER_BUILD=>0
It leaves the build directory intact so you can actually inspect the generated XS file and C file - which is sometimes helpful when things aren't working as expected.
Cheers,
Rob
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.