Giovanni Bajo wrote: > OTOH, what you really want is to share as much as possible between your > executables. I'm going to add support for this quite soon (probably > within November, since it's a customer request): the idea is that a > single .pkg file will be built, containing all the dyanamic libraries > and Python modules required for all the binaries. Then, you would simply > get lightweight executables with only the boot scripts inside.
I'm looking forward to this; I've got a set of related utilities that I've built as single-file executables, mostly out of laziness. I'd really like to redo this as you describe. Question: would this require a particular directory structure, or would there be a configurable way to tell an executable where to look for its library? (Actually, going a bit further, it'd be even nicer to have multiple libraries, so. e.g., a subset of the executables that share modules and binaries could reference the subset's library and the full set's library, maybe via a kind of path mechanism. No hurry for this from me, though; just fantasizing.) -- 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 -~----------~----~----~----~------~----~------~--~---
