Thread: [Camelbones-devel] CVS: Embedded makefile targets
Brought to you by:
shermpendley
From: Sherm P. <sh...@do...> - 2005-03-20 04:44:27
|
My earlier comments about embedded framework make file targets being incomplete lit a fire under me to fix 'em - so I did, and checked the changes in. Here's how to build from CVS: a. Check out the source and cd to the CamelBones directory. (duh, no kidding) b. ./configure Usable options for configure: --enable-debug By default, debugging symbols are stripped from the built framework. If you use this, they won't be. (Be careful not to ship a framework with your app that's been built this way - it's huge!) --enable-embedded By default, a shared framework is built and installed to /Library/Frameworks, and a Perl module installed to wherever the Perl you're building against keeps its CPAN modules. With this option, the framework is configured with the correct install_name to allow for embedding it in an .app bundle. The framework will be installed into /Developer/CamelBones/Frameworks. Xcode projects that use it will need to add a "copy files" build phase to the relevant target, to copy the framework into that target's Frameworks/ subdirectory. The Perl module is installed into the architecture-specific support bundle inside the framework that matches the Perl you're building against. --with-perl=/path/to/bin/perl By default, /usr/bin/perl is queried to determine the appropriate paths for libperl and headers to use when building. With this option, you can specify a different Perl to build against. There are some other options listed in configure --help, but they're not yet implemented. c. make d. make test This will run the CPAN module's self-tests. Hopefully they all pass. e. sudo make install Copies everything into place. Just what that place is will depend on whether you're building a shared or an embedded module - see above. sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org |
From: Andrew S. <an...@sw...> - 2005-03-23 05:44:39
|
On Sat, 19 Mar 2005, Sherm Pendley wrote: > My earlier comments about embedded framework make file targets being > incomplete lit a fire under me to fix 'em - so I did, and checked the > changes in. > > Here's how to build from CVS:... [snip] This worked great with the exception that I had to $ sudo mkdir -p /Developer/CamelBones/Frameworks prior to 'sudo make install' configured to enable an embedded framework. Otherwise I got: $ sudo make install cd CPAN ;\ make install Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Writing ///Library/Perl/5.8.1/darwin-thread-multi-2level/auto/CamelBones/.packlist Appending installation info to ///System/Library/Perl/5.8.1/darwin-thread-multi-2level/perllocal.pod cp AppMain.h CamelBones.h CBPerl.h CBPerlArray.h CBPerlHash.h CBPerlObject.h CBPerlScalar.h Conversions.h DylibInit.h Globals.h NativeMethods.h PerlImports.h PerlMethods.h Runtime.h Structs.h Wrappers.h CamelBones.framework/Headers cp typemap CBDummyModule.pm AppKitGlobalStrings.plist FoundationGlobalStrings.plist CamelBones.framework/Resources cp Info.plist CamelBones.framework/Resources cd CPAN ;\ make cp -r CamelBones.framework /Developer/CamelBones/Frameworks; \ find /Developer/CamelBones/Frameworks/CamelBones.framework -name 'CVS' | xargs rm -rf cp: /Developer/CamelBones/Frameworks: No such file or directory find: /Developer/CamelBones/Frameworks/CamelBones.framework: No such file or directory -- Andrew B. Sweger -- The great thing about multitasking is that several things can go wrong at once. |
From: Sherm P. <sh...@do...> - 2005-03-24 01:41:17
|
On Mar 23, 2005, at 12:44 AM, Andrew Sweger wrote: > On Sat, 19 Mar 2005, Sherm Pendley wrote: > >> Here's how to build from CVS:... [snip] > > This worked great with the exception that I had to > > $ sudo mkdir -p /Developer/CamelBones/Frameworks > > prior to 'sudo make install' configured to enable an embedded > framework. Fixed in CVS. Also in CVS, a new configure option: "--enable-prebinding". This does just what you'd think it would - it creates a prebound framework. It's not really as useful as you might think, though - it requires a prebound libperl, and it doesn't make a noticeable difference in startup times, at least as far as I could tell. sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org |