Re: Including shared libraries
[email protected] (Roderich Schupp)
| Newsgroups | perl.par |
|---|---|
| Message-ID | <CAC9r9zbPT-Jj6dfN2tKNUnz4LQ0=C-6FGeduLLKFdmF=2E4q+w@mail.gmail.com> |
On Sat, Jul 2, 2016 at 3:04 PM, Johan Vromans <[email protected]> wrote: > For example, the functions > abstract out whether the application is running bare (unpackaged, e.g. > during testing and development) or packaged. You could e.g. test for $ENV{PAR_TEMP} to exist. > There are functions to get access to packaged data and so on. PAR has that, too, though - cough - not well documented. Just for the record: The PAR::Tutorial on "Accessing packed files" is wrong in the context of a packed executable. You can get an Archive::Zip object for the packed executable (which is actually a zip with something you don't really want to know stuck in front of it) with my $zip = PAR::par_handle($ENV{PAR_PROGNAME}); Cheers, Roderich