On Wednesday 01 September 2004 20:18, Oron Peled wrote: > You don't need to keep the Makefile, Makefile.in, configure, > config.* etc, all of them are generated. The sources of these > (which you want to maintain via CVS) are Makefile.am > and configure.ac (or configure.in in old autoconf). > > Note that AFAIR kdevelop uses a host of custom scripts/macros > so you may want to dig deeper for other worthwhile files. > > One easy way to remove the generated files (so you can isolate > the files needed to be added to CVS) is to run: > make maintainer-clean > > Hope it helps,
Oron, The big question for me is how to create build rules for the QObject derived classes in a Qt application. There are two important things that need to be done: 1. If your UI was created using Qt Designer, you must have a way to compile the ui file, i.e: running uic and creating the header + cpp file. 2. Create a MOC file for the class by running moc and then linking the resulting file (or #include it in the main implementation file of the class). This step must be done regardless of the way the UI was designed. Now the big question is how to perform these with autotools. The commands themselves are fairly simple (requiring only one or two arguments) but the way autotools works is by specifying source files and other options in the *.am files (which I assume will eventually create a Makefile that uses gcc/g++ to compile the source files). Could it be that kdevelop's custom scripts are used to do exactly this ? Or is there another way to do this with autotools ? Regards, -- 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]
