Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Qt uses qmake to transparently support Qt’s various addons, including “moc, the meta-object compiler” (which provides signals & slots), “uic, the ui compiler” (which creates header files from .ui designer files), “rcc, the resource compiler” (which compiles resources).
There’s nothing to stop you using any build system you want. however, it’s a lot more work. For example, you need to run “moc” over every header file that contains a class that has signals or slots. In general it’s not recommended, especially for someone who’s just starting to use Qt.
QMake does not call g++/gcc directly. Instead, qmake creates native make files on your current platform. Under linux it creates standard GNU make files, under windows it can generate visual studio make files, under Mac OS X it can generate XCode project files. You then invoke your native build system (either GNU make, or MS NMake, or xcodebuild or whatever), which will call your native compiler (g++/gcc or whatever).