Don Dwiggins píše v St 04. 05. 2011 v 12:14 -0700: > I have a distribution that includes several .exes. Currently, > they're > built as onefiles (with separate .spec files), and live in a common > subfolder of the deployed distro.
> What I'd like to do, to reduce the > amount of extra space and the startup time, is to have the subfolder > contain the exes, minus the dependencies, plus a single copy of each > of > the dependencies, so each exe can find what it needs on startup. multipackage can't do this exactly as you described. with multipackage you can do following: - several .exes in onedir with a single copy of all dependencies of those .exes in the same dir (test1_multipackage.spec example) - onefile bigger .exe and other onefile .exes which depend on the bigger one. (test4_multipackage.spec example) - 2 other modes mixing the previous two modes > > It looks to me like the multipackage function could help here, but I > found the description in the doc and the examples in the buildtests > insufficient to figure out how to do what I want. In particular, will > I > need to go to a common .spec file for all exes, or one .spec for each? one .spec for all exes > I think I could get started if someone could come up with a simple > example of, say, two exes (each built from one .py) that would live in > a > common directory, with the "union" of the files that normally go in a > onedir build in the same directory. (Note: there's no dependencies > between the two.) -- 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.
