Yikes. Your plan will require that end-users have 'pod2html' available to them, and that you can feed pod2html the original perl scripts which made your pp executable. And avoid hard-coded paths!
Instead, if you really want to internally pack your documentation so you only need to ship one executable file, I would suggest you run pod2html yourself, and stuff that into a __DATA__ block in one of the compiled script files. Then your --makedoc command can regurgitate that stuff into .html files directly.
I haven't used pp much; maybe it can even include various non-Perl files which are required by the executable. Then you wouldn't even need a __DATA__ hack to include the html content.
--
[ e d @ h a l l e y . c c ]
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.