Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • by sigzero (5768) on 2006.01.25 8:37 (#45844) Journal

    While PXPerl seems to have "frozen" at the moment (the guy is a student after all). I would rather have seen someone step in to help on that one as I see this having the most "potential" as it is indepedent.

    I would much rather have the MingW install over the DEV-C++. Why install something like an IDE when 99.9% of the end users will never use it? Too much cruft.

    • I agree. That was the angle I was thinking of and might have tried myself, had I a Windows machine to actually do this on. (Ie. set up MingW, compile Perl with it, then package the lot together with an installer.)

      The ActiveState + Dev-C++ solution is good for contests (you get to win fast), but loads of bloat in practice.

      • I like the compatibility with PPM. In cases where you don't succeed in building an XS module yourself (for example because of dependency on external libriries which is not for newbies in C compilers), then you can always use a prebuilt PPM distribution, which is nice.

        But I sincerely dislike the idea that this installer installs an IDE for C++, just in order to compile XS modules.

        BTW Intrepid on Perlmonk told me earlier today he has built complex XS modules with MinGW to work with ActivePerl. If you know wha
      • Agree with comments on creating a "minimal" installer, based on a vanilla build of perl (or pxperl) and gcc/mingw toolchain. I'd love to do so, but am not interested in signing myself up for the ongoing build and testing of distinct binary releases... as that's yet another distro that can fall by the wayside. Aside from that, I only boot into Windows for testing ;-).

        In the interests of expediency, I simply packaged up some reliable (and maintained) tools in the most straightforward way possible. I would
        • Creating a new distribution, it seems to me, wouldn’t be a huge issue, if only there was an easy way for people beside the original author to repeat the process – ie. a build script, the one thing that PXPerl clearly lacks.

        • Well, not only that, but a managed to get a couple of people to look at simply taking it over the moving ahead on their own, or even to create a screencast of how to get MinGW set up with it.

          None of them were able to do it.

          If someone else is able to make it work, that would be great.

          • Are you saying you don't know how to get MinGW to work for PXPerl? Well, it works for me. I did have to delete a command line option, one that gcc for MinGW (?) apparently didn't support. The command line options that I have left are
            -g -O3 -fno-strict-aliasing
            (Use configure_pxperl, a script with a Tk GUI, to select the MinGW gcc compiler first.)