pyinstaller -onefile -collect-binaries brainstem brainstem_example.

pyinstaller -onefile -collect-binaries.

Based on the current behavior we recommend using the collect binaries option. Acroname has used this solution for many years internally however, there are better solutions such as:Ĭollect all is the most complete, but results in a larger executable and is not required for our package. Then it collects copies of all those files - including the active Python interpreter - and puts them with your script in a single folder, or optionally in a single executable file. It analyzes your code to discover every other module and library your script needs in order to execute. These are great solutions but they require you know exactly where they are located and exactly where they should be placed. PyInstaller reads a Python script written by you. Luckily, PyInstaller has supplied a ton of options to handle these cases. This means that there are external libraires that need to be taken into account when creating a self contained executable. The reason for this is because our Python API is a wrapper around our C API. Acroname’s “brainstem” package is one of these cases. However, there are situations when PyInstaller cannot detect the dependencies of certain modules. Many times pyinstaller can be excuited without any additional commands such as: The benefit being that you won't need to fuss with setting up a python environment. Whatever I seem to do I always end up with plainly readable python source files in /tmp/_MEIxxxxx in the Linux build.If you are not familiar with PyInstaller it is an application that allows you to bundle a python file or project into a single executable by providing a fully encapsulated environment. If I use the -excludes option I end up with a non-working executable. I have tried a lot of options but I am still unable to force PyInstaller to include *.pyc files only. In other words: my source code is plainly readable.Īccording to the documentation in it says only *.pyc files should be included. so files it also includes all python files as *.py and not as *.pyc files. Which is fine and according to the documentation. But on the Linux platform the executable is an extractor which unpacks every file in /tmp/_MEIxxxxx. I use -onefile and -windowed.įor Windows and macOS the executable are single file executables which run as is (or seem to be).

All files I included in the spec file are present just like all library files needed from PyQt5.

The executable works as expected on all three platforms. I build the executable using a spec file I build the executable for Windows, macOS and Linux. It uses PyQt5, a few binary files and 20+ python source files. I am building a Linux application in Python.

Py installer