For any modules installed into the @INC directories (including all standard modules), there should be no migration problem whatsoever. For any modules you've put in other places, there's really nothing for it but to find all the use lib statements and convert 'em. Fortunately for you, there's this programming language that's pretty good at that sort of thing ... =)

One way: First decide where you're going to put your libraries on the Unix-type system. Use a hash as a translation table, where the keys are windows directories and the values are your *nix correlates of those directories. That should make writing a script that updates all your perl scripts.

In reply to Re: How do I migrate a set of Unix scripts to Windows ActivePERL? by arturo
in thread How do I migrate a set of Unix scripts to Windows ActivePERL? by satchboost

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.