> I'm using the QMAKE_MAKEFILE setting in a .pro file, and when I invoke > qmake on the command-line, it produces a makefile with the specified > name. However, when I build using QtCreator, even though the makefile > with the proper name is created (because QtCreator invokes qmake), > QtCreator does not attempt to run make on that resulting makefile. I > suspect it runs 'make' without parameters, which looks for a file > named "Makefile" (which in my case does not exist) > > Should QtCreator run make on the makefile specified by the .pro file's > QMAKE_MAKEFILE? I understand that the .pro.user file can contain > additional make arguments for the make step (under projects, build > settings, build steps), however I don't think it's a good idea to > check .pro.user files into revision control, so I'd rather not use > that setting. IMO the best case would be for QtCreator to be able to > build for any valid .pro file, without further separate tweaks being > required. > > I am trying to modify qtcreator to effectively use QMAKE_MAKEFILE, if > I succeed I will submit a patch. If there's a philosophical reason > why that change would be undesirable, I'd like to know about it now, > before I spend more time working on it. Alternatively, if a QtCreator > developer views this as a bug and would like to work on it, I would > appreciate it. The tricky case is if someone sets QMAKE_MAKEFILE to different values based on different scopes. That's currently impossible to support. Otherwise it should be doable. Though I haven't looked at that in detail.
daniel _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
