On 12.06.2014 13:43, Olly Betts wrote: [...] > FWIW, most of the "assertion failed" messages are things which are just > as much of an issue (or not) in wx2.8. The difference is that wx3.0 > defaults to enabling "WXDEBUG" checks for incorrect API usage. In wx2.8 > you had to rebuild wx with non-default options (or in Debian, install > the libwxgtk2.8-dbg package) and then rebuild your app. Without the > assertions on, wx quietly tries to handle such cases (typically by just > returning from the method in question). > > These assertions can be disabled by defined NDEBUG when building the > application - e.g. by adding -DNDEBUG to CPPFLAGS - which means such > assertions will be handled as they would have been by a default build of > 2.8. > > So it's generally good to try to fix them, but if the app worked OK > with wx2.8, just disabling them isn't an unreasonable solution.
Thanks for your explanations. I think this kind of solution is O.K. with me as long as the application still works as intended. I have added -DNDEBUG to CPPFLAGS now, seems like this is going to work. [...] >> I am not sure if we can do a better job than upstream here but I am open >> for any suggestions. > > I suspect they have less experience with migrating things to wxwidgets3.0 > than I have now amassed. I'm certainly OK with trying to help where I > can. I will do some testing tomorrow and try to figure out whether there is still a real issue even after DEBUG has been disabled. If I can't find anything else, I will upload a new revision which build-depends on wx3.0 again. Regards, Markus
signature.asc
Description: OpenPGP digital signature
