Building the Camel
Fetch the code
Download the latest source from CVS, as described in CVS.
Configure
CamelBones uses an autoconf-generated "configure" script that examines your system and figures out the options needed to build. In the simplest case, you can simply navigate to the source directory and run the script without any options, like this:
cd CamelBones
./configure
There are several options available for running "configure":
- --with-perl=/path/to/perl
- By default, CamelBones is compiled and linked to the
Perl that's installed as "/usr/bin/perl" Use this option to
build against a different one.
- --with-libperl=/path/to/libperl
- This was added to support building under GNUstep on
Debian GNU/Linux. See the "Building under GNUstep" section
below.
- --enable-embedded
- By default, a shared framework will be built in
/Library/Frameworks, and a Perl module in the correct
location for the Perl you're building against. Using this
option configures the build to create an embeddable
framework. It is installed in
/Developer/CamelBones/Frameworks, and applications that are
built with it must copy it into their own Frameworks/
sub-directories with a "copy files" build phase.
- --enable-debug
- By default, debugging symbols are stripped from the built framework. Use this to suppress that and keep them. Be careful of using this with --enable-embedded - a framework that's built with debugging symbols included is huge. You probably don't want to embed such a beast into your app.
Build and Install
Run "make" to build the camel. If that succeeds, proceed with "sudo make install" to install it.
If "make" fails with an error for any reason, stop. Don't bother trying to install in hopes that the error isn't important, or that it might somehow "fix itself". It won't. Figure out why it failed - ask for help if you need it.
Building under GNUstep
The latest CVS version of CamelBones builds under GNUstep. For the most part the procedure is identical, but there is one key difference: The CPAN module is not built at the same time as the framework; an additional step is needed. After the framework is installed, "cd CPAN", and build/test/install the module with the usual procedure - "perl Makefile.PL; make; make test; sudo make install".
Not all of the CPAN module's self tests currently pass, and those that do pass emit warnings. I'm working on that.
Debian GNU/Linux doesn't keep its libperl in the "CORE" directory, nor is it simply named "libperl.so", as it is on many systems. To address that, use the "--with-libperl" switch mentioned above, like this
./configure --with-libperl=/usr/lib/libperl.so.5.8