/lvgl-latest/docs/details/integration/os/yocto/ |
D | lvgl_recipe.rst | 11 Build Host Packages 13 You must install essential host packages on your build host. The following 18 sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential \ 26 `Required Packages for the Build Host <https://docs.yoctoproject.org/ 27 ref-manual/system-requirements.html#required-packages-for-the-build-host>`_ 39 ├── build/ 65 Build a base image 67 To understand better what is going on, let's build the image like it is 73 source sources/poky/oe-init-build-env 75 Now you should have a folder named ``build`` next to ``sources``. The last [all …]
|
D | terms_and_variables.rst | 23 covers a lot of variables used in the OpenEmbedded build system. 30 The location in the Build Directory where unpacked recipe source code resides. 35 must set S in the recipe so that the OpenEmbedded build system knows where to 39 default Build Directory at poky/build. In this case, the work directory the 40 build system uses to keep the unpacked recipe for db is the following: 44 poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19 63 The destination directory. The location in the Build Directory where components 79 The directory within the Build Directory in which the OpenEmbedded build system 80 places generated objects during a recipe's build process. By default, this 89 The build system defaults to using separate directories for gcc and some kernel [all …]
|
D | core_components.rst | 16 - *Class Data:* Abstracts common build information (e.g. how to build a 33 BitBake is the tool at the heart of the OpenEmbedded Build System and is 48 ``recipename`` is the name of the recipe you want to build (referred 64 before building ``matchbox-desktop``, BitBake would build a cross 88 build system (i.e. ``.ipk`` or ``.deb`` files), this document avoids 112 variables that govern the OpenEmbedded build process. These files fall 116 ``conf/local.conf``, which is found in the `Build Directory <https://docs. 117 yoctoproject.org/ref-manual/terms.html#term-Build-Directory>`_. 125 instructions) that tell the OpenEmbedded build system how to build a
|
/lvgl-latest/.github/workflows/ |
D | ccpp.yml | 16 build: 28 name: Build ${{ matrix.build_option }} 35 run: python tests/main.py --build-option=${{ matrix.build_option }} build 37 build-windows-GCC: 39 name: Build Windows GCC 45 - name: Build 46 run: python tests/main.py build 50 build-windows-MSVC: 52 name: Build Windows MSVC 63 - name: Build [all …]
|
D | build_micropython.yml | 14 build: 16 name: Build ${{ matrix.port }} port 46 - name: Build mpy-cross 54 - name: Build ESP32 port 65 - name: Build STM32 port 68 - name: Build Raspberry Pi PICO port 74 - name: Build Unix port 85 …h=lib/lv_bindings/lvgl/tests/micropy_test/artifacts --mpy-path=ports/unix/build-standard/micropyth…
|
D | compile_docs.yml | 1 name: Build docs 18 build-and-deploy: 21 concurrency: docs-build-and-deploy 64 - name: Build examples (with cache) 66 - name: Build docs 67 run: docs/build.py skip_latex
|
/lvgl-latest/tests/ |
D | main.py | 63 '''Given the build options name, return the build directory name. 70 '''Given the build options name, return the build directory name. 72 Returns absolute path to the build directory.''' 109 '''Build all tests for the specified options name.''' 138 subprocess.check_call(['cmake', '--build', build_dir, 217 There are two types of LVGL tests: "build", and "test". The build-only 219 compiles and links (with various build options). There are also a set of 223 description='Build and/or run LVGL tests.', epilog=epilog) 224 parser.add_argument('--build-options', nargs=1, 226 help='''the build option name to build or run. When [all …]
|
D | README.md | 17 2. Build all build-only tests with `./tests/main.py build`. 18 3. Clean prior test build, build all build-only tests, 20 report `./tests/main.py --clean --report build test`.
|
D | CMakeLists.txt | 4 # Tests do not build for ESP-IDF. # 159 # Ensure 32-bit build 372 message("Disable OpenGL, GLEW or glfw3 for non-amd64 build") 424 # disable test targets for build only tests 433 # build a test libs target 453 # Run ruby to generate source in build directory
|
/lvgl-latest/docs/ |
D | build.py | 61 $ python build.py skip_latex 71 2. $ python build.py skip_latex preserve fixed_tmp_dir 81 $ python build.py skip_latex docs_dev update 104 - Change the modification date and `sphinx-build` will re-build it. 107 - Change the path or filename and `sphinx-build` will re-build it. 109 - whether the -E option is on the `sphinx-build` command line 110 - -E forces `sphinx-build` to do a full re-build. 119 Skips generating API pages (this saves about 70% of build time). 123 Excludes -E command-line argument to `sphinx-build`, which, when present, 133 temporary directory. This is important when getting `sphinx-build` [all …]
|
D | CHANGELOG.rst | 56 - **feat(env/qnx): generate lv_conf.h at build time** `6596 <https://github.com/lvgl/lvgl/pull/6596… 118 - **feat(ci): Add CI test for UEFI build** `5964 <https://github.com/lvgl/lvgl/pull/5964>`__ 121 - **feat(CI): Windows MSVC and GCC build** `6015 <https://github.com/lvgl/lvgl/pull/6015>`__ 187 - **fix(nuttx): fix build break** `6732 <https://github.com/lvgl/lvgl/pull/6732>`__ 189 - **fix(draw/neon): fix build break** `6682 <https://github.com/lvgl/lvgl/pull/6682>`__ 260 - **fix(nuttx): fix build warning using nuttx** `6379 <https://github.com/lvgl/lvgl/pull/6379>`__ 269 - **fix(env): fix meson build break** `5745 <https://github.com/lvgl/lvgl/pull/5745>`__ 277 - **fix(docs): Fix failing docs build in master since lottie** `6316 <https://github.com/lvgl/lvgl/… 288 - **fix(vglite): build issues** `6245 <https://github.com/lvgl/lvgl/pull/6245>`__ 314 - **fix(docs): use find_version helper in build script** `6122 <https://github.com/lvgl/lvgl/pull/6… [all …]
|
/lvgl-latest/docs/details/integration/os/buildroot/ |
D | image_generation.rst | 26 echo "desc: rpi4 lvgl custom build" >> external.desc 36 before starting the build. Lets install them using Ubuntu's package manager. 60 There is a build available for RPi4 62 bits: ``raspberrypi4_64_defconfig``. 74 Create a new file ``build.sh`` at the root of the project with this content: 90 chmod +x build.sh 91 ./build.sh 101 an (almost) empty folder named ``output`` is created, as the build process has 119 Build the image 130 build 133 This folder contains the intermediate files and build artifacts for the various [all …]
|
D | lvgl_app.rst | 30 When the package configuration is completed, build the environment to add the 37 find build/ -name "*libdrm*" 68 touch setup-build-env.sh && chmod +x setup-build-env.sh 70 The script ``setup-build-env.sh`` looks like this: 94 Build the application 97 The environment is now set up, and we're ready to build an application using 115 …cmake -B build -S . -DCMAKE_C_COMPILER=${CROSS_COMPILE}gcc -DCMAKE_CXX_COMPILER=${CROSS_COMPILE}g+… 116 make -j $(nproc) -C build 135 the root filesystem of the target image during the build process. It is a way
|
D | quick_setup.rst | 15 Build the image 19 ./build.sh 23 Now build the SDK and install it 37 source ../setup-build-env.sh 38 cmake -B build -S . 39 make -j $(nproc) -C build
|
/lvgl-latest/docs/details/integration/os/ |
D | torizon_os.rst | 47 and automate the tasks needed to cross-compile applications and build Docker images. 56 To build a Torizon container Docker ARM emulation needs to be enabled 66 More information on the build environment for Torizon containers is available `here 67 …dex.com/torizon/application-development/working-with-containers/configure-build-environment-for-to… 70 that will be used to build the image. 110 # BUILD ------------------------------------------------------------------------ 111 FROM torizon/debian-cross-toolchain-${IMAGE_ARCH}:${CROSS_SDK_BASE_TAG} AS build 126 RUN CC=aarch64-linux-gnu-gcc cmake -S ./lv_port_linux -B build 127 RUN make -j 4 -C ${APP_ROOT}/build 138 # Copy the lvglsim executable compiled in the build step to the $APP_ROOT directory [all …]
|
D | zephyr.rst | 49 After you chose a board you can build one of the LVGL demos for it. Here we are using the :code:`na… 54 $ west build -b native_posix samples/modules/lvgl/demos 60 $ west build -t run 68 If you want to build any of the other demo applications check out the samples 106 - `button input <https://docs.zephyrproject.org/latest/build/dts/api/bindings/input/zephyr,lvgl-but… 107 - `pointer input <https://docs.zephyrproject.org/latest/build/dts/api/bindings/input/zephyr,lvgl-po… 108 - `encoder input <https://docs.zephyrproject.org/latest/build/dts/api/bindings/input/zephyr,lvgl-en… 109 - `keypad input <https://docs.zephyrproject.org/latest/build/dts/api/bindings/input/zephyr,lvgl-key… 157 Overlays can be used to enable/disable features for specific boards or build
|
D | qnx.rst | 32 LVGL is used on other systems. The second is to build LVGL as either a shared or 59 Build LVGL as a Library 63 you choose to build a library then you do not need to follow the instructions in 68 architectures. To build all libraries, simply invoke `make` in this directory: 75 If you prefer to build for a specific architecture and variant, go to the 76 appropriate directory and run `make` there. For example, to build a shared 138 Build the Application 143 different build systems. The following is a simple make file for the example
|
/lvgl-latest/src/libs/freetype/ |
D | ftoption.h | 30 * standard build of the FreeType library. There are three ways to use 31 * this file to build project-specific versions of the library: 34 * cases where you would like to build several versions of the library 37 * - You can put a copy of this file in your build directory, more 38 * precisely in `$BUILD/freetype/config/ftoption.h`, where `$BUILD` is 42 * The default FreeType Makefiles use the build directory 46 * - Copy the file <ft2build.h> to `$BUILD/ft2build.h` and modify it 48 * this file during the build. For example, 55 * will use `$BUILD/myftoptions.h` instead of this file for macro 112 * technology similar to ClearType in this build of the library. This [all …]
|
/lvgl-latest/docs/details/integration/building/ |
D | cmake.rst | 11 This project uses CMakePresets to ensure an easy build. 24 How to build this project using cmake 27 The recommended way to build this project is to use the provided CMakePresets.json. This file conta… 29 - a windows (msvc) build using Visual Studio 30 - a linux (gcc) build using Ninja 36 Build with IDE 49 Build with CMake GUI 53 CMake will create solution files (for VS) or Ninja Files (for Linux Ninja Build) 71 Build with Command line 74 You can also build your project using the command line. Run the following commands [all …]
|
/lvgl-latest/docs/details/integration/bindings/ |
D | javascript.rst | 47 The following are developer notes on how to build lvgljs on your native platform. They are not comp… 54 - `ubuntu build Notes for sdl simulator <https://github.com/lvgl/lv_binding_js/blob/master/doc/buil… 55 - `macos x86 build Notes for sdl simulator <https://github.com/lvgl/lv_binding_js/blob/master/doc/b… 56 - `ubuntu build Notes for platform arm <https://github.com/lvgl/lv_binding_js/blob/master/doc/build… 62 - `JS Bundle build Notes <https://github.com/lvgl/lv_binding_js/blob/master/doc/build/js-bundle.md>…
|
/lvgl-latest/env_support/cmsis-pack/ |
D | gen_pack.sh | 34 # Temporary pack build directory 35 PACK_BUILD=build/ 40 # Do not include the build directory if it is local 162 # Copy files into build base directory: $PACK_BUILD 178 echo "build aborted: Schema check of $PACK_VENDOR.$PACK_NAME.pdsc against PACK.xsd failed" 187 echo "build aborted: pack check failed" 223 echo "build aborted: archiving failed" 230 echo "build of pack succeeded"
|
/lvgl-latest/docs/details/libs/ |
D | rlottie.rst | 16 Build Rlottie 19 To build Samsung's Rlottie C++14 compatible compiler and optionally 22 To build on desktop you can follow the instructions from Rlottie's 32 mkdir build 33 cd build 41 given build system. 182 - Build the lottie animation to be sized for the intended size 186 - Build the lottie animation for the intended frame rate
|
/lvgl-latest/docs/details/integration/chip/ |
D | espressif.rst | 19 Refer to the README.md files in these repositories for build and flash instructions. 47 …atest/reference/versioning.html#range-specifications>`__. During the next build, the LVGL componen… 59 All components from ``${project_dir}/components`` are automatically added to build. 131 - Apply changes to the build system 183 - **Build and flash** 185 After calling ``idf.py build flash`` the picture should be displayed on the screen.
|
D | alif.rst | 128 ninja-build, a GCC ARM compiler, and cmsis-toolbox. 176 Set Up the Build Context, Compile, and Flash 217 HP and HE Cores and Optimized Build 228 There is also an option to choose a "Build Type". For best performance, choose "release". 232 application in general, ensure the HP core is selected and the build type is release.
|
/lvgl-latest/env_support/cmake/ |
D | custom.cmake | 17 # Option to build shared libraries (as opposed to static), default: OFF 18 option(BUILD_SHARED_LIBS "Build shared libraries" OFF) 26 # Build LVGL library 59 # Build LVGL example library 68 # Build LVGL demos library
|