Does anyone pass Qt to their own source of control?

Question

Does anyone pass Qt to their own source of control? If so, how do you do it? You commit the entire Qt directory or select only those that your application needs (bin / lib / include / src)

How do you deal with the situation when a new version of Qt is released?

I ask because I'm trying to configure Build Automation and the Qt moc is a little sore ... and just wondering how people handle a third-party library in general.

Answer 1

In my company, we don’t pass Qt to the source code, we compile it separately on the build machines and then refer to it in the project, whether it be C ++, Java (Jambi) or Python (PyQt).

/ DLL .. . , CMake by Kitware.

http://www.cmake.org/

-. , CPack, CTest CDash Kitware. ( : Kitware, , Kitware).

, Qt QMake, Qt.

Answer 2

, , , , , . , , , . , , , , ! Microsoft !

Answer 3

git git -. (git, svn ..), , "git subodule", . , . , - .

See: http://www.kernel.org/pub/software/scm/git-core/docs/git-submodule.html