name the prf file libA.prf (up to lib authors, all they have to do is be consistent about their choice and document it).appB is an app that uses qmake as a build system and has libA as an optional dependencyĪ naive way of doing that is the following :.libA is a library that may or may not use Qt but whose developers a want to support qmake build system so they provide a.
The use of scopes allow simple "conditionnalization" of builds based on platform and could easily be used for more elaborate checks, like the example scenario below : For other uses I can use either one or the other or even write a dedicated Makefile if neither is available.Ĭan QMake even do platform checks like you'd find in CMake and Autohell? Depends what you mean with "platform checks".
For KDE4 applications I will prefer cmake over anything else because I'm not smart enough to setup my own build infrastructure for KDE applications. So to sum things up - for Qt only applications I will prefer qmake over cmake as long as qmake is a standard build tool for Qt. And let's not forget Qt needs to be deployed as well (in both cases). From what I've seen on QtCentre the latter yields more problems thus it is better if one experienced developer battles with qmake than if dozens of unexperienced Windoze end-users battle with both cmake (and its dependencies) and the final application itself. So this is really a battle between easing the development stage and easing the installation stage. But this all doesn't change a fact that if you want to deploy a Qt based application in a foreign environment it is easier to do it using qmake than using cmake once you have the build infrastructure set up properly. So this is obvious that many things are easier to obtain with cmake than with qmake because the former learned from the experience gathered by the latter. Let's face it - cmake is a next generation tool compared to qmake just as qmake is a next generation tool compared to autotools or tmake. And I always use CMake for any programming projects I do even when not using Qt4 and KDE4. Just take a little more time googling or asking in the #cmake channel on Freenode. Mandriva even rewrote Qt-Creator in CMake.ĬMake's documentation might be a little shotty but its not that bad.
QMake is great for small trivial applications but once you go from there to more complex it just makes it totally much harder. Qt3, KDE3, KDE4, OpenGL, etc.ĬMake gives me a clear thing so it easier to see compiler warnings, colourful output, and percentage of how much has compiled and gone by which I totally love. It's much easier to write a FindFoo.cmake to find libraries on any OS and have it available. And alot more people are moving from autotools to CMake. But it spits out all that verbose garbage that I can't stand seeing when problems are compiling just like with autotools. And since my app uses KDE4 I have to use CMake. Because I had a ton of problems setting up sub directories.
CMAKE VS CMAKE INSTALL REGISTRATION
If you have any problems with the registration process or your account login, please contact us.
CMAKE VS CMAKE INSTALL FREE
Registration is fast, simple and absolutely free so please, join our community today! By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. If you are looking for information about Qt related issue - register and post your question. Over 90 percent of questions asked here gets answered. Qt Centre is a community site devoted to programming in C++ using the Qt framework. Select the forum that you want to visit from the selection below. Before you can post: click the register link above to proceed.
0 kommentar(er)
