Re: Using Perl's cc

[Gavin Smith]

On 4 July 2015 at 19:48, Eli Zaretskii <address@hidden> wrote:
>> Meanwhile I looked around, and it sounds like all that's needed is
>> something like --with-perl-dir=/path/to/perl/installation/directory,
>> and perhaps a small change to how fetch_conf.pl is invoked (it should
>> no longer run "/usr/bin/env perl", but the one in the specified
>> directory's bin/ subdirectory).  Moreover, it sounds like ActiveState
>> Perl, which is what I have here, already supports MinGW automagically
>> (it returned the correct file name for 'cc' config option, and I
>> cannot see how it could do that without examining my system's PATH).

I think running "./configure PERL=/path/to/perl" could work. In the
latest commit the fetch_conf.pl script isn't used; ${PERL} -V is used
instead.

> Hmm... one slight complication:
>
>   $ /d/usr/Perl/bin/perl ./fetch_conf.pl archlibexp
>   D:\usr\Perl\lib
>
> It outputs the directory with backslashes.  This cannot be put
> verbatim into a Makefile, because Bash needs each backslash doubled.

In the latest, I turned two backslashes (output by Perl) into one. I
would expect

    $ /d/usr/Perl/bin/perl -V:archlibexp
    archlib='D:\\usr\\Perl\\lib'

(Note that the interpretation of single quotes differs between Perl
and the Bourne shell, where backslash is not a special character
there.)

This can easily be tweaked as necessary, for example, leave double
backslashes as they are.