64bit version of putty t017 doesn't work #89
Comments
This flag shouldn't really be necessary; it appears to just be an assert that your exception code is sane. We're not actually using any languages that have exceptions, and hopefully any Windows code that wants to use exceptions within us is safe. Maybe it's worth turning this on for x32 runs of mkfiles, just to check?
|
I didn't do a p0.63-t017 release with x64 mainly because the build was broken for me too, and I couldn't be bothered to look at it. It turns out that I added some extra flags to the makefile generation in 6ae4ae8 which actually didn't work; no idea why I hadn't noticed until now. I've rolled these back (3d9df00) and now the application builds and starts perfectly fine for me. To be clear, I'm using the What build method are you using? I'm guessing this is missing that or other important defines. I can't really help unless I can try and diagnose it for myself, or you provide a lot more information about what's gone wrong with the manifesting after the defines have been set. |
|
I am using visual studio 2012, I also tried vs2010 with the same result,. I will try to diagnose it further |
|
Same problem here |
I compiled t017 from source and while the 32bit version works ok, the 64bit version fails to run with
0xc000007b: the application was unable to start correctlyerror.I tracked this problem and it seems, that the compiler is embedding 32bit manifest (
putty.mft) even into the 64bit build.Looks like that during the parsing of
putty.rcthe_WIN64constant is not defined. After editing the rc file that it will use 64bit manifest every time, the 64bit version runs without problems (of course, then the 32bit version doesn't work). I have no idea what is causing this problem, because it didn't work even after I defined_WIN64manually in linker settingsThe text was updated successfully, but these errors were encountered: