https://bugs.winehq.org/show_bug.cgi?id=55636
Bug ID: 55636 Summary: cannot get rid of prefix status messages Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: xantares09@hotmail.com Distribution: ---
I would like to be able to get rid of the 2 messages on creation of prefixes, but even with WINEDEBUG=-all they never go away, as seen below:
$ echo "int main() {return 0;}" > main.c $ i686-w64-mingw32-gcc main.c $ rm -rf ~/.wine $ WINEDEBUG=-all wine a.exe wine: created the configuration directory '/home/devel/.wine' wine: configuration in L"/home/devel/.wine" has been updated.
I see from the code that they end up in wine_dbg_printf which is always printed
wouldnt it make sense for these to be part of one of the debug class/channel so that it could be filtered by WINEDEBUG ?
https://bugs.winehq.org/show_bug.cgi?id=55636
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source CC| |austinenglish@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=55636
--- Comment #1 from xantares xantares09@hotmail.com --- the idea is that wine can be used for configure checks which use the stdout to get results so I want to avoid these unwanted messages mixed with configure results
https://bugs.winehq.org/show_bug.cgi?id=55636
--- Comment #2 from xantares xantares09@hotmail.com --- I guess would like to filter all wine output completely
https://bugs.winehq.org/show_bug.cgi?id=55636
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Use two steps instead of one:
# Create/update the wineprefix, discarding any output. $ wineboot -u >/dev/null 2>&1 # Run your program. $ WINEDEBUG=-all wine a.exe
Remember that before calling wine like this, configure should check first the availability of wine and the ability to create a wineprefix.
If your configure is intended for public release, you should use a temporary wineprefix for those checks. I don't think users will like their ~/.wine directory being mangled by your configure script.
# Create an unique directory in the current directory and set it as WINEPREFIX. $ export WINEPREFIX=$(mktemp -d -t './XXXXXX.wine') # Populate the new wineprefix with default wine stuff. $ wineboot -u >/dev/null 2>&1 # Run your program. $ WINEDEBUG=-all wine a.exe # Cleanup. $ rm -rf $WINEPREFIX
Regards.
https://bugs.winehq.org/show_bug.cgi?id=55636
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Ken Sharp imwellcushtymelike@gmail.com --- Not a bug.
https://bugs.winehq.org/show_bug.cgi?id=55636
--- Comment #5 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=55636
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Austin English austinenglish@gmail.com --- Actually closing.