Re: Using Perl's cc

[Eli Zaretskii]

> Date: Sat, 11 Jul 2015 18:01:27 +0100
> From: Gavin Smith <address@hidden>
> Cc: address@hidden
> 
> >   $ perl -V:libperl
> >   libperl='libperl520.a';
> >
> >   $ perl -V:so
> >   so='dll';
> >
> > (The latter because the extension we build -- when we succeed to build
> > it -- will have the .dll extension, not the .so extension as on Unix.)
> 
> I thought libtool would take care of the file extension, but who knows.

It does, but maybe some target that isn't served by libtool will need
this.

> >> If you can get an ExtUtils::MakeMaker makefile working, you could copy
> >> what it does. That would be possible, but could be time-consuming. I
> >> did that for some parts of the existing Makefile.am. I think that
> >> /usr/share/perl5/ExtUtils/MM_Win32.pm and
> >> /usr/share/perl5/ExtUtils/MM_Unix.pm could be the relevant files. It's
> >> "perl Makefile.PL" to create the Makefile.
> >
> > Not sure what you mean by "get an ExtUtils::MakeMaker makefile
> > working".  I already have ExtUtils installed, and the files you
> > mention are present.  But what should I do with them?
> 
> If it successfully builds an extension library, you can look at what
> commands it did to do that and copy them.

Sounds like a project to me, especially since we've already able to
build the extension (barring the vasprintf thing).