Hi,
the #39 patch resolves assembly dependencies under Windows, ie. users do
not have to install the MSVCRT90 runtimes (the error "accessing the C
runtime incorrectly" occurs if those are not resolved), --onefile or
--onedir doesn't matter. It probably doesn't help with the egg problem.
You need pywin32 for the patch to do it's magic.
One known issue with the patch is with Matplotlib (which is solvable
though without hacking into pyinstaller code, it just means 'true'
onefile deploys are not possible when using Matplotlib because the
MSVCRT90 runtimes will need to be installed even when using the patch),
otherwise it seems to work fine.
If you continue having issues even after applying the patch to the
latest pyinstaller trunk, it'd probably be best to go back to Python 2.5
if you can.
Regards,
Florian Höch
Am 26.02.2010 07:04, schrieb Raoul Snyman:
Hi,
I'm using PyInstaller from SVN and Python 2.6 on Windows (XP and 7),
and it's working well. However, I'm using --onedir, rather than --
onefile (I have plugins written in Python that I need to load). I am
getting one or two problems though, and I looked at both the tickets
mentioned in other threads (#38 and #39), and they only seem to deal
with the --onefile.
One of the biggest problems is that even though I can see the chardet
egg in my output directory, one of my plugins doesn't seem to be able
to load it (I get the "no module named chardet" error). I also noticed
that if I build it on Windows 7, Vista and XP can't run it. I haven't
tried it on XP -> Vista/7 yet though.
Lastly, it pops up an error message when my application starts up that
I'm accessing the C runtime incorrectly. I click OK, and my
application runs fine, but obviously I would rather I didn't have this
problem.
Does anyone have any suggestions for me? Should I rather go back to
Python 2.5?
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
