Re: Dynamic linking of perl library in Panther vs. Tiger
Re: Dynamic linking of perl library in Panther vs. Tiger
- Subject: Re: Dynamic linking of perl library in Panther vs. Tiger
- From: Sherm Pendley <email@hidden>
- Date: Sun, 24 Apr 2005 13:54:46 -0400
On Apr 24, 2005, at 1:27 PM, Nils Hjelte wrote:
My app links against OS X's perl library, and I start receiving
feedback that the app won't start in Tiger because of the new perl
version included. If I run 'otool -L' on the Panther build I get
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/CORE/
libperl.dylib (compatibility version 5.8.0, current version 5.8.1)
whereas the version in Tiger apparently is 5.8.6.
How do I handle this without distributing the app as two different
binaries (one for Panther, and one for Tiger).
What I do with CamelBones is include a number of binary "support
bundles" with the main framework. Each one of these is built and
linked against a specific version of libperl. These support bundles
entirely hide the libperl API, and expose a public API that is
consistent regardless of the libperl version in use. The main
CamelBones framework examines the host system when it's initialized,
and dynamically loads the correct bundle.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden