<div dir="ltr">Looks like G_DEBUG_HERE is only available in glib >= 2.50. Might set the bar too high. For ex. latest Mint has 2.48 and the oldest Ubuntu LTS (14.04) only has 2.40. I think the latter could be a good baseline.</div> <div class="gmail_quote"><div dir="ltr">On Tue, May 29, 2018 at 2:59 PM Bastien Nocera <<a href="mailto:hadess@hadess.net">hadess@hadess.net</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey, In the process of writing and documenting the libfprint drivers API, I realised that drivers have access to library internals for no good reason, so I split off the internal library API from the drivers API. If you have an out-of-tree driver, the easiest would be to update your fork, and see where you get errors. Accessor functions were added for fields that were already in use by existing drivers, such as: - fpi_imgdev_get_usb_dev() and fpi_dev_get_usb_dev() instead of ->udev - fpi_dev_get_user_data()/fpi_dev_set_user_data() and fpi_imgdev_get_user_data()/fpi_imgdev_set_user_data() instead of accessing ->priv directly and similar. Let me know if any accessor is missing for your drivers. Note that there's a possibility that more changes are coming, especially as I don't like the way the user_data/priv is passed around, and fp_dev and fp_img_dev types need to duplicate access to some variables. But, hopefully, by the time I'm done with the above there will be a driver writing guide. Cheers _______________________________________________ fprint mailing list <a href="mailto:fprint@lists.freedesktop.org" target="_blank">fprint@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/fprint" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/fprint</a> </blockquote></div>