-
Notifications
You must be signed in to change notification settings - Fork 243
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
Building for OS X #96
Comments
To my knowledge (I'm an Integration Engineer who works on Mac but supports Linux and Windows as a general rule) there are no solutions (nothing free if any) like WINE for Mac. For instance Apple didn't even allow using OS X via VM until Lion. I'm fairly certain distributing a VM just so others can compile to Mac is not allowed in Apple's EULA. So I highly doubt this will ever be an option for this project. If anyone knows different I'd love to hear it. |
It makes sense that a full solution would not be possible. I guess I am sort of surprised that, for CLI-only tools with a fairly simple API, some way to cross-compile doesn't exist. It seems like the Darling project, for example, is targeted along these lines... |
My understanding of Darling is that it requires a kernel module to be installed; which would be difficult to do in a dockerised environment |
Thank you @davenquinn, I'd completely forgot about the Darling project. Last time I looked at it there was no GUI support. But it looks like they are making progress in that area. Hopefully they'll nail that and the ease of setup soon. Very promising! 😃 |
Thanks for this time-saving project.!
I'd be interested in having a similar docker-pyinstaller workflow available for OS X compilation, even if it had to pull in large dependencies such as clang. My use case is building a simple command-line python application that should work on every platform. I'd imagine that a cross-compilation step from Docker to OS X could be theoretically possible if something like WINE existed for Mac. Has anyone looked into this?
Compiling on OS X directly is not particularly complicated, fortunately, so it will do for now.
The text was updated successfully, but these errors were encountered: