> -----Original Message-----
> From: François LETELLIER [mailto:[EMAIL PROTECTED]]
> Good morning everybody.
Good morning.
> I've been using Perl for a couple of years now. I've written
> modules in C <all this on a mac>,
<snip>
> Now, the time has come to do the same on Win32 :-S Gllllrp.
>
> Here we go again, but this time I just found *NO*
> documentation.
see below.
> The first step, therefore, is to compile/link my modules and
> make DLLs
It used to be that you would read perlxs, perlapi, perlxstut, and the SWIG
documentation, and then shed many tears getting it to work. No more. Now
you check out Brian Ingerson's amazing Inline.pm. It allows you to embed C,
C++, Python, and now apparently Java in your perl scripts. Inline handles
all the compiling, wrapping, linking, etc. and produces compiled modules.
Check out: http://www.perl.com/pub/2001/02/inline.html
IMPORTANT CAVEAT: Inline configures itself, based on Config.pm, to use the
compiler that compiled perl. In the case of the Active State build, this is
cl.exe (the visual c compiler? is that right?). If you have another
compiler, such as gcc, you will need to build perl from source using that
compiler, or find someone who has a perl binary built with that compiler (I
have one built with gcc). Alternatively, you could attempt to reconfigure
Config.pm, XSUB.h, etc. to be gcc compatible, but I have yet to get this to
work.
Eric
