From 58099ab120d14f8c37636bfe61392fadd3a6d617 Mon Sep 17 00:00:00 2001 From: Laszlo Agocs Date: Fri, 11 Oct 2013 18:09:51 +0200 Subject: 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 --- src/doc/src/b2qt.qdoc | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) 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/. 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/ + INSTALLS += target + \endcode */ /*! -- cgit v1.2.3