On 10/2/13 1:07 AM, Martin Zibricky wrote:
On Monday 30 of September 2013 13:55:18 Don Dwiggins wrote:
* On some machines that I install the executable+manifest on,
there's no SxS folder for Microsoft.VC90.MFC. Thus, on those
machines, you get an error dialog when trying to execute; this is
due to the MFC dependency in the manifest. (I found that out by
experimentation; on such a machine, I edited out this dependency,
and the program ran with no problem.)
What pyinstaller version do you use? 2.1?
I started out on the development version, and installed 2.1 when it came
out. Just about everything I've said relates to that.
Could you please be more specific what machines (Windows version) were
missing Microsoft.VC90.MFC?
Recently, I've been working exclusively with 64-bit Windows 7 (or Server
2008) machines. One had the MFC assembly, the other didn't. I think the
salient difference is whether a development environment has been set up
on the machine (e.g., Python).
Are the Microsoft.VC90.MFC dlls bundled with your app?
I tried explicitly including them, with no succcess (I might have done
it wrong).
Microsoft.VC90.MFC is probably something that should be picked up and
not depending on having it in SxS.
I'm not sure about that. As I've said, my executable (a wxPython app)
works without it, as long as I get rid of the dependency in the manifest.
I would expect pyinstaller to bundle Microsoft.VC90.MFC dlls. If these
dlls are not bundled then there is probably a bug in pyinstaller.
See above. My guess is that they shouldn't be included unless they show
up via the dependency analysis.
We should find out what files cause pyinstaller to add
Microsoft.VC90.MFC to manifest and then decide if we really need that
or not.
Probably a good idea. Offhand, I don't think any Python libraries
depend on the MFC, but don't take my word for it.
Could you describe your ideas for making the manifest more configurable?
Well, if MFC isn't automatically added as a dependency, that will
mitigate, and maybe eliminate the need for a configuration capability.
At this point, I don't have any definite ideas beyond that.
If I get a chance, I might dig into the PyI code to see if I can make
the code avoid adding the MFC dependency unless it's "known" to be
needed. For now, my post-build surgery does the trick for me.
The issue with manifest files is that there is not a lot of people
understanding this stuff (including me).
Up until recently, that included me as well. I now know considerably
more than I wanted to know about manifest files. 8^) I'll repeat my
suggestion to ask Mark Hammond; he's about the most knowledgeable person
I know about Python and Windows. (He's worked with py2exe a lot, but he
might be willing to assist the competition. 8^)
--
Don Dwiggins
Advanced Publishing Technology
--
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/groups/opt_out.
