I did some Googling and came across http://comments.gmane.org/gmane.comp.python.pyinstaller/1265. Initially I didn't think it was related since Pyinstaller is not giving an OSError, but the user reports the app starts successfully after being run once as an administrator.
If having the support directory in dist is all that's required to ensure pyinstaller-built applications start up successfully, why not make the build process automatically create this directory? On Sat, Dec 4, 2010 at 5:21 PM, Damien Elmes <[email protected]> wrote: > Hi folks, > > I have a user who reports a pyinstaller built app won't start on their > 32bit W7 box. I built the installer on a 64bit W7 installation, and > other W7 users seem to be able to use it without issue (I do not know > if they're using 32 or 64 bit installs). I built it using python2.7 + > pyinstaller 1.5rc1 > > I rebuilt the installer with debugging enabled and asked the user to > report what was shown. They reported: > > 1) Found embedded PKG. > 2) Extracting binaries > 3) manifestpath: C:\Program Files\Anki\Anki.exe.manifest > 4) Activation context created > 5) Activation context activated > 6) C:\Program Files\Anki\python.dll > 7) Manipulating environment > 8) PYTHONPATH=C:/Program Files/Anki > 9) importing modules from CArchive > 10) extracted iu > 11) extracted struct > 12) extracted struct > 13) extracted archive > 14) installing import hooks > 15) outPYZ1.pyz > 16) Running scripts > 17) RC:-1 from win32comgenpy > 18) OK -> app terminates without error message / anything appearing > > Any ideas? > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
