gnome-keyring: Don't hard-code pkg-config executable
authorHeiko Becker <heirecka@exherbo.org>
Tue, 14 Jun 2016 11:27:05 +0000 (13:27 +0200)
committerJunio C Hamano <gitster@pobox.com>
Tue, 14 Jun 2016 20:06:10 +0000 (13:06 -0700)
Helpful if your pkg-config executable has a prefix based on the
architecture, for example.

Signed-off-by: Heiko Becker <heirecka@exherbo.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
contrib/credential/gnome-keyring/Makefile
index c3c7c98aa126470a4794903bc1e6b3be9b6d58cf..22c19df94b8177c6f264f1053f44f5ead259e730 100644 (file)
@@ -4,12 +4,13 @@ all:: $(MAIN)
 CC = gcc
 RM = rm -f
 CFLAGS = -g -O2 -Wall
+PKG_CONFIG = pkg-config
 
 -include ../../../config.mak.autogen
 -include ../../../config.mak
 
-INCS:=$(shell pkg-config --cflags gnome-keyring-1 glib-2.0)
-LIBS:=$(shell pkg-config --libs gnome-keyring-1 glib-2.0)
+INCS:=$(shell $(PKG_CONFIG) --cflags gnome-keyring-1 glib-2.0)
+LIBS:=$(shell $(PKG_CONFIG) --libs gnome-keyring-1 glib-2.0)
 
 SRCS:=$(MAIN).c
 OBJS:=$(SRCS:.c=.o)