On Mon, Mar 17, 2014 at 09:33:50PM +0100, John Tytgat wrote: > In message <[email protected]> > Vincent Sanders <[email protected]> wrote: > > > Also there is no pkg-config file which makes runtime detection a pain, > > the author seems disinclined to add such a file either as autoconf > > obviously does not require them and being a GNU project he follows the > > one true GNU way. > > autoconf is pretty orthogonal to what pkg-config offers. You can easily > use a pkg-config published library in an autoconf project. And it is > easy to support pkg-config in an autoconf based project as well. > > One should not exclude the other, they are complementing each other. >
Indeed they can. > I don't see why one couldn't consider upstreaming a pkg-config support > patch to libidn2 project. Ah, you perhaps misunderstood me, libidn2 is developed by developers who follow the GNU project guidelines. When I gently introduced the idea of having a pkg-config to them It was explained robustly in return by them that one should use autoconf to achive build time config not use pkg-config. It was futher suggested that this is GNU projects default position and then there were some questioning of my personal sanity and other such comments. I decided not to persue the matter futher as this was just a minor part of my overall unease with relying on an additional external library. The objections are borne from multiple concerns rather than any single point. > > John. > -- > John Tytgat > [email protected] > > -- Regards Vincent http://www.kyllikki.org/
