On Wednesday, November 02, 2011 12:33:02 Oswald Buddenhagen wrote: > what exactly is it that you need cmake itself for?
* Generating Targets files, including not haviing to care about what the prefix or suffix on libraries is, and without doing a bad reimplementation of a generator for them as I have currently done. * The ability to install something like CreateBasicQtConfig.cmake which can then be found by a the cmake executable to create the QtWebkitConfig.cmake which is not in qtbase. Currently I'd have to either install the create_basic_cmake_config_files.sh or duplicate it. Can qmake solve that problem? * Less for me to maintain. Others on this list have already made clear that they will block dependence on the cmake executable, so let's just move on and see how we can do the best without it. > > you don't need sed. use QMAKE_SUBSTITUTES (see creator sources for > "documentation"). in fact, the shell scripts look easy enough that you > could rewrite them in qmake entirely. Possibly. I'm not familiar enough with the existing Qt buildsystem to know where to look or where to put stuff. If you give me pointers or even a patch to start with I can do the rest. What would implementing it in QMake instead of shell script get us? Does qmake know anything that shell scripts do not? Thanks, -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
