in reply to C++ and XS compile issues on Win32

Get rid of the extern "C" stuff (apparently it's completely unneccessary and screws things up) and try again (you might need to add #include <stdlib.h> on top).

update: Whenever I've encountered errors like WIN32_CHOKE.txt recompiling the library in question with perl -MExtUtils::Embed -e ccopts (the -MD option is what's important) usually does the trick .

Also, FYI, 'XSOPT'         => '-C++', is a null op, and has been practically always (I checked).

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re^2: C++ and XS compile issues on Win32
by tachyon (Chancellor) on Jun 07, 2004 at 05:58 UTC

    Hi PodMaster thanks for the hints. I have come to the conclusion that XS, Win32, CL.EXE + C++ is a bad combination. With C things can generally be made work but C++. Aargh. While it is easy to build this SDK from within Visual studio as soon as you get out side it and want to do stuff off the command line all sorts of issues start arrising. All due to unresolved externals. I finally got sick of it when I hit an unresolved externals bug related to this MS compiler SNAFU. I don't need it to compile on Win32. I can compile on Linux so time to be practical.

    cheers

    tachyon

[reply]

In Section Seekers of Perl Wisdom