From 995ba92e833e40c27760ad9a6e80d46dee48f06f Mon Sep 17 00:00:00 2001 From: Vas Crabb Date: Mon, 28 Jan 2019 03:59:45 +1100 Subject: update docs (nw) --- docs/source/commandline/commandline-all.rst | 9 +++++---- docs/source/initialsetup/compilingmame.rst | 4 ++-- 2 files changed, 7 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/source/commandline/commandline-all.rst b/docs/source/commandline/commandline-all.rst index 9ecba9e9bea..d7026de24b9 100644 --- a/docs/source/commandline/commandline-all.rst +++ b/docs/source/commandline/commandline-all.rst @@ -2159,12 +2159,13 @@ Debugging Options **-[no]oslog** - Output ``error.log`` data to the system diagnostic output, if one is + Output ``error.log`` messages to the system diagnostic output, if one is present. - On Windows, the ``error.log`` data goes nowhere if no debugger is present. - On other operating systems, the ``error.log`` data will go to standard - error output, which typically goes to the console or terminal window. + By default messages are sent to the standard error output (this is typically + displayed in the terminal or command prompt window, or saved to a system log + file). On Windows, if a debugger is attached (e.g. the Visual Studio + debugger or WinDbg), messages will be sent to the debugger instead. The default is OFF (**-nooslog**). diff --git a/docs/source/initialsetup/compilingmame.rst b/docs/source/initialsetup/compilingmame.rst index 44af60a91df..1c102f66e63 100644 --- a/docs/source/initialsetup/compilingmame.rst +++ b/docs/source/initialsetup/compilingmame.rst @@ -392,8 +392,8 @@ Issues with specific compiler versions Adding **DEPRECATED=0** to your build options works around this by disabling deprecation warnings. * MinGW GCC 7 for Windows i386 produces spurious out-of-bounds access warnings. - Adding **NOWERROR=1** to your build options works around this by disabling - deprecation warnings. + Adding **NOWERROR=1** to your build options works around this by not treating + warnings as errors. * Initial versions of GNU libstdc++ 6 have a broken ``std::unique_ptr`` implementation. If you encounter errors with ``std::unique_ptr`` you need to upgrade to a newer version of libstdc++ that fixes the issue. -- cgit v1.2.3