I suspect you'll fix the problem with UINT if you just have a file named 'typemap'(located in the same directory as the xs file) that contains simply:
UINT T_UV
That should tell perl to treat "UINT" as a "T_UV" (unsigned int) .... and perl knows all about the "T_UV" type and how to deal with it, courtesy of perl/lib/ExtUtils/typemap.
(Btw, you don't need to include windows.h - it has already been pulled in by perl.h.)
Here's a little Inline::C demo that works only if said typemap is present:
# try.pl
use warnings;
use strict;
use Inline C => Config =>
BUILD_NOISY => 1;
use Inline C =><<'EOC';
UINT hello() {
UINT x = 17;
return x;
}
EOC
$x = hello();
print $x;
# On Windows:
# Outputs 17 if typemap is present,
# Otherwise outputs "Undefined subroutine &main::hello called at try.p
+l line 16."
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.