Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I partly blame myself for not taking the time to fully research how to fix that, but also the library authors for largely ignoring the install documentation for Windows.

    If you by this, mean that the authors are not writing install instructions for Windows, then I for one must plead quilty!

    I plead for the mercy of the court, claiming that I could not do otherwise, as my build system is not Windows, I have no build system on Windows and not least I am not mad^Weager enough to go and try to build on all po

    • A fair point.

      I can understand there being little or no documentation if you are unable to test on Windows. However, if there is a start to write install instructions it would be nice to reach the end ;)

      Windows *IS* a major pain, but it's what I have been developing on.

      I picked PDFLib as that was what I have been trying recently, but there have been several other instances of frustration. Perl stuff on the other hand is pretty good at the Windows bit ... CPAN, CPANPLUS or PPM :)

      Are you part of the PD

      • No I (try to) maintain DBD::Ingres. I had a number of requests for installation instructions for Windows, but couldn't help, so I think I know your problem.

        But even on Unix you can have the same kind of problems, we use Dec^WCompaq^WHP Alphas with Tru64; and there is quite a number of libraries that have been a pain to port.

        As long as you can keep to the Perl stuff I find that things are fine mostly. Sometimes people assume that the whole world is Linux (or Win32!).