Re: Linking frameworks in a trusted app
Re: Linking frameworks in a trusted app
- Subject: Re: Linking frameworks in a trusted app
- From: Christiaan Hofman <email@hidden>
- Date: Mon, 12 Oct 2009 23:20:41 +0200
On Oct 12, 2009, at 23:08, Paul Middlin wrote: In order to use the accessibility API's, we've followed the examples to make our app trusted. We made a helper app, used the Authentication services to launch it, and called AXMakeProcessTrusted(). Pretty much the same as how google did it:
http://code.google.com/p/command-q/source/browse/trunk/MakeProcessTrustedMain.m
Once trusted, our app won't run because we use some frameworks, like Sparkle. We get this complaint in the crash log:
Dyld Error Message:
Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle
Referenced from: /Users/username/sandbox/OurApp/build/Debug/OurApp.app/Contents/MacOS/OurApp
Reason: unsafe use of @loader_path in /Users/username/sandbox/OurApp/build/Debug/OurApp.app/Contents/MacOS/OurApp with restricted binary
I tried setting the "Install Name" to use @rpath, and then setting the rpath (Runpath Search Paths) to @loader_path/../Frameworks/, but that doesn't work. Well, it works until you mark your app trusted using AxMakeProcessTrusted(), and then it claims it can't find the library anymore.
Ideas? Any other way to get accessibility support for my app without making the user go "enable access for assistive devices" for all apps in the system preferences?
I had heard maybe you can add your app to the accessibility group during install, but didn't find much info on it.
-Paul
Have you tried using @executable_path instead of @loader_path?
Christiaan
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden