Hartmut says,
Regarding your major problem described in your OP I can not help, as
I'm not using Windows -- and I know why ;-)
OK, So, is there anybody here who can help me with the way winmanifest
is used during the build. What I'm trying to do at this point is to
specify a version of 9.0.30729.1 to be used to get the msvc*.dll files,
and I can't find the right place to make that happen. I'm guessing that
it takes the version from the Python executable (the version it's
"insisting" on is 9.0.21022.8).
Alterternatively:
As I said in the OP, I've specified exactly where it's supposed to get
the msvc*.dll files for in by adding to a.binaries in the EXE
parameters. However, the files that are picked up in the executable are
from the 9.0.21011.8 sxs folder. I'm guessing that those are added
first to the archive, then when it processes my specification, it finds
the existing file and ignores the specification. (Or possibly the other
way around: it gets the files from the paths I specify, then overwrites
them later.)
Basically, I need more insight into how PyI handles this area. Any help
appreciated,
--
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.
