I would suggest a wrapper that is specific to FFmpeg and supports only the options that your app needs to use.Īn even better idea would be to see if you can implement this using a supported Apple API.
#FFMPEG LIBRARY MAC MAC#
Apple requires Mac App Store apps to do something functional and useful without any great area "extras".įrom an implementation standpoint, all of this is much easier than it sounds. At this point, your only remaining hurdle would be to deliver useful functionality in the Mac App Store without the plugin. Or your could develop a more general wrapper that wrap any open-source tool. Your wrapper would have to be GPL to comply with FFmpeg's license. You might be able to do this all in the URL, perhaps via a Universal Link. Then, your sandboxed app could launch that FFmpeg wrapper (via NSWorkspace) and pass any work to be done via your IPC channel.
What I'm saying is that you could wrap FFmpeg in a stand alone app that listens for input via Bonjour or some other IPC. But those restrictions only app to processes that your sandboxed app launches via traditional fork (or fork-like) operations. You would still have technical restrictions due to the sandbox. The GPL is a legal restriction, not a technical one.Īssuming you are talking about the Mac App Store here, Apple explicitly allows plug-ins in the Mac App Store, "Apps distributed via the Mac App Store may host plug-ins or extensions that are enabled with mechanisms other than the App Store." And you could give yourself any kind of temporary exception you want (within reason). 21-05-2021 08:24:00 Mac specific Archiware P5 Archive: Installing ImageMagick & FFmpeg on. You can sandbox your app and distribute it directly. Archive: Installing ImageMagick & FFmpeg on macOS with Homebrew. That would mean that any GPL tool is completely off limits for a sandboxed app (unless the app itself is GPL), which is unfortunate.To clarify a couple of things.įirst of all, the GPL limitation is for the Mac App Store. Is there a path that a binary could be downloaded that can then be executed? It would seem that this is not possible, otherwise I could just copy the binary from /usr/local/bin there. Due to the nature of this particular tool, running it from the sandbox may be challenging. You are just trying one, particularly difficult way.
There is no way to give access to run an external binary from a sandboxed app? (unless it happens to be in one of the system dirs that have an exception).There are a number of ways to run an external binary from a sandboxed app.
0 kommentar(er)
