I admit that it took me a while to get a grasp on how to get started with the pp utility that's part of PAR::Packer too. Don't know if there's a guide out there or not, but I'll list the steps getting started with 32-bit Perl on Windows. There were some caveats and gotcha's along the way with using 64-bit Perl on Windows with the compiler stuff, but can't remember those details. So, I'll just stick with 32-bit Perl for this post.

The steps above should get you going. Next, just look at the documentation for the pp utility and you'll be on your way.

NOTE: If you're behind a web proxy, you might need to configure the http_proxy setting for the CPAN module or add the http_proxy environment variable to the OS.


In reply to Re: Need help using CPan's pp - PAR Packager by dasgar
in thread Need help using CPan's pp - PAR Packager by OM2

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.