As I've mentioned before, I'm using the MERGE capability to create a set
of 18 executables, using a single .spec script. This is working well in
terms of what it does, but less so in terms of the time it takes to
build. Also again, I'm using a clone of the fix-merg-case branch of git.
In particular, I've tried doing two successive builds with no changes to
any of my files, and gotten the same log output. PyI doesn't seem to
"notice" work that it's done previously.
Below is a sample of the analysis log output for one of the executables
(they all follow the same pattern). I've changed the log FORMAT to
prefix the milliseconds since the start of the build to each line (using
'%(relativeCreated)d').
Analyzing app Administration {This came from my .spec file}
101845 WARNING: Ignoring obsolete auto-added script
C:\Dwig\Falcon\Tools\Python\PyInstaller-git\support\_mountzlib.py
101845 WARNING: Ignoring obsolete auto-added script
C:\Dwig\Falcon\Tools\Python\PyInstaller-git\support\useUnicode.py
101845 INFO: checking Analysis
101939 INFO: building because out01-Analysis.toc is bad
101939 INFO: running Analysis out01-Analysis.toc
101970 INFO: Analyzing
C:\Dwig\Falcon\Tools\Python\PyInstaller-git\support\_pyi_bootstrap.py
102407 INFO: Analyzing Administration\Administration.pyw
110017 WARNING: library python%s%s required via ctypes not found
120453 WARNING: pythoncom is changing it's name to pythoncom25
120703 WARNING: pywintypes is changing it's name to pywintypes25
122407 INFO: Hidden import 'encodings' has been found otherwise
141564 INFO: Adding Microsoft.Windows.Common-Controls to dependent
assemblies of final executable
241159 INFO: c:\Dwig\Falcon\Development\Desktop
Python\build\pyi.win32\FalconApps\out01-Analysis.toc no change!
Some comments and questions:
* A few of these operations take most of the time, especially:
o "Analyzing Administration\Administration.pyw" (~8 seconds),
o "WARNING: library python%s%s required via ctypes not found"
(over 10 seconds),
o "INFO: Hidden import 'encodings' has been found otherwise" (~19
seconds), and
o "Adding Microsoft.Windows.Common-Controls..." (~99 seconds)
o (These times are typical of other
* The 4th and last lines seem to say that out01-Analysis.toc has been
found to be bad, but it doesn't get changed. (And it was found bad
in the next run.)
* Could Microsoft.Windows.Common-Controls be processed once, and
remembered for future use?
* The whole analysis step took about 38 minutes.
Here's a similar sample from the "build" section:
Building app Administration ...
2330434 INFO: checking PYZ
2330559 INFO: checking PKG
2330637 INFO: building because c:\Dwig\Falcon\Development\Desktop
Python\build\pyi.win32\FalconApps\FalconApps.exe.manifest changed
2330637 INFO: building PKG out26-PKG.pkg
2331450 INFO: checking EXE
2331465 INFO: Removing file c:\Dwig\Falcon\Development\Desktop
Python\Administration\Administration.exe
2331496 INFO: rebuilding out25-EXE.toc because Administration.exe missing
2331496 INFO: building EXE from out25-EXE.toc
2331871 INFO: Appending archive to EXE
c:\Dwig\Falcon\Development\Desktop
Python\Administration\Administration.exe
Collecting files for app Administration ...
2332434 INFO: checking COLLECT
2332481 INFO: building out27-COLLECT.toc because
c:\Dwig\Falcon\Development\Desktop
Python\Programs\Administration\Administration.exe is missing
2332481 INFO: building COLLECT out27-COLLECT.toc
Less than 2 seconds. After analysis, the rest of the run took about 2
minutes.
I'm willing to do some playing with my working copy of PyI if it will help.
Thanks,
--
Don Dwiggins
Advanced Publishing Technology
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
