On Oct 2, 2010, at 07:59:29, Kyle Sluder wrote:
> On Oct 2, 2010, at 1:57 AM, Rick Mann wrote:
>
>> I do have another question. I will ship my app with a number of built-in
>> plug-ins, but I also want the user to install additional plug-ins, or even
>> write their own. Those plug-ins need to
On Oct 2, 2010, at 1:57 AM, Rick Mann wrote:
> I do have another question. I will ship my app with a number of built-in
> plug-ins, but I also want the user to install additional plug-ins, or even
> write their own. Those plug-ins need to find my app's Framework, both for
> building and execut
Thanks, Ken. Turns out, it was partly that, but the real problem was the
differing working directories, depending on whence the app was launched.
I did find a resource that told me about @executable_path, so I fixed up that
aspect as well.
I do have another question. I will ship my app with a n
On Oct 1, 2010, at 11:52 PM, Rick Mann wrote:
> I have an app that has a framework internally (and some plug-ins). When I
> launch it from Xcode (debugging), everything works fine. But if I launch it
> by double-clicking the icon in the Finder, I get the crash dialog with
> "Library not loaded:
I have an app that has a framework internally (and some plug-ins). When I
launch it from Xcode (debugging), everything works fine. But if I launch it by
double-clicking the icon in the Finder, I get the crash dialog with "Library
not loaded: foo", where foo is the internal framework.
The path t
