CMake Port/Porting Guide: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
Line 25: Line 25:
  python3 qtbase/util/cmake/run_pro2cmake.py qtbase/examples
  python3 qtbase/util/cmake/run_pro2cmake.py qtbase/examples
  python3 qtbase/util/cmake/run_pro2cmake.py qtsvg
  python3 qtbase/util/cmake/run_pro2cmake.py qtsvg
If a directory has a configure.json, you'll want to run a script called configurejson2cmake.py to generate a configure.cmake file. These files should not be modified manually, but rather the script should be fixed to handle your specific case.
python3 qtbase/util/cmake/configurejson2cmake.py qtbase/src/corelib
=== Common qmake <-> CMake constructs ===
{| class="wikitable"
|-
! qmake !! CMake
|-
| qtHaveModule(foo) || if(TARGET Qt::foo)
|-
| qtConfig(foo) || if (QT_FEATURE_foo)
|-
| LIBS += zlib || target_link_libraries(my_target PRIVATE ZLIB::ZLIB)
|}

Revision as of 14:37, 23 May 2019

Porting Notes

General porting guide

There is a python script called pro2cmake.py in qtbase/cmake/utils.

It takes a .pro file as input, and generates a CMakeLists.txt file in the same folder. You need to have python3 installed and a few packages from pip (pyparsing, sympy) to use the script.

Example:

python3 qtbase/util/cmake/pro2cmake.py qtbase/src/corelib/corelib.pro

The script does a good chunk of the conversion process for you, but you'll sometimes need to do manual fixes to the file. Make sure to mark those manual changes with a "# special case" marker. Example:

SOURCES
 foo.cpp
 bar.cpp # special case

This way when you re-run the script, you won't lose your manual modifications. You can also use block special case markers:

# special case begin
LIBRARIES
  Qt::Gui
# special case end

There is also another script called run_pro2cmake.py which runs the first script recursively on all .pro files in the given folder. A good place to use it would be on the examples folder, or on the whole repository you are porting: Example:

python3 qtbase/util/cmake/run_pro2cmake.py qtbase/examples
python3 qtbase/util/cmake/run_pro2cmake.py qtsvg

If a directory has a configure.json, you'll want to run a script called configurejson2cmake.py to generate a configure.cmake file. These files should not be modified manually, but rather the script should be fixed to handle your specific case.

python3 qtbase/util/cmake/configurejson2cmake.py qtbase/src/corelib

Common qmake <-> CMake constructs

qmake CMake
qtHaveModule(foo) if(TARGET Qt::foo)
qtConfig(foo) if (QT_FEATURE_foo)
LIBS += zlib target_link_libraries(my_target PRIVATE ZLIB::ZLIB)