Front page | perl.perl5.porters |
Postings from April 2018
On Sun, 08 Apr 2018 21:03:16 -0700, tonyc wrote: > Thanks, applied as 908f2cb56527d29c9176e478fa7eee0d02a7c77e. > > There's still a problem if you build with STATIC_EXT=Unicode/Normalize > but that might be more difficult to fix. > > I do wonder if the Win32 build should build miniperl, then use that to > build the final config.sh/config.h and generate a Makefile for the > full perl from there. > > Tony What will generate the makefile? Makefile.SH would have to be rewritten in PP. IMO its pointless because Windows doesn't come with a "Unix shell" compiler and M4 compiler out of the box and switching to Visual C with Autoconf+Bash (I've built such FOSS projects before) is insane since not even Unix perl uses M4 or autoconf. I know you wrote one patch 2 yrs ago that generates an auxiliary extensions only makefile for parallel extension building so each extension can be parallelzed to infinity cores instead of the 4 "categories" of extensions building side by side they way they do now and doesn't saturate all cores. -- bulk88 ~ bulk88 at hotmail.com --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=133070Thread Next