abort if WINEDEBUG requests functionality that was disabled at configure time

Tomas Carnecky tom at dbservice.com
Sun Apr 16 14:19:42 CDT 2006

Segin wrote:
> Mike Hearn wrote:
>> On Sat, 15 Apr 2006 23:37:17 -0400, Mike Frysinger wrote:
>>> if wine is built with --disable-trace or --disable-debug, then using WINEDEBUG 
>>> will accept the respective options without complaining and without actually 
>>> showing any useful information
>> Why would anybody build without tracing anyway? I would be *very*
>> surprised if it led to any noticable/real world performance improvement.
>> Rather than do this why not just restore your packages configure switches
>> to the upstream defaults?
> It's because some people are Gentoo zealots whose CFLAGS are "-O9
> --omfg-optimize -march=8088"

If we can, why not?

If there is the option to disable the trace it's gotta be there for a
reason, why would it be there else, for fun?

Nobody ever told me that disabling the trace will improve performance
but I assumed it, less code means faster code (generally speaking).

But it doesn't improve performance, tested it with WoW, at least nothing
noticeable. So I'm all for removing this configure option.


More information about the wine-devel mailing list