And as a little extra bit of info, if I build with pyinstaller as snagged from your development branch as of 2/19/2013, I don't have any problems; I can run the "app" and it works, because MEIPASS2 is being set correctly.
On Wed, Apr 10, 2013 at 9:12 AM, Daniel Hyams <[email protected]> wrote: > No options to pyinstaller; used the spec file at the bottom of this email. > > What I found out just now, is that after the build is done (with the > current pyinstaller/develop branch), there are two directories formed: > > dist/SampleMacApp > dist/SampleMacApp.app > > If I run the executable in the SampleMacApp directory, it works fine. If > I run dist/SampleMacApp.app by double clicking it, I get junk in the > MEIPASS2 variable. Same thing happens if I cd into > dist/SampleMacApp.app/Contents/MacOS and try to run the executable directly. > > I'm not saying yet that the problem is with pyinstaller; it may still be > caused by me with an improper git checkout somehow, but it would help a lot > if someone with a mac could try to package up the below and run it, to see > how things go. > > > SCRIPT (sample_macapp.py): > > import sys > print sys.argv > > > SPEC FILE: > > # -*- mode: python -*- > a = Analysis(['sample_macapp.py'], > > pathex=['/Users/macapple/Dropbox/CurveExpertPro/src/stuff/MacApp/pyi'], > hiddenimports=[], > hookspath=None, > runtime_hooks=None) > pyz = PYZ(a.pure) > exe = EXE(pyz, > a.scripts, > exclude_binaries=1, > name=os.path.join('build/pyi.darwin/SampleMacApp', > 'SampleMacApp'), > debug=True, > strip=None, > upx=True, > console=False ) > coll = COLLECT(exe, > a.binaries, > a.zipfiles, > a.datas, > strip=None, > upx=True, > name=os.path.join('dist', 'SampleMacApp')) > app = BUNDLE(coll, > name=os.path.join('dist', 'SampleMacApp.app')) > > > > On Wed, Apr 10, 2013 at 7:59 AM, Martin Zibricky > <[email protected]>wrote: > >> Daniel Hyams píše v St 10. 04. 2013 v 07:25 -0400: >> > Hmm, this definitely seems to be a problem on my end. In answer to a >> > couple of the questions above, yes, it was on the latest develop >> > branch without any of my changes. But, when I run the test suite, >> > everything works fine. I'll keep working on it to see what might have >> > happened. >> >> What options for pyinstaller do you use? >> The test suite uses only a subset of them. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "PyInstaller" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/pyinstaller?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > Daniel Hyams > [email protected] > -- Daniel Hyams [email protected] -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
