FROM : Chris
DATE : Fri Nov 05 22:58:06 2004
I worked through a similar issue a couple years ago with some plugin code, but it's been so long that you should take my suggestion with that in mind :)
How about getting the bundle of one of the classes from your PreferencePane and work from that for the path? It's been long enough that I don't recall all the API calls, but you can get the bundle for a class, and then you should be able to get the path for that bundle, from which you can build the path to your framework.
Of course, if there is a better/faster/etc way to do this, I'd like to hear it as well.
Chris
On Friday, November 05, 2004, at 01:13PM, Josh Rooke-Ley <<email_removed>> wrote:
>
>I working on PreferencePane that uses some network code in a framework.
> I don't want to install the framework in /Library/Framworks because
>its really a private framework that shouldn't go there. If I compile
>the framework with the install path as "@executable_path/../Frameworks"
>as recommended for private frameworks, it will point to
>/Applications/System Preferences/Contents/Frameworks. What I'm looking
>for is something like "@bundle_path/Frameworks". ..
>
>Any ideas?
>
>Thanks
>
>josh
>
>_______________________________________________
>MacOSX-dev mailing list
><email_removed>
>http://www.omnigroup.com/mailman/listinfo/macosx-dev
>
>
DATE : Fri Nov 05 22:58:06 2004
I worked through a similar issue a couple years ago with some plugin code, but it's been so long that you should take my suggestion with that in mind :)
How about getting the bundle of one of the classes from your PreferencePane and work from that for the path? It's been long enough that I don't recall all the API calls, but you can get the bundle for a class, and then you should be able to get the path for that bundle, from which you can build the path to your framework.
Of course, if there is a better/faster/etc way to do this, I'd like to hear it as well.
Chris
On Friday, November 05, 2004, at 01:13PM, Josh Rooke-Ley <<email_removed>> wrote:
>
>I working on PreferencePane that uses some network code in a framework.
> I don't want to install the framework in /Library/Framworks because
>its really a private framework that shouldn't go there. If I compile
>the framework with the install path as "@executable_path/../Frameworks"
>as recommended for private frameworks, it will point to
>/Applications/System Preferences/Contents/Frameworks. What I'm looking
>for is something like "@bundle_path/Frameworks". ..
>
>Any ideas?
>
>Thanks
>
>josh
>
>_______________________________________________
>MacOSX-dev mailing list
><email_removed>
>http://www.omnigroup.com/mailman/listinfo/macosx-dev
>
>
| Related mails | Author | Date |
|---|---|---|
| Josh Rooke-Ley | Nov 5, 19:12 | |
| Chris | Nov 5, 22:58 | |
| Mike Davis | Nov 6, 21:28 |






Cocoa mail archive

