texinfo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using Perl's cc


From: Eli Zaretskii
Subject: Re: Using Perl's cc
Date: Fri, 03 Jul 2015 18:05:54 +0300

> Date: Fri, 3 Jul 2015 15:48:21 +0100
> From: Gavin Smith <address@hidden>
> Cc: address@hidden
> 
> MinGW providing Perl would be the best option.

I don't see the volunteer to take on that job.  There was none until
today; why should that change tomorrow?

> There are other projects that would want to use XS modules, like
> GraphicsMagick mentioned in the other thread. Do you know if any of
> those work on MinGW?

I don't know, and the Google hits don't sound promising.

> Has a MinGW Perl ever been mooted?

I didn't hear about that, but that doesn't mean anything.

> If there was a MinGW Perl, texi2any should use it when run, instead of
> any other Perl installed on the user's system.

Yes.

> Failing that it is probably possible to fall back to the existing Perl
> modules. I don't much like the idea of having to maintain two modules
> in parallel, one in C, one in Perl, which may have subtly different
> behaviour, but it may be unavoidable.

I don't see any alternative, except for using Texinfo 4.13.

> >> Have you had any success in building and using the extension module
> >> from the current trunk under Windows?
> >
> > I don't know.  Does the extension module compile by default?  If not,
> > how do I enable it?
> 
> Yes it does. It should be compiled in the
> tp/Texinfo/Convert/XSParagraph subdirectory by default.
 
If so, that doesn't work:

  Making all in tp
  make[2]: Entering directory `/d/gnu/svn/texinfo/trunk/tp'
  Making all in Texinfo/Convert/XSParagraph
  make[3]: Entering directory 
`/d/gnu/svn/texinfo/trunk/tp/Texinfo/Convert/XSParagraph'
  make[3]: *** No rule to make target `all'.  Stop.
  make[3]: Leaving directory 
`/d/gnu/svn/texinfo/trunk/tp/Texinfo/Convert/XSParagraph'
  Makefile:2997: recipe for target `all-recursive' failed

There's no Makefile in that directory.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]