> BTW: Which Windows C compiler do you use? MS Visual studio 2008 express.
It should be possible to compile bootloader with mingw but mingw bootloader is not well tested and the msvcrt library is not statically linked with the binary as it is with msvc. > > Traceback (most recent call last): > File "pyinstaller/Build.py", line 1500, in ? > main(args[0], configfilename=opts.configfile) > File "pyinstaller/Build.py", line 1478, in main > build(specfile) > File "pyinstaller/Build.py", line 1435, in build > execfile(spec) > File "test.spec", line 3, in ? > pathex=['/data2/mgd/pyinstaller-1.5']) > File "pyinstaller/Build.py", line 347, in __init__ > self.__postinit__() > File "pyinstaller/Build.py", line 298, in __postinit__ > self.assemble() > File "pyinstaller/Build.py", line 472, in assemble > self.fixMissingPythonLib(binaries) > File "pyinstaller/Build.py", line 527, in fixMissingPythonLib > if typ == 'BINARY' and name in fnm: > TypeError: 'in <string>' requires character as left operand > > Seems like this line: > > 525 for (nm, fnm, typ) in binaries: > 526 for name in names: > --> 527 if typ == 'BINARY' and name in fnm: > 528 # lib found > 529 return > > is not valid Python 2.2 code. If PyInstaller is still supposed to > support Python 2.2, maybe this should be fixed? Yes, that should be fixed for 1.5.2. -- 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.
