On 04/11/14 12:13, Michael Sverdlik wrote:
Thanks Steve,
I've checked it and indeed this works. I'm not sure I'll solve my
problem this way (other devs won't be thrilled about it), but good to
know.
The other "hack" or "work around" that I have used on occasion is to
have a variation of the __import__ class that, when run from source,
i.e. not Frozen, produces a file that "just" imports the relevant
modules and twist the exe builders tail into also building this, for
shared libraries this will ensure that all the libraries that I need are
included in the share, then don't ship the "dummy" executable, or of
course have it simply display a message. One sneaky is to have a dummy
program that is generated and has as it's main method a display package
information function.
That way the other developers don't need to know about the manual task
of adding if False statements and my build process can run a command to
(re-)generate the dummy file.
Gadget/Steve
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyinstaller.
For more options, visit https://groups.google.com/d/optout.
