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

use Perl Log In

Log In

[ Create a new account ]

ajt (2546)

ajt
  (email not shown publicly)
http://www.iredale.net/

UK based. Perl, XML/HTTP, SAP, Debian hacker.

  • CPAN: ATRICKETT [cpan.org]
  • PerlMonks: ajt [perlmonks.org]
  • Local LUG: AdamTrickett [lug.org.uk]
  • Debian Administration: ajt [debian-adm...ration.org]
  • LinkedIn: drajt [linkedin.com]

Journal of ajt (2546)

Thursday June 19, 2008
09:27 AM

Perl on Windows (again)...

[ #36722 ]

A very long time ago I use to be a Happy Windows user. Then I found Unix and for a very long time I was an unhappy Windows user. Except at work were I'm forced to use Windows as my desktop system, I don't really use Windows any more - it's simply a window manager for PuTTY or the SAP GUI.

I've just spent the past 3 hours trying to get a version of Perl onto Windows from which I can then install SAP::Rfc so I can talk to the SAP systems at work. I've tried Cygwin Perl, Stwarbery Perl and two versions of ActiveState Perl. Eventually I found a combination of AS Perl 5.8.8 and a pre-compiled binary of SAP::Rfc that worked and after some messing I got a test to work.

I know it's not Perl's fault that Windows is so rubbish, but developing/testing Perl code on Windows is a miserable experience when compared with pretty much anywhere else...

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.
  • Perl on Windows sux unless you have a compiler. ActivePerl can detect and use MinGW. So, you can have a free compiler to use with perl. There is always the MSVC route though :)
    • I had hoped that Strawberry Perl would work as it comes with MinGW, but it wasn't very happy. Cygwin does dome with gcc but not everything compiles as you would expect. In the end I used a binary provided by the module owner which solved the problem in the short term. However you look at it though Windows is a naff development environment when compared to something that is actually complete like Linux.

      To be honest I'd rather not be using Windows at all but in this case I don't have much of an option...

      --
      -- "It's not magic, it's work..."
    • At previous $job, we were a Windows shop and they provided MSVC. It didn't help much. There were still whole piles of modules that refused to compile. Some were patchable (e.g. module authors assumed directory separator was /), but others were plainly just not going to be worth the grief. Tis indeed true, that the best platform to use software on is the one it was developed on. In most cases for Perl modules, that's unix. I got to the point where I considered it a bonus if a module compiled rather tha
      • Old Sir Bill G has a lot to answer for. When he illegally created DOS and then Windows, by stealing code from others they chose to deliberately break sensible norms and the infamous back-slash directory separator was born. I know that module authors should be more platform independent but it's a pain in the posterior when vendors deliberately create confusion...

        --
        -- "It's not magic, it's work..."