Hi, although I'm balking at having to do this for every Windows setup, and regarding a recent bug, I was thinking about providing a "log" build of Wormux (configure --enable-logging), which would then allow better tracing problems.
Drawbacks: - The log build is much slower so to be used only when everything else fails (the slowness may hide bugs) - I'd have to build twice wormux, breaking any automatism I had previously (ie much more work for the Windows packager aka me) - We'd still have to get the user into: . going to the command line . entering the proper folder . typing the appropriate flag . returning the (big) log files Best regards, Kurosu _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
