Lines Matching full:to
7 This chapter serves as a guide to help you create a recipe for an application
9 (64-bit), it can be applied to any board in a similar way.
32 Use Git to clone the required repositories
67 To understand better what is going on, let's build the image like it is
72 cd ../ # go back to the root folder
75 Now you should have a folder named ``build`` next to ``sources``. The last
77 also sets the current directory to the build directory.
93 To add layers to the project there are 2 options:
97 You need to be in the same terminal you did the ``source`` command. Add the
129 To ensure the layers were added as expected, run the Bitbake command to show
153 To build an image for Raspberrypi3 64 bits, modify the file ``local.conf`` file
160 To build the image we will target, it is also needed to add this to the file:
170 Everything is setup, time to build the image::
178 Let's go through the build folders to understand what happened.
200 - **images**: it contains the images that can be flashed or deployed to
211 that you can use to cross-compile applications for your target system.
218 This folder is a modular approach introduced in Yocto to handle sysroots. It
222 Each component corresponds to a specific package or dependency that is staged
228 one package changes, Yocto only needs to update the corresponding component
235 - ``raspberrypi3_64``: Files specific to the Raspberry Pi 3 (64-bit).
238 - ``x86_64-nativesdk``: Files related to the SDK for cross-compilation on
241 Each folder corresponds to components relevant to the specific architecture,
242 and they collectively form the complete environment needed to compile and run
248 The sysroots-uninative directory in Yocto is used to support the "uninative"
251 provides a way to use the same native build tools across different Linux
279 is where you'll look when a build fails to figure out what went wrong.
310 Let's dive into this recipe to understand what is done. The objective is to add
311 this library as a shared object in the target rootfs, and also to generate a
329 │ └── 0008-fix-fbdev-set-resolution-prior-to-buffer.patch
338 - ``lvgl_9.1.0.bb`` is the recipe to build lvgl library.
339 - ``lvgl-demo-fb_9.1.0.bb`` is a recipe to build an application using lvgl.
350 DESCRIPTION = "LVGL is an OSS graphics library to create embedded GUI"
359 file://0008-fix-fbdev-set-resolution-prior-to-buffer.patch \
383 for the license file (here assumed to be LICENCE.txt). This helps to ensure the
385 there is a LICENSE.txt. To get the value of the hash of the file, you can do
390 - The following arguments are the local patch files that will be applied to
401 **EXTRA_OECMAKE**: Additional options passed to CMake during the
406 variable in BitBake that points to the working directory for the recipe.
409 specific to the LVGL library.
411 **FILES**: This is a BitBake variable used to specify the files that should
413 specifying files for a package related to development (i.e., header
420 manually to understand what is generated each step, or you can run ``bitbake
421 lvgl`` to run all the tasks.
430 The fetch Repo address has to be stored in **SRC_URI** variable. In
466 Patch task locates the patch files and applies the patches to the sources
484 In this case, it creates a build directory, It invokes CMake to configure
492 sysroots have everything required to build lvgl library.
513 After this task has been completed, everything is ready to be installed.
520 The Install task copies files that are to be packaged into the holding area
530 The lvgl library (``.so`` files) are also ready to be installed in the final
544 the library to the host SDK we will generate later on.
553 rpm/cortexa53/lvgl-9.1.0-r0.cortexa53.rpm`` and other rpm files related to
563 ready-to-use development environment tailored for a specific target
565 This includes the necessary tools, libraries, and headers to build
567 - **Cross-Compilation**: The SDK allows developers to cross-compile
573 Developers don't need to manually install and configure tools and
577 build, which helps to avoid compatibility issues and ensures that
580 To generate an SDK of the environment, run the following command:
588 sh``. This script allows you to install the SDK where you prefer. Here is the
597 You are about to install the SDK to "/opt/poky/sdk-with-lvgl". Proceed [Y/n]? y
599 If you want to ensure the SDK was generated with lvgl being installed, go to
609 Now to use the SDK environment and cross-compile an application:
625 recipes. The objective here is to create a recipe from scratch and to add the
631 First, create a layer and add it to the configuration file
655 Following this structure, create a folder containing the recipes to build 1
677 # Update SRC_URI to point to the GitHub repository
679 file://0001-change-config-file-to-run-fbdev-with-2-threads.patch \
680 file://0002-adapt-CMakeLists-file-to-compile-and-link-fbdev.patch \
695 The sources come from ``lv_port_linux`` repository. We apply 2 patches to modify the ``CMakeLists.t…
704 touch 0001-change-config-file-to-run-fbdev-with-2-threads.patch
706 Content of ``0001-change-config-file-to-run-fbdev-with-2-threads.patch``
713 Subject: [PATCH] change config file to run fbdev with 2 threads
753 * NOTE: If FreeType or ThorVG is enabled, it is recommended to set it to 32KB or more.
767 /* Use Arm-2D to accelerate the sw render */
836 touch 0002-adapt-CMakeLists-file-to-compile-and-link-fbdev.patch
838 Content of ``0002-adapt-CMakeLists-file-to-compile-and-link-fbdev.patch``
845 Subject: [PATCH] adapt CMakeLists file to compile and link only for fbdev
891 You should now be able to see the recipe listing the existing recipes
897 Now add the recipe to the project. Modify ``build/conf/local.conf`` file adding
910 Run this command to ensure the binary was generated and was installed in the