Some progress!<br><br><div class="gmail_quote">On Sat, Jul 4, 2009 at 12:55 AM, Wesley W. Terpstra <span dir="ltr"><<a href="mailto:wesley@terpstra.ca">wesley@terpstra.ca</a>></span> wrote:<br>> * A self-compile of MLton trips over the use of "mlton -stop f" in mlton/Makefile<br>
<br>Still unresolved.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">* msys uses an rxvt.exe which does not work under Windows7. Using msys -norxvt fixed this. I'll either modify the msys.bat to disable rxvt.exe or find a fixed rxvt.exe.</blockquote>
<div><br>It works just fine without rxvt.exe, so I've gone ahead with that. This file was always giving us warnings anyway (it violates some windows logo requirement or another).<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Windows7 complains vehemently about installing MLton-7999.msi because it's from an "unknown publisher". I need to learn how to sign MSI files; this might require acquiring an official MLton signing certificate.</blockquote>
<div><br>A code signing certificate costs 200EUR! I think we'll just let the user click 'yes install anyway'. :P<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Windows7 appears to treat some file extensions as dangerous.</blockquote><div><br>Fixed.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* I noticed that we don't strip executables created by MLton.</blockquote><div><br>I've made the .bat file auto-strip, since that's what non-unix savy folks will be using. The shell script mlton does not strip.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">* I'm investigating including a Win64 toolchain in the MSI with a MLton cross-target. </blockquote>
<div><br>I've succeeded in including this into one package. After trimming fat, it's only 10MB bigger, so I think it makes sense to include both win32/64 in the same package.<br>
<br>The only regressions compared to mingw32 are the failing MLton.size tests. They fail because the regression script can't tell the difference between win32/64. <br><br></div></div>