|
From: Bart V. A. <bar...@gm...> - 2008-07-30 10:35:02
|
On Wed, Jul 30, 2008 at 11:55 AM, Julian Seward <js...@ac...> wrote: > Well ok :-), but how about if I am trying to build against Qt4 on a > machine which doesn't have pkg-config installed? Using pkg-config > seems ok providing it doesn't induce a hard dependency; but I think > there needs to be a way to force the build to use a particular path > to Qt4 if pkg-config is either missing or doesn't produce the required > results for whatever reason. Maybe something like a --with-qt4= > configure flag? Since the file /usr/share/aclocal/pkg.m4 is distributed under the GPLv2 license, we could distribute this file together with Valgrind. This would require less work than implementing a --with-qt4 configure option. Does anyone know whether it is possible to start autoconf in such a way that m4 reads the system-provided pkg.m4 if present, and the pkg.m4 file distributed with Valgrind if there is no system-provided pkg.m4 ? Bart. |