Be aware that, although Inline::CPP is basically in good shape, it is currently
unmaintained (as has been the case for quite some time). So check
the bug reports.
There's also
a problem when using ParseRecDescent-1.96.0 with Inline::CPP. I don't know whether subsequent versions of Parse::RecDescent suffer the same problem - I do know that version 1.94 is fine.
You probably already know that making the library and its headers visible to the compilation process is achieved in the same way as is done with Inline::C:
use Inline CPP => Config =>
INC => '-I/path/to/include',
LIBS => '-L/path/to/lib -lmylib';
That's about the sum of my knowledge of Inline::CPP. I have used it to successfully access a C++ library, but have done so by running only void functions that print output to the console. I haven't actually passed any objects around between perl and the library.
Cheers,
Rob
Update: Changed "maintained" to "
unmaintained". Thanks
ikegami.
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.