diff options
author | Samuli Piippo <samuli.piippo@digia.com> | 2014-03-14 12:56:44 +0200 |
---|---|---|
committer | Samuli Piippo <samuli.piippo@digia.com> | 2014-03-14 14:52:43 +0200 |
commit | f5adb6e04035adcfa2d31b5328d01436b2a7ce65 (patch) | |
tree | cab18e606c3c90acbc043d9d2de5aa435389d174 | |
parent | 4738811e35a559d238ba20703eb792fca8f5756b (diff) |
doc: how to use rebuilt yocto images and BYOS
Change-Id: Ic983c7e6d05aad190bb1469cc318993720d190c3
Reviewed-by: Topi Reiniƶ <topi.reinio@digia.com>
-rw-r--r-- | src/doc/src/b2qt.qdoc | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index 6f2d44c..ca23881 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -894,7 +894,7 @@ Run the setup script that initializes the Yocto environment: \code - cd <your/yocto/build/directory> + cd <YoctoBuildDir> <INSTALL_DIR>/Boot2Qt-2.x/sources/b2qt-yocto-meta/b2qt-init-build-env . \endcode @@ -919,6 +919,9 @@ bitbake meta-toolchain-b2qt-embedded-sdk \endcode + The target rootfs image is located in the \c <YoctoBuildDir>/tmp/deploy/images/<target>/b2qt-embedded-image-<target>.tar.gz, + and the new toolchain is in \c <YoctoBuildDir>/tmp/deploy/sdk/b2qt-eglibc-x86_64-meta-toolchain-b2qt-embedded-sdk-<target-architecture>-toolchain-1.5.sh + \note The generated target image does not yet include Qt libraries, you need to build Qt and add it into the image yourself. @@ -931,10 +934,17 @@ an example: \code - cd <your/qt/build/directory> + cd <B2QtBuildDir> <INSTALL_DIR>/Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-common/init_build_env.sh <INSTALL_DIR>/Boot2Qt-2.x/sources/b2qt-build-scripts/embedded-linux/config.raspberrypi \endcode + \note You should use different build directories for Qt and the Yocto image. + + If you have rebuilt your own Yocto target image and toolchain, you can replace the + \c rootfs.tar.gz and \c toolchain.sh in the current Qt build directory with the ones generated by bitbake. + Bitbake does not generate the \c boot.tar.gz packages used by \B2Q, so you may need to update it manually + with files from bitbake. + You can use following scripts to build different parts of the \B2Q stack. \code |