Qt-contributors-summit-2013-CMake-files-feedback-requests

From Qt Wiki
Revision as of 09:18, 6 February 2015 by Maintenance script (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  1. CMake files can be used elegantly for all platforms and most Qt configurations (shared/static/mac-framework/cross-compiles), especially with CMake 2.8.11
  2. # Recent features in CMake and Qt 5.1 implement ‘target usage requirements’ http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements
  3. # https://qt.gitorious.org/qt/qtbase/blobs/dev/tests/auto/cmake/test_interface/CMakeLists.txt
  4. Qt CI tests the CMake files in many scenarios in the build and install locations.
  5. Upcoming features in CMake upstream make using static Qt builds more elegant
  6. # A file needs to be generated whenever QtGui is used which loads the platform plugin (for qmake feature-parity). This will be automatic.
  7. # Support for multiple toolchains and proper sysroot handling will make using Qt in cross-compile scenarios more easy.
  8. CMake toolchain files for all platforms will be generated while building Qt: https://codereview.qt.io/#change,53858
  9. CMake functionality is growing ever-more declarative
  1. Use of CMake is growing more declarative. Ie from

to

in version 2.8.13.

  1. CMake might replace its current language with a more-declarative one (Lua).

Tasks:

  1. Improve Creator CMake support
  2. Complete the cross compiling features upstream
  3. Implement CPack generator for BB10 bar files.
  4. Implement UI in creator to create packages in all formats known to CPack