-
Notifications
You must be signed in to change notification settings - Fork 30
Executable build with PyInstaller #23
Comments
For what it's worth, the Mac version runs on Catalina, too. But I don't have a database set up on my laptop or plan files to test it with. |
Here is my .spec file for MS Windows. Successful compilation on my PC with Windows 7 Enterprise Service Pack 1. Intel Core i5. I couldn't catch the text of the terminal because I can't get it to stay open, but below is a screen shot of the ouput. Looks like PyInstaller is saving some absolute paths instead of relative?
|
I since added my venv to datas, still getting an error. @mchamberland I wonder if the uploaded binary only worked on your mac because you already had the appropriate python libraries installed? |
Success!! Will try to post an executable tomorrow along with a version update. I should have read the output more closely. The issue is sklearn. I edited sklearn hooks per this post And also had to downgrade scikit-learn to 0.21.
I think the "reference" to user folder of my compiling PC is actually a hard-coded string of a warning output, not that the executable is trying to access that file path. I also upgraded pip to latest dev and used setuptools==44.0.0. Will have to test if sklearn is the only issue. PyInstaller and setuptools==45.0.0 aren't playing well together: pypa/setuptools#1963 Next step is to see if there are ways to trim down the included libraries and get the executable file size smaller? |
Scipy is a big culprit if you don't need it but I am sure it's a required dependency for scikit-learn.
… On Jan 16, 2020, at 18:59, Dan Cutright ***@***.***> wrote:
Success!! Will try to post an executable tomorrow along with a version update.
I should have read the output more closely. The issue is sklearn.
I edited sklearn hooks per this post
And also had to downgrade scikit-learn to 0.21.
scikit-learn==0.22.1 doesn't work with DVHA at all
scikit-learn==0.22 didn't work with pyinstaller==3.6
I think the "reference" to user folder of my compiling PC is actually a hard-coded string of a warning output, not that the executable is trying to access that file path.
I also upgraded pip to latest dev and used setuptools==44.0.0. Will have to test if sklearn is the only issue. PyInstaller and setuptools==45.0.0 aren't playing well together: pypa/setuptools#1963
Next step is to see if there are ways to trim down the included libraries and get the executable file size smaller?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes, unfortunately. I also use it for PTV distance calculations. |
I was able to trim 20MB from bokeh per my post over on bokeh's community page |
I still plan to try reducing executable size, but since the executables appear to be working I'm closing the issue. |
I'm adding this partially to help me remember what I've done, and partially in hopes that someone with more experience out there might be able to help.
I think I have successfully compiled DVHA for macOS Mojave. You can give this a try by downloading DVHA_macOS_Mojave.zip on the releases page - or directly download with this hard link to 0.6.3 (+ minor fixes) here. Your browser may automatically unzip this file which contains a single app, double click to run. You may need to enable this app in System Preferences -> Security & Privacy -> Open Anyway.
Here is the Pyinstaller spec file I used:
For MS Windows, I've successfully packaged an executable that works on my PC, but no one else's... so I suspect there's some more dll files I'm missing. I also ran into issues with SciPy because it moved its dll files, but I got around this by downgrading SciPy by one version. I'll post my MSW spec file on Monday (I left it at work).
The text was updated successfully, but these errors were encountered: