On Mon, Aug 5, 2013 at 12:56 PM, Roderich Schupp <
roderich.sch...@googlemail.com> wrote:
>
> On Mon, Aug 5, 2013 at 6:45 PM, David Mertens <dcmertens.p...@gmail.com>wrote:
>
>>
>> So if it simply scans the files in %PATH% (which I guess is the Windows
>> way of doing this), then it should have found it if it knew to replace
>> "jpeg" with "libjpeg-8_.dll".
>>
>
>
> Yeah, "if it knew". Sorry, PAR::Packer has been designed without AI
> capabilities.
>
> Cheers, Roderich
>
Well, I don't expect AI capabilities, but the docs say "i.e. -l
ncursesmeans the same thing as -l
libncurses.so or -l /usr/local/lib/libncurses.so in most Unixes". I took
this to mean that one of the module tries a number of standard-for-the-OS
names, or at least falls back to some sort of
glob("*$lib*.$shared_extension") or similar.
Do you know which module covers this behavior? I might be able to cook up a
patch, but I don't know the PAR::Packer family of modules very deeply.
Thanks!
David
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." -- Brian Kernighan
