GNOME Bugzilla – Bug 570818
better error message for not-found types (and other errors)
Last modified: 2018-02-08 11:47:36 UTC
We really need an at least slightly better developer experience than: ** WARNING **: Can't resolve type 'KeySym' for field Meta.KeyBinding.keysym Aborting I think for each symbol in the C AST we parse, we should keep track of file+line+column if we're not already. Then for each ast.py object, keep track of its source(s) in the C AST. Finally when we hit an error like this not found type (which should btw actually be caught in g-ir-scanner, not g-ir-compiler), we can output e.g.: warning: foo.c:42: Unknown C symbol KeySym Possibly add hyperlinks to live.gnome.org wiki for each error.
*** Bug 572139 has been marked as a duplicate of this bug. ***
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/11.