As regards point 1 :
The def file is auto-generated during the 'make' process - which is 'dmake', in my case. How does one influence the contents of the def file that is created by that automated procedure ?
As regards point 2 :
I changed Foo.xs so that it now has:
#include "EXTERN.h"
#include "perl.h"
#include "XSUB.h"
int __declspec(dllexport) foo(int x, int y) {
return x + y;
}
MODULE = Foo PACKAGE = Foo
PROTOTYPES: DISABLE
int
foo (x, y)
int x
int y
But, according to
dumpbin /exports, 'Foo.dll' still exports only '_boot_Foo' and 'boot_Foo'.
I'm using the MinGW compiler - don't know if that has any bearing on the matter ... apologies if I'm being dense.
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.