unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: configure's dependency on pkg-config
Date: Sun, 13 Nov 2011 12:08:18 +0100	[thread overview]
Message-ID: <9BC8D65A-EC69-4BF8-9A48-67DBC7A8989D@swipnet.se> (raw)
In-Reply-To: <8739dshp2t.fsf@escher.home>


Hello.

13 nov 2011 kl. 00:56 skrev Stephen Berman:

> On Sun, 13 Nov 2011 00:12:43 +0100 Jan Djärv <jan.h.d@swipnet.se> wrote:
> 
>> I don't know why you are opposed to installing pkg-config, but it is not Emacs
>> choice.  libxml2 has made pkg-config the way for users of that library to find
>> out compiler and linker flags as well as dependencies on other libraries.  So
>> of course Emacs uses that.  Who are we to argue about the validity of that
>> descision?  Ditto for Gtk, dbus, and others.
> 
> I'm not opposed to installing pkg-config, I just didn't know I was
> supposed to to get Emacs to use libxml2, until I looked in configure.
> If it had been documented in INSTALL, I would have been spared that
> effort and time.  (That libxml2 provides pkg-config data I also didn't
> know: I just checked, and the only mention of "pkg-config" in the entire
> libxml2-2.7.8 source tree is in the ChangeLog, which I didn't read
> before installing libxml2.)
> 

Every package that can be used provides the pkg-config data.  The one for libxml2 is generated from libxml-2.0.pc.in in the source.
I think pkg-config is considered standard, so along with tar, cp and other standard utilities, it is not mentioned.  It is only a problem for people building their own distributions, which is far fewer nowdays that say 10 years ago.  And if you are doing that, pkg-config is really something you need to install.  But adding it to INSTALL is not a big deal.

The reason for not mentioning all the libraries using pkg-config in INSTALL is that almost all new libraries support it.  So we would probably need to add every new library Emacs uses to INSTALL.

	Jan D.




  reply	other threads:[~2011-11-13 11:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 19:25 configure's dependency on pkg-config Stephen Berman
2011-11-12 14:13 ` Jan Djärv
2011-11-12 22:33   ` Stephen Berman
2011-11-12 22:59     ` Glenn Morris
2011-11-12 23:56       ` Stephen Berman
2011-11-13  0:32         ` Paul Eggert
2011-11-12 23:12     ` Jan Djärv
2011-11-12 23:56       ` Stephen Berman
2011-11-13 11:08         ` Jan Djärv [this message]
2011-11-14 14:01     ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9BC8D65A-EC69-4BF8-9A48-67DBC7A8989D@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).