On 23 May 2002, at 0:53, Jan Dubois wrote: > On Thu, 23 May 2002 08:51:19 +0100, "Robert Thorpe" > <[EMAIL PROTECTED]> wrote: > > >> Yes, perlxs is what you are looking for if you want to write Perl > >> extension modules in C/C++. Prepare for a BIG learning curve. > > > >It not what you're looking for if you want to write perl extensions to > >C/C++. SWIG may also be an idea, I don't know if it works on > >windows. > > Yes, there are other possibilities as well. Inline::C being another good > one. But XS is most definitely the native Perl extension mechanism; > everything else basically builds on top of it. > > >> No, ActivePerl should contain everything you need to use PerlEz. Just > >> make sure you include C:\Perl\lib\CORE in your INCLUDE and LIB paths, > >> include perlez.h in your C source and link in perlez.lib. > > > >I learned how to use perlez from your website, but PerlCRT.lib is no > >longer in the activeperl distribution, so it doesn't work anymore. > > PerlCRT is only relevant for ActivePerl 5xx. ActivePerl 6xx (all versions > corresponding to Perl 5.6 and 5.6.1) don't use PerlCRT anymore, so the > issue is moot. PerlEz continues to work just fine; I've tried it with > ActivePerl 631, and besides VC++ you don't need anything else. > I see remove -nodefaultlib and perlCRT.dll
How irritating, I have been trying on and off to embed perl in an application for months. In the end I gave up and did everything in compiled C. Now I know how. -- The information in this e-mail is for use by the addressee(s) only. If you are not the intended recipient, please notify us immediately and delete the message from your computer. No liability or responsibility is accepted for viruses and it is your responsibility to scan attachments (if any). Opinions and views expressed in this email are those of the sender and do not reflect the opinions and views of antenova Ltd. _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
