Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-04-20 15:32:45 +03:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

update docs (nw)

Browse Source
This commit is contained in:
Vas Crabb 2019-01-28 03:59:45 +11:00
parent 2f199abe23
commit 995ba92e83
2 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/source/commandline/commandline-all.rst
View File

@ -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**).

4
docs/source/initialsetup/compilingmame.rst
View File

@ -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.