On Tuesday 02 March 2010 08:37:44 Michael Karcher wrote: > Am Dienstag, den 02.03.2010, 07:44 +1000 schrieb Kel Modderman: > > > The qmake build system in debhelper calls qmake, which, dependent on > > > installed packages, is either Qt 3 or the Qt 4 version. If both Qt > > > versions > > > are installed, qmake defaults to qmake-qt3 (priority 45) over qmake-qt4 > > > (priority 40), making the automatic build system unable to build Qt 4 > > > packages. > > In the future, these build systems may be able to handle their own specific > > options. This build system could accept a --qmake option which sets the > > qmake binary to be called. > That sounds like a good idea. > > > > An option to choose either qmake-qt3 or qmake-qt4, or even hard > > > wiring qmake-qt4 as the automatic build system is mainly used for new > > > packages that mainly use qt4 would be nice, IMHO. > > Hardcoding anything would be crap. > Which also applies to "qmake" (as it is now) as well. "qmake-qt4" is at > least consistent on all Debian Systems, without needing a > Build-Conflicts on Qt3's qmake.
Nah, I think 'qmake' is the best we can do right now. It works in a clean chroot (and can be made more robust with build-conflicts, but thats a pain for a host system) and allows to take advantage of benefits of honouring noopt, nostrip DEB_BUILD_OPTIONS, being able to easily override LDFLAGS and so on, which is what I wanted to do with my couple of measly qt packages. There is no way that I know of to detect if source files of qt projects require qt3 or qt4. Thanks, Kel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
