Your summary is correct. I don't have VS2008 Express installed locally, so I can't easily try that out at the moment. The binaries for development branch also needed me to recompile them due to the PE header stuff. On the plus side (aside from the warnings noted in my other reply) the development branch works with my recompiled bootloader .exes on Win2k for the variants that i've tried. I've tried run.exe and its debug variation. I haven't tried runw.exe and its debug variation on Win2k yet. Bill On Thursday, March 14, 2013 12:53:32 PM UTC-4, Martin Z wrote:
> Let's summarize: > - you tried bootloader from pyinstaller 2.0 on w2k > - not working - unsupported PE header number > - you think it was compiled with VS2010 > - you recompiled bootloader with VS2008 > - it still does not work on w2k for you > - pyinstaller > - bootloader for 2.0 was compiled with VS2008 Express > - I have never installed VS2010 on my system. > - the same applies for the development branch > > > Bill Tutt píše v Čt 14. 03. 2013 v 06:36 -0700: > > No, the configure phase detected the VS 2010 C compiler, but didn't > > report a path for VS 2010's linker. The actual build did occur with VS > > 2008 CL/LINK (from the Visual Studio 2008 command prompt console > > window). I verified this with passing a single -v into waf build. > > You should be able to edit the wscript file to prefer VS2008 > > over > > VS2010. > > > > Could you try the development version? > > > > I'll try the development version today and let you know. Bill > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
