Open GoogleCodeExporter opened 9 years ago
It appears that wx-config disregards the "--debug" argument and prefers to use
DEBUG_FLAG which is present in the build.cfg generated by wxWidgets' gcc
makefile.
The DEBUG_FLAG is erroneously set to 1 even when a release build is performed,
this has been reported upstream here:
http://forums.wxwidgets.org/viewtopic.php?f=19&t=31435
I'm going to chase that down and establish is it is known to the wxWidgets
devs, and whether we can expect a fix.
With regards to the "--debug" argument:
It is parsed by checkAdditionalFlags:
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#230
8
But after this has been called:
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#259
8
Then we call detectCompiler:
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#260
3
This will detect the compiler as GCC:
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#236
3
And the parse DEBUG_FLAG from the GCC build.cfg:
http://code.google.com/p/wx-config-win/source/browse/trunk/wx-config-win.cpp#951
If this is correct (if someone could check), then I propose that either:
1. wx-config-win should emit an error when --debug is specified inconstantly;
or,
2. The --debug argument shouldn't exist at all.
Original comment by duked...@gmail.com
on 30 Dec 2011 at 8:06
This appears to be a problem with wx-config-win, as identified on the wxWidgets
mailing list:
https://groups.google.com/d/msg/wx-dev/4PuKS-xQX3k/8-rOzSExpLwJ
Original comment by duked...@gmail.com
on 4 Jan 2012 at 4:23
Original issue reported on code.google.com by
MRKing2...@gmail.com
on 28 Feb 2011 at 11:52