AM,
>> Your perl build options should be of little consequence
As glue for IM, the Perl should make little difference. But to change
the guts of Perl itself by making libperl.so instead of libperl.a,
everything else I do with Perl will pay the ~20% penalty for being a
shared object.
Is there any way that I can use the shared Perl just for PerlMagick,
use the standard, static Perl for everything else and keep just 1 set
CPAN modules (~50 bleepin modules I had to rebuild with new machine)
Or, would I have to do parallel maintenance?
Third option? Force a static link on PerlMagick and live with a 20MB
Perl_The_Hutt?
BORING STATIC VS SHARED TRIVIA SECTION:
==========================================
I have both libperl.a and libperl.so built the same except for sharedness
Ldd confirms that their guts are identical except for 1 file:
ldd `find /usr/local/bin -name perl` | psr "s/\(.*//" | freq -s
libperl.so => /usr/local/bin/im/lib/perl5/5.22.1/x86_64-linux/CORE/lib
+perl.so
/usr/local/bin/im/perl:
/usr/local/bin/perl:
The total size too is interesting, .a is 2 MB fatter:
lsr -s `bloc -s libperl. | grep 5.22`
/usr/local/bin/im/lib/perl5/5.22.1/x86_64-linux/CORE/libperl.so 20018
+56
/usr/local/lib/perl5/5.22.1/x86_64-linux/CORE/libperl.a 30494
+58
The size of the .so version of Perl too looks tiny, on the surface:
lsr -s `find /usr/local/bin -name perl`
/usr/local/bin/im/perl 17400
/usr/local/bin/perl 1887720
add 17400 2001856 -> 2019256; add 2019256 -1887720 -> 131536
The stump and the shared object together, however, are
131 THOUSAND BYTES larger than boring old STATIC PERL!
So, the shameless canard about shared libs saving disk space
and memory has finally been INESCAPABLY DEBUNKED!
They take up more memory, more disk space and they extort a
surcharge against your TIME with every Invocation!