I don't really know a lot about many things yet, but if you downloaded the source (I still have problems going straight from svn) you can do a ./configure --prefix=/somepath before the make, then a make/make install will put it elsewhere. BTW, this is where you can enable --enable-debug as well if you want to use gdb for anything.
I understand about not wanting to mess up Mac's internals. -DJ On Dec 17, 2007 12:11 PM, Jon Brisbin <[EMAIL PROTECTED]> wrote: > I'm trying to learn to write Cocoa/Python apps on my new OS X Leopard > MacBook Pro. I'm traditionally a Java and Web programmer, so I'm not > really in my element here. > > I've downloaded and compiled the sword API, but I haven't installed it > because I think I want to include the .dylib in my project directly, > rather than installing it in my /usr/local, right? Doing a "make > install" on it would break portability, if I'm understanding it right. > > I think my first task is to get the SWORD API built into a Mac OS X > framework. Has anyone done this already? Or do you just link against a > command-line-compiled version of the .dylib? > > First of many questions, I'm sure... > > Thanks! > > Jon Brisbin > http://jbrisbin.com > > > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
