|
From: Julian S. <js...@ac...> - 2008-07-30 09:39:44
|
> > How bad does the cumbersome code look? Is it the Qt4 checking stuff > > in configure.in r8465, or some other un-committed changes you have? > > Writing configure tests for detecting e.g. the Qt4 package compared to > using pkg-config is something like reinventing the wheel. E.g. for > some distro's the Qt4 include path is /usr/include, for other distro's > it is /usr/include/qt4 and maybe there exist even other choices. I > don't think there even exists a clean way to find out from the > configure script any path a distro could come up except by using > pkg-config. Additionally, sometimes additional compiler flags have to > be passed to the compiler for compiling Qt4 code. Trying to figure out > these flags from the configure script would be more duplication of > information already known by pkg-config. Is it at least possible to arrange it so that configure does not fail if pkg-config is not installed? I don't want to acquire a dependency on pkg-config. 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? J |