<div dir="ltr">> From the user's perspective, users shouldn't have to build their own > system libraries. From the developers point-of-view, the rules are > actually readable, understandable, and it takes as long to build > libfprint and the docs as it did just running configure. So I'm fine > with the drawbacks :) <div> </div><div>But they actually do it sometimes :) I understand there's no going back, which is ok. Just saying that build and install docs would be a welcome addition to the docs. Willing to help with it if needed.</div></div> <div class="gmail_quote"><div dir="ltr">On Fri, May 18, 2018 at 6:51 AM 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">On Thu, 2018-05-17 at 23:40 +0300, Igor Filatov wrote: > Mine seems ok. The docs could use a short build&install guide though. > I've updated the readme in my > repo <a href="https://github.com/iafilatov/libfprint" rel="noreferrer" target="_blank">https://github.com/iafilatov/libfprint</a>. Meson is great but from > a user's perspective it doesn't beat `./configure && make`. >From the user's perspective, users shouldn't have to build their own system libraries. From the developers point-of-view, the rules are actually readable, understandable, and it takes as long to build libfprint and the docs as it did just running configure. So I'm fine with the drawbacks :) > And actually there's quite a few ones who want to try it out but > don't have that much experience with build systems. If anyone has problems updating the Makefile.am/<a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a> rules for their WIP drivers, let me know. FWIW, unless additional files or libraries are needed, you'd only need to add the driver name to "all_drivers" in the top-level meson.build, and add a conditional in the "foreach driver: drivers" loop in libfprint/meson.build. > I'd like to follow the updates in the new repo but it won't let me > sign in. Says my account is blocked... There's no new repo, it's not migrated yet. > On Thu, May 17, 2018 at 7:01 PM Bastien Nocera <<a href="mailto:hadess@hadess.net" target="_blank">hadess@hadess.net</a>> > wrote: > > Hello all, > > > > libfprint has been ported to Meson[1] (from autotools) and gtk-doc > > (from Doxygen) in git. This means that building libfprint is now > > much > > much faster, and the API documentation is now clearer. > > > > It would be great if driver authors could update their development > > branches and report any problems. > > > > Let me know if you run into any problems building the library, or > > spot > > any errors in the documentation. > > > > Other short-term plans include migrating libfprint and fprintd to > > <a href="http://freedesktop.org" rel="noreferrer" target="_blank">freedesktop.org</a>'s gitlab instance[2], giving the website/wiki a > > refresh, and writing a guide to writing new drivers. > > > > Cheers > > > > [1]: <a href="http://mesonbuild.com/" rel="noreferrer" target="_blank">http://mesonbuild.com/</a> > > [2]: <a href="https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/</a> > > 21 > > _______________________________________________ > > 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>