But now I need to turn it into a pre-compiled, free-standing loadable moduleNot that it has much to do with your actual problem, but the approach you're taking will fail to create a "free-standing loadable module" - in that it will still depend upon Inline::C.
Nothing necessarily wrong with that. It just struck me as something worth pointing out (in case it *is* relevant to your aims). If you want to avoid the Inline dependency altogether,
InlineX::C2XS can convert your Inline::C code to a suitable XS file, and even write you a stub Makefile.PL and Your_Mod.pm in the process.
As to the actual problem, there's nothing wrong with what you're doing (based on your description), but it *is* highly likely that you are doing *something* wrong. The stuff that you are doing usually works quite well.
Inline::C does throw up some pretty strange errors at times - messages that don't really help you determine exactly what it is that you've done wrong. This could well be another example of that.
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.