B2QT Build Release: Difference between revisions
From Variscite Wiki
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
=About Boot to Qt= | = About Boot to Qt = | ||
Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device. | Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device. | ||
| Line 15: | Line 15: | ||
The full B2Qt documentation is available at [http://doc.qt.io/QtForDeviceCreation Qt for Device Creation] official page. | The full B2Qt documentation is available at [http://doc.qt.io/QtForDeviceCreation Qt for Device Creation] official page. | ||
=Requirements= | = Requirements = | ||
You should be familiar with the Yocto tools and the concept of recipes. For more information, see Yocto Project [https://www.yoctoproject.org/documentation/current documentation]. | You should be familiar with the Yocto tools and the concept of recipes. For more information, see Yocto Project [https://www.yoctoproject.org/documentation/current documentation]. | ||
| Line 22: | Line 22: | ||
* Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required: | * Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required: | ||
sudo apt-get install gawk curl git-core diffstat unzip p7zip texinfo \ | $ sudo apt-get install gawk curl git-core diffstat unzip p7zip texinfo \ | ||
gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison \ | gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison \ | ||
g++-multilib | g++-multilib | ||
=Setting Up Yocto Build Environment= | = Setting Up Yocto Build Environment = | ||
Run the setup script that initializes the Yocto environment. | Run the setup script that initializes the Yocto environment. | ||
mkdir ~/var-b2qt | $ mkdir ~/var-b2qt | ||
cd ~/var-b2qt | $ cd ~/var-b2qt | ||
git clone {{#var:B2QT_GIT}} -b {{#var:B2QT_BRANCH}} | $ git clone {{#var:B2QT_GIT}} -b {{#var:B2QT_BRANCH}} | ||
cd meta-variscite-boot2qt | $ cd meta-variscite-boot2qt | ||
./b2qt-init-build-env init --device {{#var:MACHINE_NAME}} | $ ./b2qt-init-build-env init --device {{#var:MACHINE_NAME}} | ||
b2qt-init-build-env has the following additional command line options: | b2qt-init-build-env has the following additional command line options: | ||
| Line 43: | Line 43: | ||
For all command line options, see: | For all command line options, see: | ||
./b2qt-init-build-env help | $ ./b2qt-init-build-env help | ||
=Building the Image and Toolchain= | = Building the Image and Toolchain = | ||
After the Yocto environment is set up, you need to configure the build environment for your target device: | After the Yocto environment is set up, you need to configure the build environment for your target device: | ||
MACHINE={{#var:MACHINE_NAME}} source ./setup-environment.sh | $ MACHINE={{#var:MACHINE_NAME}} source ./setup-environment.sh | ||
Yocto recipes for Boot to Qt for embedded Linux have two main targets to build: The target image, and the external toolchain that can be used with Qt Creator for building Qt applications. | Yocto recipes for Boot to Qt for embedded Linux have two main targets to build: The target image, and the external toolchain that can be used with Qt Creator for building Qt applications. | ||
MACHINE={{#var:MACHINE_NAME}} bitbake b2qt-embedded-qt5-image | $ MACHINE={{#var:MACHINE_NAME}} bitbake b2qt-embedded-qt5-image | ||
MACHINE={{#var:MACHINE_NAME}} bitbake meta-toolchain-b2qt-embedded-qt5-sdk | $ MACHINE={{#var:MACHINE_NAME}} bitbake meta-toolchain-b2qt-embedded-qt5-sdk | ||
The target rootfs image is located | The target rootfs image is located at: | ||
~/var-b2qt/meta-variscite-boot2qt/build-{{#var:MACHINE_NAME}}/tmp/deploy/images/{{#var:MACHINE_NAME}}/b2qt-embedded-qt5-image-{{#var:MACHINE_NAME}}.img | ~/var-b2qt/meta-variscite-boot2qt/build-{{#var:MACHINE_NAME}}/tmp/deploy/images/{{#var:MACHINE_NAME}}/b2qt-embedded-qt5-image-{{#var:MACHINE_NAME}}.img | ||
and the new toolchain is | and the new toolchain installation file is: | ||
~/var-b2qt/meta-variscite-boot2qt/build-{{#var:MACHINE_NAME}}/tmp/deploy/sdk/b2qt-x86_64-meta-toolchain-b2qt-embedded-qt5-sdk-{{#var:MACHINE_NAME}}.sh | ~/var-b2qt/meta-variscite-boot2qt/build-{{#var:MACHINE_NAME}}/tmp/deploy/sdk/b2qt-x86_64-meta-toolchain-b2qt-embedded-qt5-sdk-{{#var:MACHINE_NAME}}.sh | ||
=Flashing the SD card image= | = Flashing the SD card image = | ||
Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX) | Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX) | ||
| Line 72: | Line 72: | ||
Replace /dev/sdX with your actual device name, e.g. /dev/sdb | Replace /dev/sdX with your actual device name, e.g. /dev/sdb | ||
=Creating an extended SD card= | = Creating an extended SD card = | ||
Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card. The script copies the NAND/eMMC flash burning scripts and relevant binaries for your convenience.<br> | Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card. The script copies the NAND/eMMC flash burning scripts and relevant binaries for your convenience.<br> | ||
Revision as of 14:45, 25 June 2018
- Boot to Qt based on Yocto
About Boot to Qt
Boot to Qt is a light-weight, Qt-optimized, full software stack for embedded Linux systems that is installed into the actual target device.
The stack can be customized to production with Build-Your-Own-Stack tooling, including proprietary Yocto Project recipes.
The full B2Qt documentation is available at Qt for Device Creation official page.
Requirements
You should be familiar with the Yocto tools and the concept of recipes. For more information, see Yocto Project documentation.
To get started, you need the following:
- Install the dependencies for the Yocto tools. In Ubuntu, the following packages are required:
$ sudo apt-get install gawk curl git-core diffstat unzip p7zip texinfo \ gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison \ g++-multilib
Setting Up Yocto Build Environment
Run the setup script that initializes the Yocto environment.
$ mkdir ~/var-b2qt $ cd ~/var-b2qt $ git clone -b $ cd meta-variscite-boot2qt $ ./b2qt-init-build-env init --device
b2qt-init-build-env has the following additional command line options:
- list-devices: show all supported devices that can be used for a Boot to Qt build
- mirror: create a local mirror of the yocto repositories. This enables you to use the same repository downloads for multiple build environments, when initializing with init --reference <mirror path>.
For all command line options, see:
$ ./b2qt-init-build-env help
Building the Image and Toolchain
After the Yocto environment is set up, you need to configure the build environment for your target device:
$ MACHINE= source ./setup-environment.sh
Yocto recipes for Boot to Qt for embedded Linux have two main targets to build: The target image, and the external toolchain that can be used with Qt Creator for building Qt applications.
$ MACHINE= bitbake b2qt-embedded-qt5-image $ MACHINE= bitbake meta-toolchain-b2qt-embedded-qt5-sdk
The target rootfs image is located at:
~/var-b2qt/meta-variscite-boot2qt/build-/tmp/deploy/images//b2qt-embedded-qt5-image-.img
and the new toolchain installation file is:
~/var-b2qt/meta-variscite-boot2qt/build-/tmp/deploy/sdk/b2qt-x86_64-meta-toolchain-b2qt-embedded-qt5-sdk-.sh
Flashing the SD card image
Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
$ sudo umount /dev/sdX* $ sudo dd if=tmp/deploy/images//b2qt-embedded-qt5-image-.img of=/dev/sdX bs=1M && sync Replace /dev/sdX with your actual device name, e.g. /dev/sdb
Creating an extended SD card
Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card. The script copies the NAND/eMMC flash burning scripts and relevant binaries for your convenience.
Later, you will be able to follow Yocto Recovery SD card guide to burn your images to NAND flash or eMMC.
Plug the SD card into your Linux HOST PC, run "dmesg|tail" and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
$ cd ~/var-b2qt/meta-variscite-boot2qt $ sudo MACHINE= sources/meta-variscite-fslc/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh /dev/sdX Replace /dev/sdX with your actual device name, e.g. /dev/sdb