I've committed a CamelBones 1.1.0 to Sourceforge's SVN, to tide us
over until we can get the new 2.0 architecture up and running. I'll
let Sherm build the installer package and put that up on the project
page, partly because the installer itself isn't in SVN currently, and
partly because I develop a migraine every time I try to build the
If you feel like playing with the library beforehand, the actual
binaries (minus the aforementioned optional 'kits' the framework can
include) are at http://idisk.mac.com/seattlesparks/Public/CB-1.1.0.zip
-- if you break it, let someone know ASAP, before the final build goes
Worth noting that if you have installed the PerlSDKs image on Snow
Leopard, it /does/ break a symlink which causes Pain And Suffering for
the Snow Leopard compatible CamelBones. If you are running Snow
Leopard and have installed PerlSDKs, you can fix the issue by doing:
sudo rm libperl.dylib
sudo ln -s ../../5.8.9/darwin-thread-multi-2level/CORE/libperl.dylib .
...and then life will be happy again.
For those who are feeling particularly daring and wish to try to build
1.1.0 from source, here's the horrifying process currently involved,
which presently seems to require two machines (thank you, Apple, for
killing legacy SDKs from Xcode 3.2...):
* Machine 1
- Must have the CB developer support package PerlSDKs installed.
* Machine 2
- Snow Leopard
- Must NOT have the CB developer support package PerlSDKs installed
(or at least, you better apply the fix above).
Check out CamelBones from sourceforge, putting it somewhere that both
Machine 1 and Machine 2 can get to. (Removable drive, network drive,
On Machine 1, load CamelBones.xcodeproj, select the target 'All' and
the configuration 'Release' (for the system-wide framework), 'Release-
App-Embedded' (for the embedded-in-an-app framework) or 'Release-Lib-
Embedded' (for the embedded-in-another-framework framework) as
necessary for your needs.
When built, close Xcode on Machine 1.
Open CamelBones.xcodeproj on Machine 2. Select the target 'Snow
Leopard' and the configuration you picked before. Build, and do NOT
clean before building. Wait.
When you are done, you should now have a 'Release' or 'Release-App-
Embedded' or 'Release-Lib-Embedded' directory under CamelBones/build
containing a framework appropriate for your needs.
Alternatively, since the 10.6 bundles are built with the 10.5
framework, if you can get Perl 5.8.9 installed on Leopard alongside
5.8.8 and the PerlSDKs versions of Perl, you MIGHT be able to build
the entire project on one machine. (I have not yet tried this, so I
will not swear to that.)
Whew. I'm going to get some sleep. :)
On Tue, Sep 22, 2009 at 6:14 AM, Terje Bless <link@...> wrote:
>>… here's the horrifying process currently involved, …
> Would this process become any less painful by only supporting 10.5 and 10.6?
Somewhat, but it wouldn't fix the root cause of the horror, which is
the use of the Apple-supplied libperl.
Cocoa programming in Perl: http://camelbones.sourceforge.net