As suggested by
Anonymous Monk you should modify the declarations. Substitute
CV by
struct cv in lines 1552, 1554 and 1557.
But (as remarked by
Anonymous Monk) another problem will show up then with the different prototypes of
void boot_pwiz_swigbindings(PerlInterpreter*, int*) in line 1531 and
SWIGEXPORT void boot_pwiz_swigbindings (pTHXo_ struct cv* cv) from line 1554.
The type of the second parameter
int * is incompatible to
struct cv*. (The number of parameters seems to be right). It looks like SWIG did not generate this correctly with the supplied template. Maybe the template needs to be updated (line 1531 looks wrong).
Anyhow, without access to the complete template and generated file it is quite difficult to guess how this could be rectified.
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.