After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790761 - Define G_ENABLE_DIAGNOSTIC=1 when building
Define G_ENABLE_DIAGNOSTIC=1 when building
Status: RESOLVED FIXED
Product: gnome-builder
Classification: Other
Component: general
3.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-23 16:22 UTC by Philip Withnall
Modified: 2017-11-23 19:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
pipeline: use G_ENABLE_DIAGNOSTIC by default (1.16 KB, patch)
2017-11-23 19:03 UTC, Christian Hergert 		committed Details | Review

Description Philip Withnall 2017-11-23 16:22:20 UTC 
As per https://bugzilla.gnome.org/show_bug.cgi?id=732184#c29, Builder should define G_ENABLE_DIAGNOSTIC=1 in the environment when building anything which has GLib as a transitive dependency.

It enables deprecation warnings for GObject properties and signals.
Comment 1 Christian Hergert 2017-11-23 19:03:49 UTC 
Created attachment 364285 [details] [review]
pipeline: use G_ENABLE_DIAGNOSTIC by default

This enables various deprecation warnings so that developers catch them
when writing applications instead of at runtime.
Comment 2 Christian Hergert 2017-11-23 19:04:21 UTC 
No problem, thanks!

Attachment 364285 [details] pushed as 3fe6c94 - pipeline: use G_ENABLE_DIAGNOSTIC by default