If debug use flag is NOT set, wine will emerge with no debug or trace support for applications. That is, the command: WINEDEBUG=blah wine myapp.exe will produce no output. It took me awhile to figure out that wine was looking for the debug use flag. However, this use of debug is different than compiling something with debug symbols (i.e. -g). I'd like to suggest that you add some output during the emerge that explains what is being compiled and why. Something like: if !use debug einfo "Wine is being compiled without support for debug or trace." einfo "The WINEDEBUG environment variable and all its commands will" einfo "be ignored." echo einfo "To enable debugging support, please enable the debug flag for wine." einfo "add app-emulation/wine debug" einfo "to the package.use file if you would like full debug support." fi Or, you could make this a negative option -- meaning that wine will compile normally WITH debug support, and the above message could be reversed so the user can turn it off. One could argue that it's more proper to have the complete wine support turned on by default. That is the default wine behavior. JM2C.
Yeah, the Wine devs got more than a little pissed off when they found out Gentoo has this disabled by default as apparently it should be enabled by default, not V-V.
that URL pretty much will solve this issue -- forcing wine to report an error if WINEDEBUG is used without support. However, from the emerge POV, I still suggest having a message show that debug support (default support, btw) has been disabled. Also, I still strongly support the idea that this support be ENABLED by default. JM2C
I just spent an hour trying to figure out why my wine wouldn't spit out debugging info. This is super annoying--please fix! <kyle@pbx.org>
nothing left to do as upstream has resolved this
