> > Some libraries are shipping with the right macros (e.g: gtk+, > glib, gnome, freetype2, etc.) QT does not ship these tools as > Trolltech probably assume you will use their qmake tool to > generate Makefiles. Theoretically, distros can fill this hole, > but I haven't seem them doing it and AFAIK the KDE libraries > are not shipped with m4 macros either. > > What Kdevelop does (AFAIR -- long time since I used it), is to > generate the required macros and scripts and than use them > in its configure.ac file.
Ok, although what you suggest is possible there is an easier solution in the form of qmake. The options that we have thought about are: 1. Manually using autotools to create Makefiles for the entire project, without using Kdevelop at all. Of course, the scripts you mentioned are still necessary. The original problem was that KDevelop itself was lousy at recompiling forms (ui files) and moc (meta object code) files. And since we've also had other object files that are built seperately, this created a mess. 2. Using qmake to create everything. QMake knows how to compile all ui and moc files (for the later it also adds them to the link process :) and is a snap to use. Trivial. For Qt applications, this is the way to go. It doesn't have all the bells and whistles of autotool's in terms of cross-platform development but for developing Qt/KDE apps, it is THE easiest tool that I've seen. FINALLY! Eli -- Eli Kara Beyond Security Ltd. http://www.beyondsecurity.com/ http://www.securiteam.com/ The First Integrated Network and Web Application Vulnerability Scanner: http://www.beyondsecurity.com/webscan-wp.pdf ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
