diff options
author | Alexandru Croitor <alexandru.croitor@qt.io> | 2021-09-22 18:45:14 +0200 |
---|---|---|
committer | Alexandru Croitor <alexandru.croitor@qt.io> | 2021-09-27 21:36:36 +0200 |
commit | 96659297064ad0eb15f173a4452d349e8d43e2c5 (patch) | |
tree | 16dec2adee2a813ea6d17fc610a39a8061771026 /src/plugins/platforms/cocoa | |
parent | 124f7c681fd74f01aaa60dc31c26e51c52f2b1e9 (diff) |
pro2cmake: Generate public CMake API code for projects by default
Previously pro2cmake assumed that all .pro were internal Qt projects
like qtbase/src/corelib.pro and generated private api calls like
qt_internal_add_module().
Public CMake API calls (like qt_add_executable) were only generated if
an --is-example command line flag was passed to the script or if the
.pro file was located under the examples subfolder of a qt repo source
directory (indicated by the presence of a .qmake.conf file).
Change the logic to always generate public CMake API code by default,
unless a .cmake.conf/.qmake.conf file is encountered with a valid repo
module version inside, in which case apply the old heuristic of
checking for the ./examples subfolder.
The intention is to have a sensible default so that Qt users can use
the script to more easily migrate their qmake projects without having
to explicitly specify the --is-example flag.
Pick-to: 6.2
Task-number: QTBUG-96799
Change-Id: I38f4f1b349a5b9688cf7bc5914d4fde72e660a98
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Diffstat (limited to 'src/plugins/platforms/cocoa')
0 files changed, 0 insertions, 0 deletions