Searched +full:common +full:- +full:build +full:- +full:and +full:- +full:test (Results 1 – 25 of 564) sorted by relevance
12345678910>>...23
... .vim meson-1.0.0/data/test.schema.json meson-1.0.0/
1 #!/bin/bash -e9 echo -e "dummy \tbuild dummy"10 echo -e "A \tbuild dummy A"11 echo -e "B \tbuild dummy B"12 echo -e "C \tbuild dummy C"14 # Test:15 # ./build.sh shell16 # ./device/rockchip/common/build-hooks/example.sh -h18 # Usage: ./device/rockchip/common/build-hooks/example.sh [OPTIONS]19 # dummy build dummy[all …]
1 # IMAGE_TAG is the tag of the docker image used for the build jobs. If the2 # image doesn't exist yet, the docker-image stage generates it.8 # gcc/clang or other packages, which might break the build with older commits16 IMAGE_TAG: "debian-testing-20190219"21 - docker-image22 - build-and-test24 debian-testing:25 stage: docker-image27 name: gcr.io/kaniko-project/executor:debug30 …- echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGIST…[all …]
1 mpp (1.5.0-1) stable; urgency=critical6 -- Caesar Wang <wxt@rock-chips.com> Thu, 20 May 2021 09:40:00 +08008 mpp (1.4.0-1) stable; urgency=critical28 * [test]: Fix rc2 test rc_mode error39 * [osal]: linux: add -ldl -lct to link relative library42 * [oasl]: Add lock timing test43 * [base]: Add mpp/base/test for task en/dequeue demo47 * [jpegd]: fix the compiler warnings and hide some symbols71 * Revert "[osal]: linux: add -ldl -lct to link relative library"77 * [mpp_dec]: remove obsoleted code and format comments[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK4 The Yocto Project Test Environment Manual10 Welcome to the Yocto Project Test Environment Manual! This manual is a12 environment used by the Yocto Project to make sure each major and minor13 release works as intended. All the project's testing infrastructure and14 processes are publicly visible and available so that the community can15 see what testing is being performed, how it's being done and the current16 status of the tests and the project at any given time. It is intended17 that Other organizations can leverage off the process and testing19 production test environment, building upon the foundations from the[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK4 Yocto Project Releases and the Stable Release Process7 The Yocto Project release process is predictable and consists of both8 major and minor (point) releases. This brief chapter provides9 information on how releases are named, their life cycle, and their12 Major and Minor Release Cadence16 month cadence roughly timed each April and October of the year.18 also shown. See the ":ref:`ref-manual/release-process:major release codenames`"21 - 2.2 (Morty) 22 - 2.1 (Krogoth)[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK7 Following is a list of terms and definitions users new to the Yocto Project14 Files that append build information to a recipe file. Append files are15 known as BitBake append files and ``.bbappend`` files. The OpenEmbedded16 build system expects every append file to have a corresponding recipe17 (``.bb``) file. Furthermore, the append file and corresponding recipe file19 file type suffix used (e.g. ``formfactor_0.0.bb`` and23 similarly-named recipe file. For an example of an append file in use, see24 the ":ref:`dev-manual/common-tasks:appending other layers metadata with your layer`"37 .. code-block:: shell[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK4 QA Error and Warning Messages7 .. _qa-introduction:12 When building a recipe, the OpenEmbedded build system performs various13 QA checks on the output to ensure that common issues are detected and14 reported. Sometimes when you create a new recipe to build new software,15 it will build with no problems. When this is not the case, or when you20 checks, it is best to try and resolve any reported QA issues. This21 chapter provides a list of the QA messages and brief explanations of the24 The next section provides a list of all QA error and warning messages[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK7 Class files are used to abstract common functionality and share it16 ``.bbclass`` and are usually placed in a ``classes/`` directory beneath19 :term:`BUILDDIR` (e.g. ``build/``) in the same way as24 This chapter discusses only the most useful and important classes. Other29 .. _ref-classes-allarch:35 architecture-specific output. The class disables functionality that is37 building the cross-compiler and a C library as pre-requisites, and44 :term:`RDEPENDS` and47 even if the recipes do not produce architecture-specific output.[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK4 Common Tasks9 work to new hardware (adding a new machine), and so forth. You will find13 Understanding and Creating Layers16 The OpenEmbedded build system supports organizing21 ":ref:`overview-manual/yp-intro:the yocto project layer model`"22 section in the Yocto Project Overview and Concepts Manual.25 -----------------------30 build system, as the Yocto Project ships with tools that speed up creating33 layer-creation tools, see the[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK11 developers create custom Linux-based systems that are designed for13 Yocto Project provides a flexible toolset and a development environment15 through shared technologies, software stacks, configurations, and best19 provides advantages in both systems and applications development,20 archival and management benefits, and customizations used for speed,21 footprint, and memory utilization. The project is a standard when it23 software customizations and build interchange for multiple hardware24 platforms as well as software stacks that can be maintained and scaled.26 .. image:: figures/key-dev-elements.png[all …]
1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK4 Common Tasks7 This chapter presents several common tasks you perform when you work11 kernel, iterative development, working with your own sources, and12 incorporating out-of-tree modules.17 2.4 Release and forward.19 Preparing the Build Host to Work on the Kernel22 Before you can do any kernel development, you need to be sure your build24 set up, see the ":doc:`/dev-manual/start`" section in28 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"[all …]
1 // -*- mode:doc; -*-4 === Tips and tricks6 [[package-name-variable-relation]]7 ==== Package name, config entry name and makefile variable relationship11 * the _package name_, which is the package directory name (and the21 * the package directory and the +*.mk+ name are the _package name_22 itself (e.g.: +package/foo-bar_boo/foo-bar_boo.mk+);25 +foo-bar_boo+);27 * the config entry is the upper case _package name_ with `.` and `-`32 with `.` and `-` characters substituted with `_` (e.g.:[all …]
1 // -*- mode:doc; -*-7 and fixing bugs, analyzing and fixing package build failures detected by8 the autobuilders, testing and reviewing patches sent by other9 developers, working on the items in our TODO list and sending your own15 the main way of interacting with other Buildroot developers and to send17 xref:community-resources[] for the subscription link.21 source code tarball. Git is the easiest way to develop from and directly22 send your patches to the mailing list. Refer to xref:getting-buildroot[]25 === Reproducing, analyzing and fixing bugs30 help in reproducing, analyzing and fixing reported bugs is more than[all …]
8 and booting a kernel.15 On some systems, hot-plug tests could hang forever waiting for cpu and16 memory to be ready to be offlined. A special hot-plug target is created17 to run the full range of hot-plug tests. In default mode, hot-plug tests run18 in safe mode with a limited scope. In limited mode, cpu-hotplug test is19 run on a single cpu as opposed to all hotplug capable cpus, and memory20 hotplug test is run on 2% of hotplug capable memory instead of 10%.23 userspace may wish to use the `Test Harness`_. Tests that need to be24 run in kernel space may wish to use a `Test Module`_.29 To build the tests::[all …]
1 # This mimics the top-level Makefile. We do it explicitly here so that this17 # The following are built by lib.mk common compile rules.19 # custom build rule and prevent common build rule use.20 # TEST_PROGS are for test shell scripts.21 # TEST_CUSTOM_PROGS and TEST_PROGS will be run by common run_tests22 # and install targets. Common clean doesn't touch them.36 # Invoke headers install with --no-builtin-rules to avoid circular38 # make inherits builtin-rules which will use the rule generate39 # Makefile.o and runs into40 # "Circular Makefile.o <- prepare dependency dropped."[all …]
3 # SPDX-License-Identifier: GPL-2.0+8 Quick-start11 If you just want to quickly set up buildman so you can build something (for14 cd /path/to/u-boot16 buildman --fetch-arch arm17 buildman -k rpi_219 # u-boot.bin is the output image25 This tool handles building U-Boot to check that you have not broken it26 with your patch series. It can build each individual commit and report27 which boards fail on which commits, and which errors come up. It aims[all …]
2 # are most common to tests that are likely to be shared.9 # and a 32 bit version. The MACHINE is the DNS name to get to the15 # By default, BOX and MACHINE are the same.30 # THIS_DIR is used through out the configs and defaults to ${PWD} which40 # Reset the log before running each test.53 # and run a script called 'run-test' located on that box.54 TEST = ${SSH} run-test56 # Point build dir to the git repo you use59 # Each machine will have its own output build directory.60 OUTPUT_DIR = ${THIS_DIR}/build/${MACHINE}[all …]
2 Stressful Application Test (or stressapptest, its unix name) is a memory interface test.3 …and I/O, with the intent of creating a realistic high load situation in order to test the existing…7 Discussion group: https://groups.google.com/d/forum/stressapptest-discuss14 ./stressapptest -s 20 -M 256 -m 8 -W # Test 256MB, running 8 "warm copy" threads. Exit after 20 …15 ./stressapptest --help # list the available arguments.17 Common arguments18 * -M mbytes : megabytes of ram to test (auto-detect all memory available)19 * -s seconds : number of seconds to run (20)20 * -m threads : number of memory copy threads to run (auto-detect to number of CPUs)21 * -W : Use more CPU-stressful memory copy (false)[all …]
4 Subject: [PATCH] Add devd config backend for FreeBSD (and GNU/kFreeBSD)7 by Koop Mast and myself.9 Signed-off-by: Robert Millan <rmh@freebsd.org>11 v2 - Emilio Pozuelo Monfort <pochu@debian.org>13 - Ported to NotifyFd API.14 ---16 config/config-backends.h | 5 +20 hw/xfree86/common/xf86Config.c | 7 +-21 hw/xfree86/common/xf86Globals.c | 3 +-22 include/dix-config.h.in | 3 +[all …]
1 .. SPDX-License-Identifier: CC-BY-2.54 Syntax and Operators11 describes the available syntax and operators as well as provides20 ----------------------53 ----------------------------58 - Customize a recipe that uses the variable.60 - Change a variable's default value used in a ``*.bbclass`` file.62 - Change the variable in a ``*.bbappend`` file to override the variable65 - Change the variable in a configuration file so that the value69 originally assigned and also on the desired intent of the change. In[all …]
3 ---9 ---17 - Update Debian10 to Debian1118 - Update Yocto3.4 to Yocto4.019 - Update Buildroot 2018 to Buildroot202120 - Update Kernel4.19 with rockchip inside22 2 SDK optimization and adjustment24 - Reconstruct SDK configuration compilation mechanism25 - Adjusting the compilation mechanism of the wifibt module26 - Import a new version of Camera rkaiq to optimize its functionality and performance[all …]
1 fix build with gcc 103 gcc 10 is now defaulting to -fno-common resulting in the following build6 …-buildroot-test/scripts/instance-0/output-1/host/bin/arm-buildroot-linux-gnueabihf-gcc -D_LARGEFI…7 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…8 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…9 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…10 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…11 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…12 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…13 …-buildroot-test/scripts/instance-0/output-1/host/lib/gcc/arm-buildroot-linux-gnueabihf/10.2.0/../.…[all …]
1 # this file holds documentation for known keys, possible values and2 # their meanings. Please update, correct and extend this documentation.3 # Mail your changes to openembedded-devel@openembedded.org8 do_build[doc] = "Default task for a recipe - depends on all other normal tasks required to 'build' …9 do_bundle_initramfs[doc] = "Combines an initial ramdisk image and kernel together to form a single …12 do_cleanall[doc] = "Removes all output files, shared state cache, and downloaded source files for a…13 do_cleansstate[doc] = "Removes all output files and shared state cache for a target"16 do_compile_ptest_base[doc] = "Compiles the runtime test suite included in the software being built"17 do_configure[doc] = "Configures the source by enabling and disabling any build-time and configurati…18 do_configure_ptest_base[doc] = "Configures the runtime test suite included in the software being bu…[all …]