Searched full:build (Results 1 – 25 of 34) sorted by relevance
12
18 - name: Build26 cmake -S test/unit-test -B test/unit-test/build/27 make -C test/unit-test/build/ all30 cd test/unit-test/build/35 make -C test/unit-test/build/ coverage36 lcov --list --rc lcov_branch_coverage=1 test/unit-test/build/coverage.info40 path: ./test/unit-test/build/coverage.info84 - name: Run doxygen build89 build-checks:93 - name: Build Install Dependencies[all …]
78 - name: Build83 cmake -S test/unit-test -B test/unit-test/build/84 make -C test/unit-test/build/ all88 pushd test/unit-test/build/91 make -C test/unit-test/build/ coverage92 lcov --list --rc lcov_branch_coverage=1 test/unit-test/build/coverage.info
1 # Build Instructions10 * Build checks (Enable all functionalities)12 cmake -S . -B build -DFREERTOS_PLUS_TCP_TEST_CONFIGURATION=ENABLE_ALL13 cmake --build build --target freertos_plus_tcp_build_test16 * Build checks (Disable all functionalities)18 cmake -S . -B build -DFREERTOS_PLUS_TCP_TEST_CONFIGURATION=DISABLE_ALL19 cmake --build build --target freertos_plus_tcp_build_test22 * Build checks (Default configuration)24 cmake -S . -B build -DFREERTOS_PLUS_TCP_TEST_CONFIGURATION=DEFAULT_CONF25 cmake --build build --target freertos_plus_tcp_build_test[all …]
77 # Common build combination test.
20 and CTest. Others use a custom python-based build system. New proofs21 should use CMake. This README describes how to build and run both kinds25 CMake-based build31 `~/src/freertos` and you wish to build the proofs into32 `~/build/freertos`. The following three commands build and run36 cmake -S~/src/freertos -B~/build/freertos -DCOMPILER=cbmc38 cmake --build ~/build/freertos --target all-proofs39 cd ~/build/freertos && ctest -L cbmc43 have the Ninja build tool installed:46 ctest --build-and-test \[all …]
4 Write a ninja build file to generate reports for cbmc proofs.6 Given a list of folders containing cbmc proofs, write a ninja build27 description='Generate ninja build file for cbmc proofs.',29 Given a list of folders containing cbmc proofs, write a ninja build133 build {folder}/{entry}.goto: build_goto136 build {folder}/cbmc.txt: build_cbmc {folder}/{entry}.goto139 build {folder}/coverage.xml: build_coverage {folder}/{entry}.goto142 build {folder}/property.xml: build_property {folder}/{entry}.goto145 build {folder}/html/index.html: build_report {folder}/{entry}.goto {folder}/cbmc.txt {folder}/cover…148 build clean_{folder}: clean_folder[all …]
32 of all tasks needed to build, run, and report on all the proofs, and45 litani run-build;48 The CBMC CI runs this script with no arguments to build and run all52 run-build`; use it when you want to add additional proof jobs, not56 finally run `litani run-build`.152 cmd = ["litani", "run-build"]175 # Build goto-binary182 "--ci-stage", "build",
84 def build(): function115 build()
69 # Build each goto-binary out-of-source (i.e. in a 'gotos' directory70 # underneath each proof directory, to make it safe to build all proofs
44 or CBMC proof. The intention is that the build process will run
5 …ttps://github.com/FreeRTOS/FreeRTOS-Plus-TCP/tree/main/test/Coverity/ConfigFiles) required to build27 ### To build and run coverity:33 2. Create the build files using CMake in a `build` directory35 cmake -B build -S test/Coverity37 3. Go to the build directory and copy the coverity configuration file39 cd build/42 4. Build the (pseudo) application44 cov-build --emit-complementary-info --dir cov-out make
17 # Do not allow in-source build.19 …sage( FATAL_ERROR "In-source build is not allowed. Please build in a separate directory, such as $…32 message( STATUS "FreeRTOS-Kernel is required for this build. Submoduling it..." )
16 # Do not allow in-source build.18 …sage( FATAL_ERROR "In-source build is not allowed. Please build in a separate directory, such as $…22 option(FREERTOS_PLUS_TCP_BUILD_TEST "Build the test for FreeRTOS Plus TCP" OFF)143 # If not defined will be default compile with one of the test build combinations AllEnable.145 # Select the appropriate Build Test configuration146 # This is only used when freertos_config is not defined, otherwise the build test will be performed148 set(FREERTOS_PLUS_TCP_TEST_CONFIGURATION "CUSTOM" CACHE STRING "FreeRTOS Plus TCP Build Test config…205 # Suppressions required to build clean with clang.
10 …+ Build separation feature introduced to achieve low memory footprint. Supported build combination…17 …+ Support added in FreeRTOS-plus-TCP git repository CI tool to validate various build configuratio…28 3. Code size details for various build configurations52 …+ Introduced build separation feature to achieve low memory footprint. Supported build combination…
4 …Build separation is added to make the library modular, enabling users to compile and create a low-…
25 …cs.aws.amazon.com/freertos/latest/userguide/getting_started_xilinx.html) to build and run the demo.59 - this particular example supports a native and cross-compiled build option.102 …om/FreeRTOS/FreeRTOS-Kernel)/[Litani-port](https://github.com/awslabs/aws-build-accumulator)) the …
20 # In this example, @doctocat owns any files in the build/logs23 # /build/logs/ @doctocat27 # `docs/build-app/troubleshooting.md`.
16 # Do not allow in-source build.18 …sage( FATAL_ERROR "In-source build is not allowed. Please build in a separate directory, such as $…33 message( STATUS "FreeRTOS-Kernel is required for this build. Submoduling it..." )236 # Include CMock build configuration.246 …clone it manually, or set BUILD_CLONE_SUBMODULES to 'ON' to automatically clone it during build." )254 # Add build targets for CMock and Unit, required for unit testing.260 # Include unit-test build configuration
15 # Macro utility to add library targets for Unity and CMock to build configuration.17 # Build Configuration for CMock and Unity libraries.
42 BUILD_DIR="${UNIT_TEST_DIR}/build/"44 # Create the build directory using CMake:78 Reading tracefile test/unit-test/build/coverage.info
3 # in their Cmake based build system by including this file.
1 add_subdirectory(build-combination)
2 * Windows.h and WinBase.h are include files used to build FreeRTOS (the parts we currently test) on…
37 /* Empty configuration file to check the build with default configuration. */
87 # places the generated source file in the build directory
