[PyInstaller] Confused about --out=path option
Using 2.0 on Mac OSX. When I use the option --out=$HOME/Desktop/scratch what I find in scratch is: drwxr-xr-x 3 original staff 102 Mar 27 13:01 build/ drwxr-xr-x 3 original staff 102 Mar 27 13:01 pyi.darwin/ drwxr-xr-x 11 original staff 374 Mar 27 13:02 myscript/ -rw-r--r-- 1 original staff51618 Mar 27 13:01 out00-Analysis.toc -rw-r--r-- 1 original staff11590 Mar 27 13:02 out00-COLLECT.toc -rw-r--r-- 1 original staff 128 Mar 27 13:01 out00-EXE.toc -rw-r--r-- 1 original staff 1160401 Mar 27 13:01 out00-PKG.pkg -rw-r--r-- 1 original staff 1404 Mar 27 13:01 out00-PKG.toc -rw-r--r-- 1 original staff 1134736 Mar 27 13:01 out00-PYZ.pyz -rw-r--r-- 1 original staff39032 Mar 27 13:01 out00-PYZ.toc -rwxr-xr-x 1 original staff 1194861 Mar 27 13:01 myscript* -rw-r--r-- 1 original staff 9028 Mar 27 13:01 warnppqt.txt drwxr-xr-x 3 original staff 102 Mar 27 13:01 dist/ drwxr-xr-x 83 original staff 2822 Mar 27 13:02 myscript/ all the collected libs and stuff plus... -rwxr-xr-x 1 original staff 1194861 Mar 27 13:01 ppqt* -rw-r--r-- 1 original staff 621 Mar 27 13:01 myscript.spec Several things about this puzzle me. 1) Why is there a build dir here? I did not specify the --build-path= option. There is a build dir back in the cwd where the command ran, and it did receive a logdict*.log file at this time. 2) Why does this scratch/build dir have an extra copy of the executable myscript* ? It's rather large. 3) Is there a reason to retain the .toc, .pkg, and .pyz files after the job is done? They are also rather large. I would file a ticket on this but I am not clear about what the correct behavior should be. (Also what I should document as the expected behavior!) Thanks, Dave Cortesi -- 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 pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[PyInstaller] Further confused about --out=path option with a spec file
Say I have a project folder with source and spec file, but I want to put the bundled app elsewhere. This should do it, cd $PROJECT/src pyinstaller --out=$HOME/scratch ./myscript.spec But the --out option is ignored, the build and dist directories are built in the cwd. Note the --buildpath=path option IS respected (kind of) when used with a spec file. Is there any way to achieve this? One important use-case is when $PROJECT is in one's Dropbox. You would like to not dump a bunch of big binaries, .pyzs and tocs into the Dropbox and have them uploaded to the cloud for no reason. Thanks, Dave Cortesi -- 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 pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [PyInstaller] Further confused about --out=path option with a spec file
As you describe it, I'm confused as well: - never tried these options myself. - they are from time before unified interface pyinstaller.py How should be changed the behavior of these options? - should the --out point to directory where to put .log files, build and dist folders? David Cortesi píše v St 27. 03. 2013 v 13:51 -0700: Say I have a project folder with source and spec file, but I want to put the bundled app elsewhere. This should do it, cd $PROJECT/src pyinstaller --out=$HOME/scratch ./myscript.spec But the --out option is ignored, the build and dist directories are built in the cwd. Note the --buildpath=path option IS respected (kind of) when used with a spec file. Is there any way to achieve this? One important use-case is when $PROJECT is in one's Dropbox. You would like to not dump a bunch of big binaries, .pyzs and tocs into the Dropbox and have them uploaded to the cloud for no reason. Thanks, Dave Cortesi -- 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 pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [PyInstaller] Further confused about --out=path option with a spec file
Martin Zibricky píše v St 27. 03. 2013 v 22:04 +0100: As you describe it, I'm confused as well: - never tried these options myself. - they are from time before unified interface pyinstaller.py How should be changed the behavior of these options? - should the --out point to directory where to put .log files, build and dist folders? - or rename '--out' to '--spec-dir' - directory where to put .spec file if it is created - and '--buildpath' rename to '--build-dir' - directory containing dirs 'build' and 'dist' -- 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 pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
