GNOME Bugzilla – Bug 557070
Add a macro to check for single header includes
Last modified: 2009-08-08 16:05:48 UTC
Currently we have GNOME_MAINTAINER_MODE_DEFINES which takes care of enabling all the CFLAGS for deprecated functions for the libraries the stack. Why not add a similar macro that enables -DG_DISABLE_SINGLE_INCLUDES and friends? (or even add that to GNOME_MAINTAINER_MODE_DEFINES)
I wanted to file the very same bug :) I think just adding them to the defines in GNOME_MAINTAINER_MODE_DEFINES should be ok. I think we should get the opinion of d-d-l first, though.
I just sent a mail to d-d-l to gather feedback.
Created attachment 121378 [details] [review] patch No protests on ddl, I guess we can go ahead with this :)
I guess we should make sure the gnome-suites-2.26 modules build with this, and file patches where they don't?
Yes, I think this is a good plan. I will try to build all the modules tonight or tomorrow, as now I'm on battery ;) If you want to beat me at it, feel free, but anyway let's try to keep here a list of modules/bugs affected by this so that we don't duplicate the work.
Cosimo: any news? :-)
Sorry for the delay. I am currently building all the modules, will post the results as soon as my slow PC finishes.
So, I managed to build the modules, except Evolution and some python modules and the only modules which were affected were - totem/totem-pl-parser - at-spi (not directly, some other program compiled with the flags was linking to it) - libepc (ditto) I committed the trivial single includes fixes to all of them, so there shouldn't be any additional breakage with this patch, which we should commit.
*** Bug 539456 has been marked as a duplicate of this bug. ***
Hey Cosimo :) Have you already committed the patch in attachment #121378 [details]? If so, could you please set the status accordingly? Also, what is still needed to close this bug? ;-) Cheers!
Pushed an updated variation of this. Closing as FIXED.
(In reply to comment #11) > Pushed an updated variation of this. > Closing as FIXED. Can you push your commit? :-)
Argh, I was thinking of another bug. Sorry :-)