On 9/10/13 1:01 AM, Martin Zibricky wrote:
My guess is that you just passed your old .spec file directly to
pyinstaller. But there are some changes in the .spec format and the
development version just fails with your old .spec file. --
Well, I did get a failure at first, and as I said, had to replace
BUILDPATH by WORKPATH -- after that, the build ran successfully, in that
it produced all the usual stuff in the build and dist folders, and the
executable worked fine on the build machine. Are there other changes in
the .spec format that I should know about? If so, are they described
somewhere?
That said, the issue I want to call attention to is my need to address
the SxS problem. At this point, I think my best shot is to be able to
pull all the VC-related DLLs into the executable (built as a one-file)
during the build. This way, I'm guessing, I won't run into the startup
issues on machines that don't happen to have the "right" version. If
I'm right, I need to know how to make that happen.
If I'm wrong about this, I'd like some guidance on what to try next.
I'm willing to dig into the PyI code to find out what's happening, and
make needed changes to get the right results, but I'll need some
pointers to where to look.
Thanks,
--
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.
