in reply to xdg at Perl Seminar NY Tuesday October 17

Hi Jim,
Could you (or even someone else) impress upon David the following points:

1)The version of MinGW that ships with Strawberry Perl really should include the fortran compiler (g77.exe) - so that the PGPLOT and PDL (and perhaps other) modules can be built;
2)Strawberry Perl ought also include the MSYS shell as part of the download - so that C libraries like gmp, gsl, expat, mpfr, netcdf, fftw and others can be built on Win32 (trivially), thus enabling the use of modules that rely on those C libraries;

(Sorry - I haven't provided links to those C libraries ... Google should find them readily enough.)

I'm fairly firmly committed to both points ... more so to the former.

I was going to make both points in person, but I find that my passport has expired ;-)

Cheers,
Rob
  • Comment on Re: xdg at Perl Seminar NY Tuesday October 17

Replies are listed 'Best First'.
Re^2: xdg at Perl Seminar NY Tuesday October 17
by xdg (Monsignor) on Oct 15, 2006 at 13:51 UTC

    I think we've had this discussion before, though I can't remember the venue and I support the first point and am open to the second.

    In some of the early Vanilla design discussions, there was concern about not trying to build GNU/Perl if we can avoid it. Including MSYS so that end users can compile libraries pre-supposes that the solution to the external library problem is having each user compile their own.

    In any case, I've added both points to the Vanilla Perl Roadmap, g77 for Build 8 and the other to the "additional toolchain" entry of the backlog. Both would be released and tested in Vanilla before being added to Strawberry. So they're under "official" consideration, to the extent that anything about Vanilla Perl could be considered that.

    -xdg

    Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

      Including MSYS so that end users can compile libraries pre-supposes that the solution to the external library problem is having each user compile their own

      I see the inclusion of MSYS merely as providing another option. You can't always find a library that suits your requirements - eg it wasn't built with the configuration you wanted, or it's a dynamic library whereas you'd prefer a static library so you can distribute binaries of a module without having to include the dll with the package.

      Of course, it's extra bulk to download, and if anyone wants MSYS they can always download it themselves ... hence I refrain from pushing too hard its inclusion.

      Good to hear that g77 is planned for inclusion (subject to testing). I definitely think that's as it should be.

      Cheers,
      Rob