On Monday, January 20, 2014 1:12:06 PM UTC-8, Michael Hipp wrote: > > Hello, > > Does it tell somewhere how to put an option in the .spec file to create a > one-file executable? > > the content of the spec file varies based on --onefile or --onedir (in the pyinstaller or pyi-makefile commands). Once that decision is made, the spec file is stuck with it. To have a choice, you need to make two spec files, one for each.
> Is there somewhere a list of all the things that can go into a .spec file? > > There is I think some reluctance to do that because the spec file is executed code and as such (a) can have any python code you like, and (b) might vary from release to release. They've tried to get away from modifying spec files at all, adding more and more options to the command line. > I've read http://pythonhosted.org/PyInstaller/#using-spec-files but it > seems more like an overview without a lot of detail. > The three use-cases (bundling data files, python options, multiprogram bundles) are detailed. The big thing is understanding the uses of a TOC. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
