portable completely statically linked
Issue #715
new
It used to be that there was a version which was statically linked, or at least I think there was. The upside to that one was that it was easy to drop it into system32 and have crunch available from run on windows. I don't really want to clutter system32 with all the various dlls which speedcrunch depends on.
The run command looks for executables in all the directories listed in the PATH environment variable. Instead of dropping anything into
system32
you should add the speedcrunch install directory to the PATH.Really, copying anything into
system32
that doesn't belong there is a terrible idea. Especially a binary that saves its user data (history, variables, ...) there is an absolute no go.Still, I agree that there are a number of reasons for having a statically built portable version. I vaguely remember this discussion, and IIRC, we decided against it as building static apps with Qt on Windows is not the most straightforward thing to do.