Wouldn't you have to put the native shared library (.so, .dylib, what-ev) in a shoes accessible libload path? Its the back door to madness IMO, totally non portable, but sometimes setting the environment LD_LIBRARY_PATH properly won't screw up everything else on your system as well. Once bitten (Solaris and gnu-libc so long ago), I won't ever play with the Library path, ever again. It's a clue.
On Sat, 2008-07-05 at 16:47 +1000, Bluebie, Jenna wrote: > Okay, that didn't work. It crashes shoes. I guess shoes has a > different ruby version than the one Leopard's gems compiled json gem > against. Thats just great. :/ > > No native extensions can work in leopard shoes, if i'm right, even if > you manually shove the gem stuff in the +gems folder yourself. > Luckily, json has a pure ruby (slower) implementation I can hopefully > use instead for now.