Public bug reported:
The packaging guidelines for libgtk say to avoid using "--enable-
debug=no" when packaging stable releases of GTK+. [1]
The "--enable-debug=no" option can cause subtle errors and should be
avoided. "--disable-debug" is another alias for this configuration
option.
More info a
Thanks for the response. The problem is that with libgtk, "--enable-
debug=no" alters the logic within the library, and actually allows
undefined behavior, by disabling code assertions and cast checks.
This makes it easy for library and application developers to make
mistakes leading to "undefined
I am not sure if this answer will satisfy you, but the Rust bindings to
libgtk, in the Gtk-rs library, are unusable on Ubuntu currently since it
requires a libgtk compiled with safety on. I am trying to write a
Nautilus (aka Files on Ubuntu) extension which crashes when using Gtk-
rs.
It is not a
I'm sorry for wasting your time. The problem does not appear to be a
misconfigured libgtk. From your links, it looks like it is already using
a configuration equivalent to --enable-debug=minimum.
Thank you for linking the build configurations, I would never have been
able to find those. Launchpad
4 matches
Mail list logo