diff options
| author | Volker Hilsheimer <volker.hilsheimer@qt.io> | 2019-10-08 18:17:04 +0200 |
|---|---|---|
| committer | Volker Hilsheimer <volker.hilsheimer@qt.io> | 2019-10-09 11:50:52 +0200 |
| commit | 0c2dba6114301bd3c2aa60fde36a6b4880585831 (patch) | |
| tree | 5b82b2e2522501cd0d6f9a1366114258fcc4ad09 | |
| parent | 203c6f9cc25f2bb40f6098f50e587467f874cf15 (diff) | |
Document that it's usually sufficient to run dumpcpp manuallyv5.14.0-beta2
Type libraries are like system libraries, so they rarely change. The
dependency generated by qmake for all object files to the generated
output can be overkill, even though that output should really not
change that much automatically.
Fixes: QTBUG-66924
Change-Id: Iab2777b63ddb9d16aac7eb8bec634572be8de418
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
| -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 |