Oops, I meant to remove the Prima email list, though my playing with Prima
motivated this email. Hopefully it's useful chatter for Prima folks as well
as PAR folks. :-)
On Mon, Aug 5, 2013 at 12:04 PM, Roderich Schupp <
roderich.sch...@googlemail.com> wrote:
>
> On Mon, Aug 5, 2013 at 5:43 PM, David Mertens <dcmertens.p...@gmail.com>wrote:
>
>> For example, on a Windows system without jpeg, it throws a runtime
>> exception saying "The application has failed to start because
>> libjpeg-8_.dll was not found..."
>
>
> What --link option did you specify in this case?
>
I had used --link=jpeg for jpeg linking, and similar for png, tiff, Xpm,
etc.
> Where is this DLL located and what was the value of PATH when you ran pp?
>
The command that worked was to specify the whole path with
--link=C:\strawberry\c\bin\libjpeg-8_.dll
and the contents of my %PATH% variable is
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files\QuickTime\QTSystem\;C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin
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".
Actually, I wrote my own script that uses pp.pm, and I appended these full
link arguments to the end of @ARGV before calling pp->go. But of course
it's essentially the same as using the pp executable. Very handy in this
regard, by the way!
> but it is not correctly finding the libraries that I ask it to find with
>> the --lib flag.
>>
>
> The --lib option has nothing to do with your problem, it augments the *
> Perl* *module* search path
> (same as "perl -Ipath ..." does).
>
>
> Cheers, Roderich
>
Oops, yeah, typo on that. I meant to say --link flag.
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
