David Cortesi píše v Ne 24. 02. 2013 v 15:07 -0800: > > Pyinstaller users, in what current working directory do you usually > run it?
> Or, method B: > > cd /path/to/project/src/ > python /path/to/pyinstaller/pyinstaller.py --options... > yourscript.py > > This creates build, dist, and yourscript.spec in /path/to/project/src/ > I'd like to know which method is most popular (or if there's another > way)? I usually use this way - having build/dist/spec in project directory. For manual I would prefer this way because with the next release you will be able to install pyinstaller by 'python setup.py install' and the 'A' way will not be always available. > In either case, do you also use an alias, shell script, or makefile to > shorten the command? For manual I would assume that: - 'python setup.py install' will create shell script pyinstaller on linux and pyinstaller.exe on windows. - there is always available command 'pyinstaller' in your PATH - refer in manual to PyInstaller command as 'pyinstaller' - and add a note that when PyInstaller is not installed and used from the extracted tarball - 'pyinstaller' refers to script 'pyinstaller.py' and in that case you need to substitute it with 'python pyinstaller.py'. -- 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.
