On Sun, Mar 26, 2017 at 01:06:17PM -0600, Simon Glass wrote: > Some build systems have their own version of the pkg-config tool. > Use a variable for this instead of hard-coding it, to allow for this. > > Signed-off-by: Simon Glass <sjg@xxxxxxxxxxxx> > Suggested-by: Mike Frysinger <vapier@xxxxxxxxxxxx> This is good Makefile practice, regardless of anything else, so I've merged this. > --- > > Makefile | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Makefile b/Makefile > index 1d08ec1..e6d8251 100644 > --- a/Makefile > +++ b/Makefile > @@ -23,6 +23,7 @@ CFLAGS = -g -Os -fPIC -Werror $(WARNINGS) > BISON = bison > LEX = flex > SWIG = swig > +PKG_CONFIG ?= pkg-config > > INSTALL = /usr/bin/install > DESTDIR = > @@ -119,7 +120,7 @@ SCRIPTS = dtdiff > # We need both Python and swig to build pylibfdt. > .PHONY: maybe_pylibfdt > maybe_pylibfdt: FORCE > - if pkg-config --cflags python >/dev/null 2>&1; then \ > + if $(PKG_CONFIG) --cflags python >/dev/null 2>&1; then \ > if which swig >/dev/null 2>&1; then \ > can_build=yes; \ > fi; \ -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
