Am 14.09.2011 21:56, schrieb Don Dwiggins:
True, and I can see the log of its activity. However, the main
question is why the .pyc file is seen as having been changed, even
after several builds where nothing was actually changed. (I've
checked a bit further, and see that the analysis phase doesn't take
long at all when no changes are detected.)
pyinstaller does no test for changes, it simply builds.
pyinstaller is not build-optimization tool like make or scons. IMHO this
is absolutely okay, since these builds are cheap and not run that often.
So it's not worth the effort building in dependency checking.
But if you like to implement this, you are welcome :-)
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult ist Mitglied bei http://www.7-it.de
--
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.
