On Wednesday, April 4, 2001, at 03:37 PM, Peter Prymmer wrote:
>
> On Wed, 4 Apr 2001, Forest Dean Feighner wrote:
>>
>> This worries me a bit because I get the impression that it'll replace
>> the perl exectutable with PerlMagick.
>
> I do not think that it will replace perl with PerlMagick it will leave
> perl in your default bin directory then add the PerlMagick next to it
> in the same directory. If you had specified:
>
> perl Makefile.PL MAP_TARGET=perl
> make
> make -f Makefile.aperl inst_perl
>
> then that incantation would have made a new binary named 'perl' with the
> Image Magick library statically linked in.
Thanks for the explanation, that helps to clarify things for me.
> The question then becomes "why bother with static linking at all?".
> Perhaps in the case of a graphics intensive thing like Image Magick
> there
> could be some sort of speed advantage. But OS X supports dynamic
> loading
> and you perl should too. What do the following return on your system
> (and
> are you using the system supplied perl or did you build it yourself?):
My impression is that dynamic loading would be the way to go. I had
thought that I might have to go with a static linking due to the use of
the shared graphics libraries.
I am still acclimating to this new environment and am having a hard time
understanding the equivalent to ldconfig -v, etc..
The default perl is installed. perl -v prints This is perl, v5.6.0 built
for darwin
> perl -V:usedl
> perl -V:so
> perl -V:dlsrc
usedl='define';
so='dylib';
dlsrc='dl_dyld.xs';
>> perl Makefile.PL
>> make
>> make install
>>
>
> Ah - OK. That looks better to me (i.e. use dynamic loading). Thanks
> for
> your detailed reply.
Yes, I thought the default would be best.
Thank you for your help. It is appreciated.
Forest
