build (full) in projects: hal_rpi_pico-latest

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:build (Results 1 – 25 of 88) sorted by relevance

12 3 4

/hal_rpi_pico-latest/.github/workflows/
D	multi-gcc.yml	11 build: 31 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 36 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 41 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 46 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 51 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 56 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 61 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 66 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/; cd build; cmake ../ -DPICO_SDK_TEST… 71 …run: cd ${{github.workspace}}; mkdir -p build; rm -rf build/*; cd build; cmake ../ -DPICO_SDK_TEST… [all …]
D	cmake.yml	9 # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.) 13 build: 31 - name: Create Build Environment 32 # Some projects don't allow in-source building, so create a separate build directory 34 run: cmake -E make_directory ${{github.workspace}}/build 40 working-directory: ${{github.workspace}}/build 42 # and build directories, but this is only available with CMake 3.13 and higher. 46 - name: Build 47 working-directory: ${{github.workspace}}/build 49 # Execute the build. You can specify a specific target with "--target <NAME>" [all …]
D	macOS.yml	`1 name: Build on macOS 11 build: 28 - name: Build Project 32 mkdir build 33 cd build 35 cmake --build . 37 - name: Build Native 44 cmake --build .`
D	windows.yml	`1 name: Build on Windows 11 build: 26 - name: Build Project 29 mkdir build 30 cd build 32 cmake --build .`
D	bazel_build.yml	`8 bazel-build-check: 25 # Store build cache per workflow. 41 - name: Full Bazel build with develop Picotool 42 run: python3 tools/run_all_bazel_checks.py --program=build --picotool-dir=lib/picotool 45 run: bazel build @picotool//:picotool 58 # Store build cache per workflow.`
/hal_rpi_pico-latest/bazel/
D	README.md	1 # Bazel build 28 ### Ready to build! 33 $ bazelisk build --platforms=@pico-sdk//bazel/platform:rp2040 //... 37 An exhaustive list of build system configuration options is available in 38 `//bazel/config:BUILD.bazel`. 43 $ bazelisk build --platforms=//bazel/platform:rp2040 --@pico-sdk//bazel/config:PICO_BOARD=pico_w //… 53 Creation of UF2 images can be done as explicit build steps on a per-binary 54 rule basis, or through an aspect. Running a wildcard build with the 59 $ bazelisk build --platforms=@pico-sdk//bazel/platform:rp2040 \ 69 launcher) to build the Pico SDK. [all …]
/hal_rpi_pico-latest/src/cmake/
D	on_device.cmake	31 …postprocessing that disassembles RP2350 coprocessor instructions, type=bool, default=0, group=build 55 …ing/hashing and coprocoessor disassembly will all be unavailable, type=bool, default=0, group=build 66 …CMAKE_CONFIG: PICO_NO_TARGET_NAME, Don't define PICO_TARGET_NAME, type=bool, default=0, group=build 67 …NAME, Name of the build target being compiled (unless PICO_NO_TARGET_NAME set in build), type=stri… 84 # PICO_CMAKE_CONFIG: PICO_NO_UF2, Disable UF2 output, type=bool, default=0, group=build 90 …o whether the build is not targeting an RP2040 or RP2350 device, type=bool, default=1 when PICO_PL… 91 …, Whether the build is not targeting an RP2040 or RP2350 device, type=bool, default=1 when PICO_PL… 93 … to whether the build is targeting an RP2040 or RP2350 device, type=bool, default=0 when PICO_PLAT… 94 …CE, Whether the build is targeting an RP2040 or RP2350 device, type=bool, default=0 when PICO_PLAT…
D	rp2_common.cmake	`5 …binaries to not use flash i.e. run from SRAM, type=bool, default=0, group=build, docref=cmake-bina… 7 … copy code from flash to SRAM before running, type=bool, default=0, group=build, docref=cmake-bina… 17 …TAL, Flag to exclude anything except base headers from the build, type=bool, default=0, group=build 29 # RP2040/RP2350 specific From standard build variants`
/hal_rpi_pico-latest/bazel/config/
D	BUILD.bazel	5 # PICO_BAZEL_CONFIG: PICO_TOOLCHAIN, The toolchain to use, type=string, default=gcc, group=build 15 …RD, Board name being built for, type=string, default=pico or pico2, group=build, docref=cmake-plat… 21 …TAL, Flag to exclude anything except base headers from the build, type=bool, default=0, group=build 33 …e 2 file to use; this should point to a filegroup with the .S file to use, type=string, group=build 39 …mon/boot_stage2/{PICO_DEFAULT_BOOT_STAGE2}.S, type=string, default=compile_time_choice, group=build 45 …s to fully override/replace boot_stage2, default=@pico-sdk//src/rp2_common:boot_stage2, group=build 105 …ly supported on the rp2040. dcp is only supported on rp2350, type=string, default=auto, group=build 118 …ted on the rp2040. vfp and dcp are only supported on rp2350, type=string, default=auto, group=build 132 …latform default (hardware on RP2040 and compiler on RP2350), type=string, default=auto, group=build 143 …havior while pico provides a pico-specific implementation, type=string, default=double, group=build [all …]
/hal_rpi_pico-latest/cmake/
D	pico_pre_load_platform.cmake	1 # PICO_BOARD is the root of config as it can define PICO_PLATFORM and other build vars 3 …cified in the user environment, type=string, default=pico or pico2, group=build, docref=cmake-plat… 9 …build for e.g. rp2040/rp2350/rp2350-arm-s/rp2350-riscv/host. This may be specified in the user env… 57 …ok for <PICO_BOARD>.cmake in. This may be specified in the user environment, type=list, group=build 75 …platform to build for if rp2350 is specified for PICO_PLATFORM e.g. rp2350-arm-s/rp2350-riscv, typ… 112 …O_PLATFORM}' which is incompatible. You need to delete the CMake cache or build directory and reco… 113 The best practice is to use separate build directories for different platforms.") 121 You need to delete the CMake cache or build directory and reconfigure to proceed.\ 122 The best practice is to use separate build directories for different platforms.") 124 set(PICO_PLATFORM ${PICO_PLATFORM} CACHE STRING "PICO Build platform (e.g. rp2040, rp2350, rp2350-r… [all …]
D	pico_pre_load_toolchain.cmake	1 …for compiler, type=string, default=none (i.e. search system paths), group=build, docref=cmake-tool… 4 # Set a default build type if none was specified 10 message(STATUS "Defaulting build type to '${default_build_type}' since not specified.") 11 …set(CMAKE_BUILD_TYPE "${default_build_type}" CACHE STRING "Choose the type of build, options are: … 12 # Set the possible values of build type for cmake-gui 18 error("Default build type is NOT supported") 28 # PICO_CMAKE_CONFIG: PICO_COMPILER, Specifies the compiler family to use, type=string, group=build,… 70 … The best practice is to use separate build directories for different platforms or compilers.")
/hal_rpi_pico-latest/
D	MODULE.bazel	16 build_file = "//bazel/toolchain:gcc_arm_none_eabi.BUILD", 24 build_file = "//bazel/toolchain:gcc_arm_none_eabi.BUILD", 32 build_file = "//bazel/toolchain:gcc_arm_none_eabi.BUILD", 40 build_file = "//bazel/toolchain:gcc_arm_none_eabi.BUILD", 48 build_file = "//bazel/toolchain:gcc_arm_none_eabi.BUILD", 56 build_file = "//bazel/toolchain:clang.BUILD", 64 build_file = "//bazel/toolchain:clang.BUILD", 73 build_file = "//bazel/toolchain:clang.BUILD", 81 build_file = "//bazel/toolchain:clang.BUILD", 92 build_file = "//src/rp2_common/tinyusb:tinyusb.BUILD", [all …]
D	README.md	3 The Raspberry Pi Pico SDK (henceforth the SDK) provides the headers, libraries and build system 13 The SDK can be used to build anything from simple applications, fully-fledged runtime environments … 23 hardware, IDE/environment and how to build and debug software for the Raspberry Pi Pico and other R… 35 See [pico-examples](https://github.com/raspberrypi/pico-examples) for example code you can build. 56 …sudo apt install cmake python3 build-essential gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++… 177 1. Setup a CMake build directory. 180 $ mkdir build 181 $ cd build 185 …OARD=pico2 ..` or `cmake -DPICO_BOARD=pico_w ..` to configure the SDK and build options accordingl… 194 1. Make your target from the build directory you created. [all …]
D	CMakeLists.txt	`24 message("Build type is ${CMAKE_BUILD_TYPE}") 27 … message("Using fully de-optimized debug build (set PICO_DEOPTIMIZED_DEBUG=0 to optimize)") 29 … message("Using regular optimized debug build (set PICO_DEOPTIMIZED_DEBUG=1 to de-optimize)") 63 … set(PICO_SDK_TESTS_ENABLED "${PICO_SDK_TESTS_ENABLED}" CACHE INTERNAL "Enable build of SDK tests")`
/hal_rpi_pico-latest/tools/
D	run_all_bazel_checks.py	`34 "build", 42 "step_name": "build", 43 "description": "Bazel build", 49 "description": "Ensure build system configurations options match", 54 "description": "Ensure source files are present in Bazel build", 60 if args.program == "build" or run_all_steps: 74 for build in failed_steps: 75 print_to_stderr(f" * FAILED: {build}")`
D	compare_build_systems.py	35 "/BUILD.bazel", 37 "/*.BUILD", 48 # Sometimes the build systems are supposed to be implemented differently. This 55 # In Bazel, it's a build label rather than a path. 74 # https://bazel.build/extending/platforms 79 # Bazel build uses PICO_CONFIG_EXTRA_HEADER and PICO_CONFIG_PLATFORM_HEADER 98 # These aren't supported as build flags in Bazel. Prefer to 311 _LOG.info("[1/3] Checking build system configuration flags...") 318 # build configurability since it's a big ask to make contributors 323 _LOG.info("[2/4] Checking build system defines...")
D	bazel_build.py	`7 # A script that verifies various Bazel build configurations succeed. 51 # Pretty much only Picotool and pioasm build on Windows. 192 # regressions that cause them to vanish from the wildcard build. 209 "build", 220 for build in failed_builds: 221 print_to_stderr(f" * FAILED: {build} build")`
D	check_source_files_in_bazel_build.py	`7 # Check Bazel build file source coverage. Reports files that: 8 # - Are in the repo but not included in a BUILD.bazel file. 9 # - Are referenced in a BUILD.bazel file but are not present. 138 "Files not included in the Bazel build:\n\n%s\n", 144 "Files referenced in the Bazel build that are missing:\n\n%s\n",`
/hal_rpi_pico-latest/docs/
D	mainpage.md	`3 …are Development Kit), henceforth SDK, provides the headers, libraries and build system necessary t… 7 …evel functionality built using PIO, such as audio. The SDK can be used to build anything from simp… 17 ## The Build System 19 …build. CMake is widely supported by IDEs (Integrated Development Environments), and allows a simpl… 21 Apart from being a widely-used build system for C/C++ development, CMake is fundamental to the way …`
/hal_rpi_pico-latest/src/common/pico_base_headers/
D	BUILD.bazel	`54 …o whether the build is not targeting an RP2040 or RP2350 device, type=bool, default=1 when PICO_PL… 55 …, Whether the build is not targeting an RP2040 or RP2350 device, type=bool, default=1 when PICO_PL… 56 … to whether the build is targeting an RP2040 or RP2350 device, type=bool, default=0 when PICO_PLAT… 57 …CE, Whether the build is targeting an RP2040 or RP2350 device, type=bool, default=0 when PICO_PLAT…`
/hal_rpi_pico-latest/src/rp2040/boot_stage2/include/boot_stage2/
D	config.h	14 // PICO_CONFIG: PICO_BUILD_BOOT_STAGE2_NAME, Name of the boot stage 2 if selected in the build syst… 20 …0 as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 29 …0 as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 38 …l as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 47 …a as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 57 …h as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul…
/hal_rpi_pico-latest/src/rp2350/boot_stage2/include/boot_stage2/
D	config.h	14 // PICO_CONFIG: PICO_BUILD_BOOT_STAGE2_NAME, Name of the boot stage 2 if selected in the build syst… 20 …0 as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 29 …0 as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 38 …l as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 47 …a as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul… 57 …h as the boot stage 2 when no boot stage 2 selection is made by the CMake build, type=bool, defaul…
/hal_rpi_pico-latest/src/rp2_common/pico_standard_binary_info/
D	doc.h	16 …build date (unless `PICO_NO_BI_PROGRAM_BUILD_DATE=1). The value defaults to the C preprocessor val… 17 …* * The program build type (unless `PICO_NO_BI_BUILD_TYPE=1`). The value is `PICO_CMAKE_BUILD_TYPE…
/hal_rpi_pico-latest/.github/workflows/scripts/
D	generate_multi_gcc_workflow.py	`46 build: 70 …output += " run: cd ${{{{github.workspace}}}}; mkdir -p build; rm -rf build/*; cd build; cmak…`
/hal_rpi_pico-latest/bazel/util/
D	transition.bzl	10 A transition in Bazel is a way to force changes to the way the build is 23 that sets --copts=-DFOO=42, we're telling Bazel to build a and all of its 32 from. The common `src` attr tells the transition which build rule to apply 111 # This transition sets SDK configuration options required to build test binaries 133 # This transition sets SDK configuration options required to build test binaries

12 3 4

Zephyr-2.7.6
Zephyr-3.6.0
Zephyr-3.7.1
Zephyr-4.0.0
Zephyr-4.1.0
Zephyr-latest
acpica-latest
babblesim_base-latest
babblesim_ext_2G4_channel_NtNcable-latest
babblesim_ext_2G4_channel_multiatt-latest
babblesim_ext_2G4_device_WLAN_actmod-latest
babblesim_ext_2G4_device_burst_interferer-latest
babblesim_ext_2G4_device_playback-latest
babblesim_ext_2G4_libPhyComv1-latest
babblesim_ext_2G4_modem_BLE_simple-latest
babblesim_ext_2G4_modem_magic-latest
babblesim_ext_2G4_phy_v1-latest
babblesim_ext_libCryptov1-latest
bsim-latest
cmsis-latest
cmsis-dsp-latest
cmsis-nn-latest
cmsis_6-latest
edtt-latest
fatfs-latest
hal_adi-latest
hal_altera-latest
hal_ambiq-latest
hal_atmel-latest
hal_espressif-latest
hal_ethos_u-latest
hal_gigadevice-latest
hal_infineon-latest
hal_intel-latest
hal_microchip-latest
hal_nordic-latest
hal_nuvoton-latest
hal_nxp-latest
hal_openisa-latest
hal_quicklogic-latest
hal_renesas-latest
hal_rpi_pico-latest
hal_silabs-latest
hal_st-latest
hal_stm32-latest
hal_tdk-latest
hal_telink-latest
hal_ti-latest
hal_wch-latest
hal_wurthelektronik-latest
hal_xtensa-latest
hostap-latest
liblc3-latest
libmctp-latest
libmetal-latest
littlefs-latest
loramac-node-latest
lvgl-latest
mbedtls-latest
mcuboot-latest
mipi-sys-t-latest
net-tools-latest
nrf_hw_models-latest
nrf_wifi-latest
open-amp-latest
openthread-latest
percepio-latest
picolibc-latest
segger-latest
tinycrypt-latest
trusted-firmware-a-latest
trusted-firmware-m-latest
uoscore-uedhoc-latest
zcbor-latest