Re: winemenubuilder: disable debug output for .desktop files
On Fri, Apr 3, 2009 at 4:05 PM, Vincent Povirk <madewokherd+8cd9(a)gmail.com> wrote:
I'll work on a patch for the FIXME thing.
Turns out this is not "fairly easy" but actually "incredibly difficult". We have a fallback case at http://source.winehq.org/source/include/wine/debug.h#L133 with a macro that returns a statement that ends in a function call, omitting the arguments and semicolon. This allows us to do FIXME_(channel)("message\n");. I can handle this in the other cases (where the macro result ends in a macro that takes arguments), but I can't see a way to create a static variable in a statement that ends in a function call that we only execute sometimes. Vincent Povirk
I just responded to my previous mail, nice to see you care about that issue! I just want to say that nobody uses the desktop file to launch a program to debug, i think, in response to previous messages. That would be very nice. Is it difficult to implement? Why not simply add WINEDEBUG-all to generated desktop files? Maybe i didn't understand the discussion... 2009/4/4 Vincent Povirk <madewokherd+8cd9(a)gmail.com<madewokherd%2B8cd9(a)gmail.com>
On Fri, Apr 3, 2009 at 4:05 PM, Vincent Povirk <madewokherd+8cd9(a)gmail.com <madewokherd%2B8cd9(a)gmail.com>> wrote:
I'll work on a patch for the FIXME thing.
Turns out this is not "fairly easy" but actually "incredibly difficult". We have a fallback case at http://source.winehq.org/source/include/wine/debug.h#L133 with a macro that returns a statement that ends in a function call, omitting the arguments and semicolon. This allows us to do FIXME_(channel)("message\n");. I can handle this in the other cases (where the macro result ends in a macro that takes arguments), but I can't see a way to create a static variable in a statement that ends in a function call that we only execute sometimes.
Vincent Povirk
On Sat, Apr 4, 2009 at 1:37 PM, Warren Dumortier <nwarrenfl(a)gmail.com> wrote:
I just responded to my previous mail, nice to see you care about that issue!
I just want to say that nobody uses the desktop file to launch a program to debug, i think, in response to previous messages. That would be very nice.
Is it difficult to implement? Why not simply add WINEDEBUG-all to generated desktop files? Maybe i didn't understand the discussion...
This would add WINEDEBUG="-all" to all .desktop files. Vincent is saying that stderr may not be lost when someone runs from a .desktop file, e.g., that information may be captured/redirected somewhere. -- -Austin
participants (3)
-
Austin English -
Vincent Povirk -
Warren Dumortier