Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document the change to unknown options handling in configure

Browse Source 
They used to be silently ignored, but are flagged as errors since
aa7e10bb09
This commit is contained in:
Vadim Zeitlin
2018-09-20 17:40:11 +02:00
parent d663cd5641
commit deb0c2566b
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/changes.txt
View File

@@ -86,6 +86,13 @@ Changes in behaviour which may result in build errors
not long. Its return value hasn't changed, however, and is still always not long. Its return value hasn't changed, however, and is still always
either true or false, so normally the existing code should continue to work. either true or false, so normally the existing code should continue to work.
- configure only accepts the options it knows about now and doesn't silently
ignore all the rest. If you get errors about unknown options, you may either
specify --disable-option-checking argument to continue accepting them (which
only ever makes sense if you pass these options to sub-configure scripts) or,
e.g. if the error is due to spelling an option name wrongly, fixing or
removing its name.
3.1.2: (released 2018-??-??) 3.1.2: (released 2018-??-??)
---------------------------- ----------------------------