Hello Jon,<br><br>Not sure if this will help or not but on a related note, someone made available Sword 1.5.7a via MacPorts (<a href="http://trac.macports.org/projects/macports/browser/trunk/dports/textproc/sword/Portfile">
http://trac.macports.org/projects/macports/browser/trunk/dports/textproc/sword/Portfile</a>) along with a number of modules. Unfortunately, this has not been maintained. It would be nice to get this port updated for 1.5.10
. <br><br>MacPorts seems to be a good way of making available software that needs to be built and installed for OS X. By default, it installs into /opt/local to keep away from anything manually built and installed into /usr/local.
<br><br>-Bill<br><br><div class="gmail_quote">On Dec 17, 2007 2:11 PM, Jon Brisbin <<a href="mailto:jon@jbrisbin.com">jon@jbrisbin.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm trying to learn to write Cocoa/Python apps on my new OS X Leopard<br>MacBook Pro. I'm traditionally a Java and Web programmer, so I'm not<br>really in my element here.<br><br>I've downloaded and compiled the sword API, but I haven't installed it
<br>because I think I want to include the .dylib in my project directly,<br>rather than installing it in my /usr/local, right? Doing a "make<br>install" on it would break portability, if I'm understanding it right.
<br><br>I think my first task is to get the SWORD API built into a Mac OS X<br>framework. Has anyone done this already? Or do you just link against a<br>command-line-compiled version of the .dylib?<br><br>First of many questions, I'm sure...
<br><br>Thanks!<br><br>Jon Brisbin<br><a href="http://jbrisbin.com" target="_blank">http://jbrisbin.com</a><br><br></blockquote></div>