I'm trying to use pp to build an executable that contains a data file from which it reads.

Here's the command I'm using:

pp -v=3 -a /Users/chap/private/dict/lex.dict -o ppdir/brillig brillig

Verbose output includes the line:

adding /Users/chap/private/dict/lex.dict as Users/chap/private/dict/lex.dict
The pp documentation of the -a switch is as follows:
-a, --addfile=FILE|DIR Add an extra file into the package. If the file is a directory, recursively add all files inside that directory, with links turned into actual files.

By default, files are placed under / inside the package with their original names. You may override this by appending the target filename after a ; like this: % pp -a "old_filename.txt;new_filename.txt"

I don't understand the bolded sentence. What path should my Perl code use to access lex.dict?

Thanks!

In reply to pp (PAR-Packer) - how to access included data files by ibm1620

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.