unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: pkg-config required on OSX, why?
Date: Fri, 16 May 2014 15:38:48 +0200	[thread overview]
Message-ID: <537614E8.7050401@swipnet.se> (raw)
In-Reply-To: <83y4y1eush.fsf@gnu.org>

Hi.

Eli Zaretskii skrev 2014-05-16 15:07:
>> Date: Fri, 16 May 2014 13:01:23 +0200
>> From: "Jan D." <jan.h.d@swipnet.se>
>>
>> Why is pkg-config a requirement on OSX?
>
> Are you sure it is needed for building Emacs, and not just for running
> autogen.sh/aclocal in order to produce the configure script when
> building out of the repository?

It is requred for that also, but pkg-config is run in configure also.

>
> The latter is indeed new, and is because configure.ac now calls a
> macro that is defined by pkg.m4, which comes with pkg-config.
>

Yes, I saw those undefined macros (I think it was three) when trying to 
build without pkg-config after tweaking autogen.sh.

I built pkg-config from source, but having pkg-config as a requirement 
form some macros must mean those macros are important.  What are they?

	Jan D.




  reply	other threads:[~2014-05-16 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 11:01 pkg-config required on OSX, why? Jan D.
2014-05-16 13:07 ` Eli Zaretskii
2014-05-16 13:38   ` Jan D. [this message]
2014-05-16 14:24     ` Paul Eggert
2014-05-16 15:52       ` Stefan Monnier
2014-05-16 15:52       ` Paul Eggert
2014-05-16 16:48         ` Glenn Morris
2014-05-16 16:50         ` Jan D.
2014-05-16 19:04           ` Paul Eggert
2014-05-17  6:41             ` Jan Djärv
2014-05-16 15:57     ` Glenn Morris
2014-05-16 16:39       ` Jan D.
2014-05-16 16:46         ` Glenn Morris
2014-05-16 17:45           ` Jan D.

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=537614E8.7050401@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).