|
From: Julian S. <js...@ac...> - 2008-07-30 10:03:41
|
On Wednesday 30 July 2008 11:48, Tom Hughes wrote: > In message <200...@ac...> > Julian Seward <js...@ac...> wrote: > > > Also, what happens if I want to use a non-default Qt4, that is, one which > > I build from source and pkg-config knows nothing about? What then? > > Then you set PKG_CONFIG_PATH to point at the directory with the .pc > file for your build ;-) 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? J |