diff options
author | Laszlo Agocs <laszlo.agocs@digia.com> | 2013-10-11 18:09:51 +0200 |
---|---|---|
committer | Laszlo Agocs <laszlo.agocs@digia.com> | 2013-10-14 12:38:52 +0300 |
commit | 58099ab120d14f8c37636bfe61392fadd3a6d617 (patch) | |
tree | 97880b402c7ad57bb9064ca01a8807ab3093e3a3 | |
parent | 84732e0ef58b3ed8d06f688d4076757ac2dfbb82 (diff) |
Doc: Add some words about deployment paths
It's very nice that new projects generated by Creator deploy properly
but we really need to say a few words about running existing projects
(for example Qt's own examples).
The Qt examples, say shadereffects from qtdeclarative, won't deploy
by default since target.path is garbage. It has to be manually updated
to /data/user/qt/whatever. Document this.
Change-Id: I8d09c091d449b8b4ad519210a938f9b56195bb60
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@digia.com>
-rw-r--r-- | src/doc/src/b2qt.qdoc | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index be4b8ba..c5808b8 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -636,6 +636,28 @@ connected device. \li To build and run the project, click \inlineimage qtcreator-run.png \endlist + + \section1 Setting up an already existing project for deployment + + The projects generated by Qt Creator will always have the correct settings + for deployment on the device or emulator. Existing projects may need some + changes however. + + As a general rule, application binaries and content (like QML files) are + deployed under /data/user/qt/<APPLICATION_NAME>. This means that deployment + settings in .pro files like the following: + + \code + target.path = ... + INSTALLS += target + \endcode + + should be migrated to + + \code + target.path = /data/user/qt/<APPLICATION_NAME> + INSTALLS += target + \endcode */ /*! |