diff options
| author | Qt Forward Merge Bot <qt_forward_merge_bot@qt-project.org> | 2019-10-12 03:00:50 +0200 |
|---|---|---|
| committer | Qt Forward Merge Bot <qt_forward_merge_bot@qt-project.org> | 2019-10-12 03:00:50 +0200 |
| commit | 9bf8b9727e34514b129e448e390aaa4077c79c8d (patch) | |
| tree | 5bef01e069021a04ac14181aef8ab3fbe3a56045 | |
| parent | 2b0af1e7bb1a6a52d90f904ca05bedf52d5df901 (diff) | |
| parent | 0c2dba6114301bd3c2aa60fde36a6b4880585831 (diff) | |
Merge remote-tracking branch 'origin/5.14' into 5.15
Change-Id: Ic7e7a9d0a50e9f2c61d24189cec8a537115ac3df
| -rw-r--r-- | src/activeqt/doc/src/activeqt-dumpcpp.qdoc | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/src/activeqt/doc/src/activeqt-dumpcpp.qdoc b/src/activeqt/doc/src/activeqt-dumpcpp.qdoc index 11ae652..ee37f51 100644 --- a/src/activeqt/doc/src/activeqt-dumpcpp.qdoc +++ b/src/activeqt/doc/src/activeqt-dumpcpp.qdoc @@ -70,8 +70,11 @@ \li Print help \endtable - \c dumpcpp can be integrated into the \c qmake build system. In your .pro - file, list the type libraries you want to use in the TYPELIBS variable: + Running the tool manually (and perhaps even checking the generated files into your version + control system) is usually sufficient, as type libraries change very rarely. + If your type library changes frequently, then you can integrate \c dumpcpp into the \c qmake + build system. In your .pro file, list the type libraries you want to use in the TYPELIBS + variable: \snippet activeqt/qutlook/qutlook.pro 0 |