From: Werner F. B. <wer...@fr...> - 2010-02-12 11:50:43
|
Hi, On 12/02/2010 11:57, le dahut wrote: ... > > Werner, this was *very* helpful ! > > It works fine now. > > I also tried Dependency Walker and I didn't understand how to interpret > it, so thank you very much for your clarification. I still have a hard time with it too. > > After some tests, I see that my test app works with only : > * mfc90.dll > * Microsoft.VC90.MFC.manifest > Other mfc*.dll and msv*.dll are not necessary. > > Can I conclude that I don't need to redistribute them or can the > application fail to run on other machines ? At particular python calls ? The import test is definitely not enough, it might be that some functions will need other things. So, you will need to check your full application at least once on a machine which never saw Python or other tools you are using, i.e. only has the py2exe'd version installed. > > > Maybe this could be documented somewhere on http://www.py2exe.org/ ? It is a wiki, so everyone can document things, maybe you could create a new page below this: http://www.py2exe.org/index.cgi/WorkingWithVariousPackagesAndModules with a heading of win32ui. I don't use win32ui myself, so I don't think that I know enough about it to write up something. All my stuff is done using wxPython and I documented my findings for this on the deploy pages on the wxPython wiki. > > > > I've subsidiary question : in setup.py, why do you define a "Target" > class ? Why don't you use dict() ? > Like : > GUI2Exe_Target_1con = dict( > script = "test_win32ui.py", > icon_resources = icon_resources, > ..., > ) > To generate my initial version of a setup.py I use the gui2exe tool (http://code.google.com/p/gui2exe/), that is generating most of the code you see, only additions I made by had is the stuff for the dll's and I adjust some of the include/exclude stuff based on my needs. Werner |