On Oct 30, 2006, at 9:54 AM, Daniel Harple wrote:
I tried this, and it did not work. It is complicated to setup, however, so I may have made an error.
Solutions:
- Include a script the user must run after installation. The script
would run install_name_tool and change the shared library path of the iTerm framework linked against the Growl.framework to an absolute path. This solution requires the user have the Apple Developer Tools installed.
- Have Allan include Growl.framework with TextMate, and just use
`@exectuable_path` like normal. We would also include the Python/ Perl/Ruby extensions so you actually could use Growl from some of the bundles. I'm not sure how useful that would be, but it could be interesting for longer running commands.
Or you could use NSBundle to dynamically load the framework. You would probably want a bootstrap loader that TM would load and then it would load Growl, iTerm and your real code in the proper order.
Likely easier than requiring scripts or doing (2).
b.bum