"Kort, Eric" wrote:
> > I really only intended that particular example to work with ActivePerl
> > for MSWin32. This requires nmake and cl.exe.
> >
> Ok...what does cl.exe do? Is that a C compiler? Are you saying I should be
> using that instead of the GNU compiler? Finally, can I just install cl.exe
> and still use IndigoPerl, or is there something else special about
> ActivePerl (I don't much care...so I'll switch distributions if need be.)
cl.exe is the compiler that comes with MS Visual Studio. It's what
ActiveState uses to compile ActivePerl. It obviously costs $.
The base rule of Inline is "use the compiler and make tool that was used
to build Perl". (These values are pulled from Config.pm by Inline.) I'm
sure other options/combinations might work, but I'll leave it to the
Inline community to find out and report back.
You're the first person I've heard of that uses Ind**oPerl (censured by
the ruthless ActiveState bureaucracy) with Inline. ActiveState puts a
lot of work into making the Win32 stuff work right. But don't let that
stop you from trying.
Kudos to Leo for testing stuff on Cygwin. I was surprised that it
worked.
I'd be very interested to know if anybody's gotten Inline to work with
ActivePerl and gcc. Let me know what it takes. I'd be willing to put in
a special patch for that particularly useful combination.
Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
