Add framework to plugin(Bundle)

Question

Created 4w

Replies 1

Boosts 0

Participants 2

I have developed framework and want to use this framework in authplugin which added on same project in different target That plugin target is working fine without framework, once I am adding framework the authplugin is not working

Auth-plugin I am using to change in screen-saver plist

Answered by DTS Engineer in 823566022

AFAIK there’s nothing to stop you from embedding a framework within an authorisation plug-in and then using that framework in your plug-in. However, setting this up can be a challenge. Three things:

Make sure you follow the embedding rules from Placing Content in a Bundle.
You’ll want to use an rpath-relative install name. See the first option in Dynamic Library Identification.
Your plug-in will need to add a new entry to the rpath. It has to be relative to @loader_path, rather than @executable_path, because the latter refers to the main executable loading your plug-in.

Oh, and it should go without saying that your framework must follow the rules for the context in which it’s loaded. For authorisation plug-ins that context is particularly restrictive. For example, a large web view based UI framework is not going to work in this context.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

4w

Accepted Answer

Recommended

AFAIK there’s nothing to stop you from embedding a framework within an authorisation plug-in and then using that framework in your plug-in. However, setting this up can be a challenge. Three things:

Make sure you follow the embedding rules from Placing Content in a Bundle.
You’ll want to use an rpath-relative install name. See the first option in Dynamic Library Identification.
Your plug-in will need to add a new entry to the rpath. It has to be relative to @loader_path, rather than @executable_path, because the latter refers to the main executable loading your plug-in.

Oh, and it should go without saying that your framework must follow the rules for the context in which it’s loaded. For authorisation plug-ins that context is particularly restrictive. For example, a large web view based UI framework is not going to work in this context.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1