in reply to Re: Moving Perl from test to Dev
in thread Moving Perl from test to Dev

For sure you will run into problems in a Windows environment where various DLL-modules will need to be properly registered or else they may fail.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Replies are listed 'Best First'.
Re: Moving Perl from test to Dev
by Abigail-II (Bishop) on Nov 20, 2003 at 20:26 UTC
    The only adminny thingies I've ever done on a Windows machine are 1) setting an IP address and 2) asking someone to install Cygwin for me.

    You've given me another reason to keep it that way.

    Abigail

[reply]
Re: Re: Re: Moving Perl from test to Dev
by welchavw (Pilgrim) on Nov 21, 2003 at 15:48 UTC

    Hmmm....I have never hit any problems in this regard. My understanding is that DLLs will never need to be "registered" unless they do OLE-ish kinds of things. My guess is that I have never needed to use any OLE-ish perl DLLs on Win32. I copy perl installations around to different Win32 hosts quite frequently and run reloc_perl and its been all smooth sailing. Are you just guessing that various modules will fail or can you cite examples? I would be interested to know what you have found necessary to avoid.

    ,welchavw

[reply]
      A good point you have here.

      As long as all the DLL's are in the perl-tree and are "dynaloaded" it will work, but I can imagine that some modules might put the DLL's elsewhere and then simply copying the perl-tree will not work.

      I was thinking of things like expat or sablotron which use their own dll's in their own folders and with which I had no end of trouble getting them to run after I upgraded my perl-installation.

      CountZero

      "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

[reply]

In Section Seekers of Perl Wisdom