I'll do this: - during install, allow to chose SSE2 or non-SSE (SSE2 by default, with some brief explanation)
- if SSE2 is selected, the .exe is executed for a check and if it fails, the pop-up tells the user to reinstall (re-run the installer) using non-SSE exes. Sounds good enough to me, I'll use for the next build. MaX. 2009/9/15 Jonathan Kinsey <[email protected]>: > I don't think that's the best approach, people in general will not know what > SSE > is and the vast majority will just be able to run the SSE version anyway. > > An installer has to be idiot-proof, I know inno-setup isn't that > customisable, > ideally just install the SSE versions if the utility passes (otherwise they > will > have to go find the non-SSE version). > > Of course another option is to re-add the fallback to non-sse code, I'm > against > this - hopefully we'll be able to try compiling the whole code with auto-SSE > optimisations soon and then (if it's faster) that version will not be able > to > fallback to non-sse. > > Jon _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
