-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for bundling XPC Services #24
Comments
Would you be able to provide an example xcode project with an xpc service so that I can see how the resulting app bundle should look? I haven’t worked with xpc services before so I don’t know how they work. |
I've started my project using https://github.com/rderik/XPCSquirrel as a template. The resulting app folder looks like this:
Happy to provide more information if you need it. |
Thanks, that should be enough info for now 👍 Once I've gotten very basic iOS support working (a sponsor wants that) I'll try implementing support for XPC services. Basic iOS support isn't too far away so you shouldn't have to wait too long :) |
I'm finally working on Swift Bundler again after not really working on it much at all for probably over 6 months. The early access version currently has support for expressing any possible plist entries in the configuration file. I will be merging the early access version into this repo soon after a few more improvements. After that I'll be looking into supporting a big chunk of the kinds of Apple-specific app content that Xcode supports (iMessage extensions, XPC services, etc.) |
I would like to use swift-bundler to create an app that includes an XPC Service. For that the resulting
.app
directory needs to contain a directoryContents/XPXServices
which in turn contains.xpc
bundles.A first step to make this possible would be to support dictionaries dictionaries as additional plist entries:
results in
Given this I could already add a manual step that adds my ServiceProvider to the already created bundle.
The text was updated successfully, but these errors were encountered: