Not I, but why do you want it? The 2.3.3.1 binaries are now the same as
FINAL=1 except __WXDEBUG__ is defined so you get runtime diagnostics.
The binaries have max optimizations turned on, memory tracking turned
off, etc.
Well, one of the reasons I want FINAL=1 is because I don't like the
default popup handling of those errors, so I'm glad to hear about the
Python exceptions version.
But, the main reason I want it is because of distribution size. I've
tried to compile them myself now, and I've successfully compiled
wxmsw233.dll, which is over 800k smaller than wxmsw233h.dll.
But I had problems after that, as some part of the setup.py installation
process seems to still be looking for wxmsw233h.lib instead of
wxmsw233.lib, and the process fails.
Not I, but why do you want it? The 2.3.3.1 binaries are now the same as
FINAL=1 except __WXDEBUG__ is defined so you get runtime diagnostics.
The binaries have max optimizations turned on, memory tracking turned
off, etc.
Well, one of the reasons I want FINAL=1 is because I don't like the
default popup handling of those errors, so I'm glad to hear about the
Python exceptions version.
But, the main reason I want it is because of distribution size. I've
tried to compile them myself now, and I've successfully compiled
wxmsw233.dll, which is over 800k smaller than wxmsw233h.dll.
But I had problems after that, as some part of the setup.py installation
process seems to still be looking for wxmsw233h.lib instead of
wxmsw233.lib, and the process fails.
Try putting FINAL=1 on the setup.py command-line.
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!