I have implemented options --specpath where to create .spec file --distpath where to put final app --workpath where to put temporary files (.toc, .pkg, etc.)
in my fork: https://github.com/matysek/pyinstaller PyInstaller now also ignores full paths in the .spec files and uses just basenames. name=os.path.join('build', 'pyi.win32', 'exename.exe') -> name = 'exename.exe' name=os.path.join('dist', 'exename.exe'), -> name = 'exename.exe' name=os.path.join('dist', 'appname-dir') -> name='appname-dir' I would appreciate any testing or feedback. 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. -- 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.
