I'm going to close this bug in the 2.67.5-1 upload which I'm just making to experimental. There will still be "some" projects still affected, but it's as fixed as it's going to get from glib2.0's side - we made the API break opt in for packages that have followed glib's longstanding advice and defined the MAX_ALLOWED/MIN_REQUIRED macros.
Affected projects can do either (but should do both) of these.
- Define GLIB_VERSION_MAX_ALLOWED to something below GLIB_VERISON_2_66 to opt out or _2_68 to opt in to this new typesafe behaviour.
- Not include glib's headers in an 'extern "C"' context. GLib has G_{BEGIN,END}_DECLS that might help with this.
I'm going to close this bug in the 2.67.5-1 upload which I'm just making to experimental. There will still be "some" projects still affected, but it's as fixed as it's going to get from glib2.0's side - we made the API break opt in for packages that have followed glib's longstanding advice and defined the MAX_ALLOWED/ MIN_REQUIRED macros.
Affected projects can do either (but should do both) of these.
- Define GLIB_VERSION_ MAX_ALLOWED to something below GLIB_VERISON_2_66 to opt out or _2_68 to opt in to this new typesafe behaviour.
- Not include glib's headers in an 'extern "C"' context. GLib has G_{BEGIN,END}_DECLS that might help with this.