Question or issue on macOS:
- Script To Generate The Plist For Mac Shortcut
- Script To Generate The Plist For Macbook Pro
- Apple Plist Files
- Script To Generate The Plist For Mac Download
- Open the “org.wso2.am.plist” file in a text editor and copy the following content to the property list (.plist) file. Please replace with path to the product directory.
- Open up your favorite editor on the Mac, I’m going to use Xcode and I’m going to create a script file titled UserCollection.sh. If the typical header information isn’t added automatically by your editor, add it in.
I am developping a simple Python application using a PySide2 GUI. It currently works fine in Windows, Linux and Mac. On Windows, I could use PyInstaller and InnoSetup to build a simple installer. Then I tried to do the same thing on Mac. It soon broke, because the system refused to start the command or the app generated by PyInstaller because it was not correctly signed. And as I am not an apple developper, I cannot sign anything…
After some research, I tried py2app. I can go one step further here. With
I can create a runnable app. Which obviously cannot be ported to a different system because it uses my development folders. And if I use python setup.py py2app the generated program cannot start because py2app did not copy all the required Qt stuff. I tried to add one by one the missing libraries, but on the end the system could not find the plugins and I gave up…
Can someone help me with a recipe to convert a python script or package using a Qt GUI into a portable app on Mac? Ideally, the recipe should say how to use a custom application icon, but this is not required.
As my real package is too large for a SO question I trimmed it down to a minimal reproducible example:
Listing 35-1 demonstrates how to create a new property list file. First, an empty plist file (class property list file) is created. Next, individual property list items (class property list item) of varying type (Boolean, date, list, number, record, string) are added to the file. Open in Script Editor.
And here is the setup.py file used for py2app:
How to solve this problem?
Solution no. 1:
Requirements
Script To Generate The Plist For Mac Shortcut
- works with Python 3.8.5
- macOS 10.15.7 Catalina
- uses PySide2 and py2app
Problems
PySide2
must be added under OPTIONS to the packages list- when running the app then still an error occurs:
Library not loaded: @rpath/libshiboken2.abi3.5.15.dylib, Reason: image not found
Solution
The slightly modified setup.py could look like this:
Additionally, an icon definition and a few plist entries for some basic information have been added.
The whole build is best triggered with a script that could look like this:
Test
Here the screenshot of a test run:
Solution no. 2:
I think what you’re missing is the inclusion of the Python3 Framework in your application bundle. I’ve developed a simple macOS app myself recently, however I wanted to have a little more insight on how to do so, so I did a bit of digging into the actual structure of an application. Basically, you are going to put everything into a normal folder with the name of your application. Call this folder MyApp
. Inside this folder we’ll have another called Contents
. From my understanding, py2app
just takes all of the things that make up your app, and structures them inside of this folder as well as creates an Info.plist
file, which also goes inside of Contents
. So far, here is what you have:
MyApp
-> Contents
-> -> Info.plist
In addition to the Info.plist
file with all of the necessary properties, in your Contents
folder you will have a MacOS
folder and a Resources
folder at minimum. Your issue is that you also need a Frameworks
folder, where you would add the required version of Python.
Now, your app hierarchy should look like:
MyApp
-> Contents
-> -> Info.plist
-> -> MacOS
-> -> Resources
-> -> Frameworks
In the Frameworks
folder, you can put the full Python 3 framework you’re working with to build the app, as well as any site-packages that you require to run the application, and then you can reflect all of those changes in the executable so that you are pointing to the correct installations.
To my understanding, all that’s necessary to make the application functional on MacOS is to ensure that your main executable is placed in the MacOS
folder and points to the Python located in your Frameworks
folder, your icon .icns
file is placed in the Resources
folder, and your Info.plist
file is built.
In order for MacOS to recognize it as a full application, I believe you possibly need to use productbuild
and include a Developer license certificate, but it’s really only necessary if you want the application to be distributed. Otherwise, I just added the extension .app
to MyApp
, which converts it into an application.
Without the above-mentioned license/certificate whatever, it probably won’t recognize that it should find your icon file and add it, so if you open it in Preview, select-all, and copy it, you should be able to right-click on the application, press ‘Get Info’, and paste the icon on top of the current icon in the window to make it display correctly.
EDIT: My resources for learning about making macOS apps:
Solution no. 3:
I have successfully build apps using fbs.
It is intended to build Python+PyQt5 apps (you can also use PySide2) and it should work on Mac OS as well (according to the documentation/tutorial).
Using PyInstaller it failed very often for including PyQt5 dependencies (especially when I was working with pyqtgraph
), but with fbs it works great.
Solution no. 4:
I think the solution to your problem can be found here. First, create a virtual environment and install all modules to the same virtual environment.
Install Qt
framework
Then, install the PySide2
After that,
Build, and install PySide2
and make sure to set the path of QMAKE
that comes with the Qt
installation
Script To Generate The Plist For Macbook Pro
Update
First, make sure that you run your code in the same virtual environment, and to convert it to a standard mac OS app you can use py2app or pyinstaller . Also, try to downgrade your py2app if it is not working with your current version after you follow the same process.
Create setup.py
and you have to create a config file or see this example and include any file that you have
To build the application use
To run the app you have to use this way
If it is work with python setup.py py2app -A
that means that everything is going ok and you need to use
If any things go wrongs please refer to these references1, 2, and 3. Also, there are alternatives ways to convert your app to os.
When you open a workbook with a userform that you create in Excel for Windows you will notice that you think your getting old because the userform will popup very small and you need a optical device. You can copy the code below in the Userform module of your workbook to change the size automatic when you open the userform on a Mac. How do i resize a userform in excel 2011 for mac.
After I read your comment, I tried to see what is the problem and I found this and it may solve the problem or you can use alternatives tools such as bbFreeze
, pyInstaller
or cx_Freeze
Solution no. 5:
If you want to package for OSX, you should either
Create a Brew Tap
This probably makes the most sense for an open source developer
General Instructions https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
- host your code in git (does not need to be GitHub)
- create a Formula (Formula Cookbook)
- fork homebrew-core on GitHub
- add your Formula and create a pull request to get it into the main repo
- support your pull request such that it is completed
Join the Apple Developer Program
This probably makes the most sense for a closed source developer
Overview: https://developer.apple.com/programs/how-it-works/
This program costs 99USD annually, but will allow you to sign your package/final binary and distribute it yourself or on their App Store
After creating your account, here’s a guide for packaging and signing for OSX https://developer.apple.com/forums/thread/128166
Apple Plist Files
- structure your code to support signing (add a build step to copy your work into a clean path to avoid frustrating rework)
% codesign -s <Developer ID Application signing identity> /path/to/code
- pick a storage format (
.zip
,.dmg
,.pkg
) and bundle your application as it