> Hartmut Goebel píše v Út 17. 05. 2011 v 12:48 +0200: >> If we are going to run configure every time, there is no need for the >> config.dat at all. So in this case we should get rid of it. > > we still need it because we still have script ./utils/Configure.py > unless we would eliminate ./utils/Configure.py and the configuration > step would be put to ./utils/Build.py and ./utils/Makespec.py >
> That would be my preference. The less files, the less steps the better. I have noticed that all the package tools (e.g. pyinstaller, Py2Exe, Py2App, cxfreeze) approach the problem the same way, with spec files, paths, etc., running multiple commands. But, in the end, I think a simple and intuitive setup is always better. Nobody would care about waiting 10-15 more seconds for the build to finish. (It's not exactly like we're building the distribution multiple times in a short time span. What attracted me to pyinstaller was the philosophy of everything working out of the box. (It's also the *only* tool that can produce a single standalone exe, which is very nice). Making the run procedure always a single step would build on that philosophy. Have you seen the PerlApp tool? In my view, something equivalent to that would be fantastic. -- 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.
