Changeset 78
- Timestamp:
- Thu Sep 15 15:02:52 2005
- Files:
-
- trunk/doc/source/Tutorial.rst (modified) (diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
trunk/doc/source/Tutorial.rst
r75 r78 145 145 For simple projects, the generated spec file will probably be sufficient. For 146 146 more complex projects, it should be regarded as a template. The spec file is 147 actually Python code, and modifying it should be ease. See Spec Filesfor147 actually Python code, and modifying it should be ease. See `Spec Files`_ for 147 147 details. 148 148 … … 159 159 160 160 161 A buildprojectsubdirectory will be created in the specfile's directory. This161 A ``buildproject`` subdirectory will be created in the specfile's directory. This 161 161 is a private workspace so that ``Build.py`` can act like a makefile. Any named 162 162 targets will appear in the specfile's directory. For ``--onedir`` 163 configurations, that include distproject, which is the directory you're163 configurations, it will create also ``distproject``, which is the directory you're 163 163 interested in. For a ``--onefile``, the executable will be in the specfile's 164 164 directory. … … 200 200 COM server. In the driver script, set ``debug=1`` in the registration line. 201 201 202 Warnings: the inprocess COM server support will not work when the client202 **Warnings**: the inprocess COM server support will not work when the client 202 202 process already has Python loaded. It would be rather tricky to 203 203 non-obtrusively hook into an already running Python, but the show-stopper is … … 229 229 230 230 The ``Py_OptimizeFlag`` will be set if you use a ``('O','','OPTION')`` in one of 231 the TOCsbuilding the ``EXE``::231 the ``TOCs`` building the ``EXE``:: 231 231 232 232 exe = EXE(pyz, … … 235 235 ... 236 236 237 See `Spec Files` for details. 237 See `Spec Files`_ for details. 237 237 238 238 |GOBACK| … … 309 309 310 310 While we are not a security expert, we believe the scheme is good enough for 311 most of the users. Now, take notice that if the executable does a setuid root, 311 most of the users. 312 313 **Notes for \*nix users**: Take notice that if the executable does a setuid root, 312 314 a determined hacker could possibly (given enough tries) introduce a malicious 313 315 lookalike of one of the shared libraries during the hole between when the … … 340 342 :: 341 343 342 python ArchiveViewer.py archivefile344 python ArchiveViewer.py <archivefile> 342 344 343 345 … … 365 367 366 368 369 bindepend 370 --------- 371 372 :: 373 374 python bindepend.py <executable_or_dynamic_library> 375 376 bindepend will analyze the executable you pass to it, and write to stdout all 377 its binary dependencies. This is handy to find out which DLLs are required by 378 an executable or another DLL. This module is used by |PyInstaller| itself to 379 follow the chain of dependencies of binary extensions and make sure that all 380 of them get included in the final package. 381 382 367 383 GrabVersion (Windows) 368 384 --------------------- … … 370 386 :: 371 387 372 python GrabVersion.py executable_with_version_resource388 python GrabVersion.py <executable_with_version_resource> 372 388 373 389
