Graham Cobb wrote: > On Friday 19 March 2010 14:42:05 Stefan Kost wrote: > >> I noticed that still lots of packages that use GObject are not disable >> GObject cast checks in their builds. *It is a safe thing to do*. The >> macro is doing a cast, if checking is enabled it checks and warn in the >> case of an mismatch. The check is pointless in device that is running a >> PR image as we have the (sys)logging turned off. So we can also turn off >> the checks (the checks are not preventing anything). This makes binaries >> smaller and faster. >> > > That is a good suggestion for production binaries. However, for beta > binaries > I would prefer to leave it on -- I find the console mesages very useful > during testing (and I run syslog on my development device as well). > I does not show on the console. Our glib is patched so that it goes to syslog. But anyway I am totally with you. Messages enabled for testing binaries, messages off for releases.
Stefan > >> I wonder if it would make sense to disable this globally on the package >> builder. Having the check enabled is most useful in conjunction with >> defining G_DEBUG="fatal_warnings" and checking for coredumps. >> > > No thanks, at least not without a way to override it. > > Graham > _______________________________________________ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
