当前位置:   article > 正文

pyinstall exe打包详解

pyinstall

在学习和工作之中,想制作一些小工具,用python秃了一个晚上,拿到公司,发现要安装python才能用,看别人的博客看不懂,别急,一篇搞定。

一、pyinstaller安装

pyinstaller 是一个python库,和其他库一样,可以用pip 进行导入。

pip install pyinstaller

pyinstaller可以打包python程序变为exe,像其他程序一样,让其可以在任何windows下正常运行而无需python的解析。

pyinstaller有很多参数,可以用-H参数查看帮助

  1. pyinstaller -h
  2. usage: pyinstaller [-h] [-v] [-D] [-F] [--specpath DIR] [-n NAME]
  3. [--add-data <SRC;DEST or SRC:DEST>]
  4. [--add-binary <SRC;DEST or SRC:DEST>] [-p DIR]
  5. [--hidden-import MODULENAME]
  6. [--collect-submodules MODULENAME]
  7. [--collect-data MODULENAME] [--collect-binaries MODULENAME]
  8. [--collect-all MODULENAME] [--copy-metadata PACKAGENAME]
  9. [--recursive-copy-metadata PACKAGENAME]
  10. [--additional-hooks-dir HOOKSPATH]
  11. [--runtime-hook RUNTIME_HOOKS] [--exclude-module EXCLUDES]
  12. [--key KEY] [--splash IMAGE_FILE]
  13. [-d {all,imports,bootloader,noarchive}]
  14. [--python-option PYTHON_OPTION] [-s] [--noupx]
  15. [--upx-exclude FILE] [-c] [-w]
  16. [-i <FILE.ico or FILE.exe,ID or FILE.icns or "NONE">]
  17. [--disable-windowed-traceback] [--version-file FILE]
  18. [-m <FILE or XML>] [--no-embed-manifest] [-r RESOURCE]
  19. [--uac-admin] [--uac-uiaccess] [--win-private-assemblies]
  20. [--win-no-prefer-redirects]
  21. [--osx-bundle-identifier BUNDLE_IDENTIFIER]
  22. [--target-architecture ARCH] [--codesign-identity IDENTITY]
  23. [--osx-entitlements-file FILENAME] [--runtime-tmpdir PATH]
  24. [--bootloader-ignore-signals] [--distpath DIR]
  25. [--workpath WORKPATH] [-y] [--upx-dir UPX_DIR] [-a]
  26. [--clean] [--log-level LEVEL]
  27. scriptname [scriptname ...]
  28. positional arguments:
  29. scriptname Name of scriptfiles to be processed or exactly one
  30. .spec file. If a .spec file is specified, most options
  31. are unnecessary and are ignored.
  32. optional arguments:
  33. -h, --help show this help message and exit
  34. -v, --version Show program version info and exit.
  35. --distpath DIR Where to put the bundled app (default: ./dist)
  36. --workpath WORKPATH Where to put all the temporary work files, .log, .pyz
  37. and etc. (default: ./build)
  38. -y, --noconfirm Replace output directory (default:
  39. SPECPATH\dist\SPECNAME) without asking for
  40. confirmation
  41. --upx-dir UPX_DIR Path to UPX utility (default: search the execution
  42. path)
  43. -a, --ascii Do not include unicode encoding support (default:
  44. included if available)
  45. --clean Clean PyInstaller cache and remove temporary files
  46. before building.
  47. --log-level LEVEL Amount of detail in build-time console messages. LEVEL
  48. may be one of TRACE, DEBUG, INFO, WARN, ERROR,
  49. CRITICAL (default: INFO).
  50. What to generate:
  51. -D, --onedir Create a one-folder bundle containing an executable
  52. (default)
  53. -F, --onefile Create a one-file bundled executable.
  54. --specpath DIR Folder to store the generated spec file (default:
  55. current directory)
  56. -n NAME, --name NAME Name to assign to the bundled app and spec file
  57. (default: first script's basename)
  58. What to bundle, where to search:
  59. --add-data <SRC;DEST or SRC:DEST>
  60. Additional non-binary files or folders to be added to
  61. the executable. The path separator is platform
  62. specific, ``os.pathsep`` (which is ``;`` on Windows
  63. and ``:`` on most unix systems) is used. This option
  64. can be used multiple times.
  65. --add-binary <SRC;DEST or SRC:DEST>
  66. Additional binary files to be added to the executable.
  67. See the ``--add-data`` option for more details. This
  68. option can be used multiple times.
  69. -p DIR, --paths DIR A path to search for imports (like using PYTHONPATH).
  70. Multiple paths are allowed, separated by ``';'``, or
  71. use this option multiple times. Equivalent to
  72. supplying the ``pathex`` argument in the spec file.
  73. --hidden-import MODULENAME, --hiddenimport MODULENAME
  74. Name an import not visible in the code of the
  75. script(s). This option can be used multiple times.
  76. --collect-submodules MODULENAME
  77. Collect all submodules from the specified package or
  78. module. This option can be used multiple times.
  79. --collect-data MODULENAME, --collect-datas MODULENAME
  80. Collect all data from the specified package or module.
  81. This option can be used multiple times.
  82. --collect-binaries MODULENAME
  83. Collect all binaries from the specified package or
  84. module. This option can be used multiple times.
  85. --collect-all MODULENAME
  86. Collect all submodules, data files, and binaries from
  87. the specified package or module. This option can be
  88. used multiple times.
  89. --copy-metadata PACKAGENAME
  90. Copy metadata for the specified package. This option
  91. can be used multiple times.
  92. --recursive-copy-metadata PACKAGENAME
  93. Copy metadata for the specified package and all its
  94. dependencies. This option can be used multiple times.
  95. --additional-hooks-dir HOOKSPATH
  96. An additional path to search for hooks. This option
  97. can be used multiple times.
  98. --runtime-hook RUNTIME_HOOKS
  99. Path to a custom runtime hook file. A runtime hook is
  100. code that is bundled with the executable and is
  101. executed before any other code or module to set up
  102. special features of the runtime environment. This
  103. option can be used multiple times.
  104. --exclude-module EXCLUDES
  105. Optional module or package (the Python name, not the
  106. path name) that will be ignored (as though it was not
  107. found). This option can be used multiple times.
  108. --key KEY The key used to encrypt Python bytecode.
  109. --splash IMAGE_FILE (EXPERIMENTAL) Add an splash screen with the image
  110. IMAGE_FILE to the application. The splash screen can
  111. display progress updates while unpacking.
  112. How to generate:
  113. -d {all,imports,bootloader,noarchive}, --debug {all,imports,bootloader,noarchive}
  114. Provide assistance with debugging a frozen
  115. application. This argument may be provided multiple
  116. times to select several of the following options.
  117. - all: All three of the following options.
  118. - imports: specify the -v option to the underlying
  119. Python interpreter, causing it to print a message
  120. each time a module is initialized, showing the
  121. place (filename or built-in module) from which it
  122. is loaded. See
  123. https://docs.python.org/3/using/cmdline.html#id4.
  124. - bootloader: tell the bootloader to issue progress
  125. messages while initializing and starting the
  126. bundled app. Used to diagnose problems with
  127. missing imports.
  128. - noarchive: instead of storing all frozen Python
  129. source files as an archive inside the resulting
  130. executable, store them as files in the resulting
  131. output directory.
  132. --python-option PYTHON_OPTION
  133. Specify a command-line option to pass to the Python
  134. interpreter at runtime. Currently supports "v"
  135. (equivalent to "--debug imports"), "u", and "W
  136. <warning control>".
  137. -s, --strip Apply a symbol-table strip to the executable and
  138. shared libs (not recommended for Windows)
  139. --noupx Do not use UPX even if it is available (works
  140. differently between Windows and *nix)
  141. --upx-exclude FILE Prevent a binary from being compressed when using upx.
  142. This is typically used if upx corrupts certain
  143. binaries during compression. FILE is the filename of
  144. the binary without path. This option can be used
  145. multiple times.
  146. Windows and Mac OS X specific options:
  147. -c, --console, --nowindowed
  148. Open a console window for standard i/o (default). On
  149. Windows this option has no effect if the first script
  150. is a '.pyw' file.
  151. -w, --windowed, --noconsole
  152. Windows and Mac OS X: do not provide a console window
  153. for standard i/o. On Mac OS this also triggers
  154. building a Mac OS .app bundle. On Windows this option
  155. is automatically set if the first script is a '.pyw'
  156. file. This option is ignored on *NIX systems.
  157. -i <FILE.ico or FILE.exe,ID or FILE.icns or "NONE">, --icon <FILE.ico or FILE.exe,ID or FILE.icns or "NONE">
  158. FILE.ico: apply the icon to a Windows executable.
  159. FILE.exe,ID: extract the icon with ID from an exe.
  160. FILE.icns: apply the icon to the .app bundle on Mac
  161. OS. Use "NONE" to not apply any icon, thereby making
  162. the OS to show some default (default: apply
  163. PyInstaller's icon)
  164. --disable-windowed-traceback
  165. Disable traceback dump of unhandled exception in
  166. windowed (noconsole) mode (Windows and macOS only),
  167. and instead display a message that this feature is
  168. disabled.
  169. Windows specific options:
  170. --version-file FILE Add a version resource from FILE to the exe.
  171. -m <FILE or XML>, --manifest <FILE or XML>
  172. Add manifest FILE or XML to the exe.
  173. --no-embed-manifest Generate an external .exe.manifest file instead of
  174. embedding the manifest into the exe. Applicable only
  175. to onedir mode; in onefile mode, the manifest is
  176. always embedded, regardless of this option.
  177. -r RESOURCE, --resource RESOURCE
  178. Add or update a resource to a Windows executable. The
  179. RESOURCE is one to four items,
  180. FILE[,TYPE[,NAME[,LANGUAGE]]]. FILE can be a data file
  181. or an exe/dll. For data files, at least TYPE and NAME
  182. must be specified. LANGUAGE defaults to 0 or may be
  183. specified as wildcard * to update all resources of the
  184. given TYPE and NAME. For exe/dll files, all resources
  185. from FILE will be added/updated to the final
  186. executable if TYPE, NAME and LANGUAGE are omitted or
  187. specified as wildcard *. This option can be used
  188. multiple times.
  189. --uac-admin Using this option creates a Manifest that will request
  190. elevation upon application start.
  191. --uac-uiaccess Using this option allows an elevated application to
  192. work with Remote Desktop.
  193. Windows Side-by-side Assembly searching options (advanced):
  194. --win-private-assemblies
  195. Any Shared Assemblies bundled into the application
  196. will be changed into Private Assemblies. This means
  197. the exact versions of these assemblies will always be
  198. used, and any newer versions installed on user
  199. machines at the system level will be ignored.
  200. --win-no-prefer-redirects
  201. While searching for Shared or Private Assemblies to
  202. bundle into the application, PyInstaller will prefer
  203. not to follow policies that redirect to newer
  204. versions, and will try to bundle the exact versions of
  205. the assembly.
  206. Mac OS specific options:
  207. --osx-bundle-identifier BUNDLE_IDENTIFIER
  208. Mac OS .app bundle identifier is used as the default
  209. unique program name for code signing purposes. The
  210. usual form is a hierarchical name in reverse DNS
  211. notation. For example:
  212. com.mycompany.department.appname (default: first
  213. script's basename)
  214. --target-architecture ARCH, --target-arch ARCH
  215. Target architecture (macOS only; valid values: x86_64,
  216. arm64, universal2). Enables switching between
  217. universal2 and single-arch version of frozen
  218. application (provided python installation supports the
  219. target architecture). If not target architecture is
  220. not specified, the current running architecture is
  221. targeted.
  222. --codesign-identity IDENTITY
  223. Code signing identity (macOS only). Use the provided
  224. identity to sign collected binaries and generated
  225. executable. If signing identity is not provided, ad-
  226. hoc signing is performed instead.
  227. --osx-entitlements-file FILENAME
  228. Entitlements file to use when code-signing the
  229. collected binaries (macOS only).
  230. Rarely used special options:
  231. --runtime-tmpdir PATH
  232. Where to extract libraries and support files in
  233. `onefile`-mode. If this option is given, the
  234. bootloader will ignore any temp-folder location
  235. defined by the run-time OS. The ``_MEIxxxxxx``-folder
  236. will be created here. Please use this option only if
  237. you know what you are doing.
  238. --bootloader-ignore-signals
  239. Tell the bootloader to ignore signals rather than
  240. forwarding them to the child process. Useful in
  241. situations where for example a supervisor process
  242. signals both the bootloader and the child (e.g., via a
  243. process group) to avoid signalling the child twice.

作者常用的有[--onefile]、[-w]和[-i],这三个参数的作用分别是

1.将py只打包成一个exe文件

2.可以将命令行隐藏,在有GUI的程序里非常管用,可以把黑窗隐藏,让程序变的美观(如果没有GUI,建议不要使用该参数)

3.可以自定义图标

以下全是干货

PyInstaller 工具的命令语法如下:

pyinstaller 选项 选项的参数

不管这个 Python 应用是单文件的应用,还是多文件的应用,只要在使用 pyinstaller 命令时编译作为程序入口的 Python 程序即可。

PyInstaller工具是跨平台的,它既可以在 Windows平台上使用,也可以在 Mac OS X 平台上运行。在不同的平台上使用 PyInstaller 工具的方法是一样的,它们支持的选项也是一样的。

下面先创建一个 app 目录,在该目录下创建一个 app.py 文件,文件中包含如下代码:

  1. print('程序开始执行')
  2. print('孙悟空')

接下来使用命令行工具进入到此 app 目录下,执行如下命令:

pyinstaller --onefile app.py

执行上面命令,将看到详细的生成过程。当生成完成后,将会在此 app 目录下看到多了一个 dist 目录,并在该目录下看到有一个 app.exe 文件,这就是使用 PyInstaller 工具生成的 EXE 程序。

在命令行窗口中进入 dist 目录下,在该目录执行 app.exe ,将会看到该程序生成如下输出结果:

程序开始执行
孙悟空

由于该程序没有图形用户界面,因此如果读者试图通过双击来运行该程序,则只能看到程序窗口一闪就消失了,这样将无法看到该程序的输出结果。

在上面命令中使用了--onefile 选项,该选项指定生成单独的 EXE 文件,因此,在 dist 目录下生成了一个单独的大约为 6MB 的 app.exe 文件(在 Mac OS X 平台上生成的文件就叫 app,没有后缀);与 -F(--onefile) 选项对应的是 -D 选项(默认选项),该选项指定生成一个目录(包含多个文件)来作为程序。

下面先将 PyInstaller 工具在 app 目录下生成的 build、dist 目录删除,并将 app.spec 文件也删除,然后使用如下命令来生成 EXE 文件。

pyinstaller -D app.py

执行上面命令,将看到详细的生成过程。当生成完成后,将会在 app 目录下看到多了一个 dist 目录,并在该目录下看到有一个 app 子目录,在该子目录下包含了大量 .dll 文件和 .pyz 文件,它们都是 app.exe 程序的支撑文件。在命令行窗口中运行该 app.exe 程序,同样可以看到与前一个 app.exe 程序相同的输出结果。

PyInstaller 不仅支持 -F(--onefile)、-D 选项,而且也支持如下表表所示的常用选项。
 

 PyInstaller 支持的常用选项
-h,--help查看该模块的帮助信息
-F,-onefile产生单个的可执行文件,参数为py文件路径。
-D,--onedir产生一个目录(包含多个文件)作为可执行程序,参数为py文件路径。
-a,--ascii不包含 Unicode 字符集支持,无参数。
-d,--debug产生 debug 版本的可执行文件,无参数。
-w,--windowed,--noconsolc指定程序运行时不显示命令行窗口(仅对 Windows 有效),无参数。
-c,--nowindowed,--console指定使用命令行窗口运行程序(仅对 Windows 有效),无参数。
-o DIR,--out=DIR指定 spec 文件的生成目录。如果没有指定,则默认使用当前目录来生成 spec 文件,参数为spec文件路径。
-p DIR,--path=DIR设置 Python 导入模块的路径(和设置 PYTHONPATH 环境变量的作用相似)。也可使用路径分隔符(Windows 使用分号,Linux 使用冒号)来分隔多个路径,无参数。
-n NAME,--name=NAME指定项目(产生的 spec)名字。如果省略该选项,那么第一个脚本的主文件名将作为 spec 的名字

在表中列出的只是 PyInstaller 模块所支持的常用选项,如果需要了解 PyInstaller 选项的详细信息,则可通过 pyinstaller -h 来查看。

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/Cpp五条/article/detail/567722
推荐阅读
相关标签
  

闽ICP备14008679号