I am trying to get PyInstaller to build an executable of PyInstaller. The end goal of this research is to be able to use PyInstaller to package our codebase with an sqlite database and pyInstaller into one file, so that the code can latter repackage itself with any changes done after the executable has run (e.g. the sqlite database could get updated and we want to bring that back into the exe for the next user).
To do this, I do not know if you need a second PyInstaller location but I am using one in the build:
This builds the pyinstaller/dist/pyinstaller executable fine but the executable will not work and generates the following error when used:
11 INFO: wrote /home/d3y034/pyinstaller-2.0/pyinstaller/dist/testing.spec
32 INFO: UPX is available.
Traceback (most recent call last):
File "<string>", line 91, in <module>
File "<string>", line 86, in main
File "<string>", line 50, in run_build
File "/home/d3y034/pyinstaller-2.0/pyinstaller/build/pyi.linux2/pyinstaller/out00-PYZ.pyz/PyInstaller.build", line 1611, in main
File "/home/d3y034/pyinstaller-2.0/pyinstaller/build/pyi.linux2/pyinstaller/out00-PYZ.pyz/PyInstaller.configure", line 173, in get_config
File "/home/d3y034/pyinstaller-2.0/pyinstaller/build/pyi.linux2/pyinstaller/out00-PYZ.pyz/PyInstaller.configure", line 138, in find_PYZ_dependencies
File "/home/d3y034/pyinstaller-2.0/pyinstaller/build/pyi.linux2/pyinstaller/out00-PYZ.pyz/posixpath", line 120, in dirname
AttributeError: 'NoneType' object has no attribute 'rfind'
Any advice, suggestions, patches, or etc. which would allow us to use PyInstaller in this fashion would be appreciated.
Just to repeat, the idea is we want to be able to package our onefile data (e.g. it is generated in a temporary directory but we will move it to the executable's directory) back into the onefile. Specifically this is so that changes to the code can be made on the fly and repackaged for easy distribution between parties.