| /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
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.
72 [Bazelisk](https://bazel.build/install/bazelisk).
[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/cmake/ |
| 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.")
|
| 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.")
127 …LATFORM_FILE, Custom CMake file to use to set up the platform environment, type=string, group=build
|
| /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/ |
| D | .gitignore | 6 build
7 build-*
|
| D | .bazelignore | 1 # Don't accidentally pick up external CMake deps with Bazel build files.
2 build
|
| D | CMakeLists.txt | 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")
|
| 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 | .bazelrc | 5 # Produce useful output when the build fails.
|
| /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/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…
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/rp2_common/pico_crt0/rp2040/ |
| D | BUILD.bazel | 32 # PICO_BUILD_DEFINE: PICO_USE_BLOCKED_RAM, whether this is a 'blocked_ram' build, type=bool, defaul…
45 # PICO_BUILD_DEFINE: PICO_COPY_TO_RAM, whether this is a 'copy_to_ram' build, type=bool, default=0,…
58 # PICO_BUILD_DEFINE: PICO_NO_FLASH, whether this is a 'no_flash' build, type=bool, default=0, but d…
|
| /hal_rpi_pico-latest/src/rp2040/boot_stage2/ |
| D | CMakeLists.txt | 1 … is useful when explicitly setting the default build from a per board CMake file, type=string, gro…
2 …mon/boot_stage2/{PICO_DEFAULT_BOOT_STAGE2}.S, type=string, default=compile_time_choice, group=build
100 # Create a new boot stage 2 target using the default implementation for the current build (PICO_BOA…
|
| /hal_rpi_pico-latest/src/rp2350/boot_stage2/ |
| D | CMakeLists.txt | 1 … is useful when explicitly setting the default build from a per board CMake file, type=string, gro…
2 …mon/boot_stage2/{PICO_DEFAULT_BOOT_STAGE2}.S, type=string, default=compile_time_choice, group=build
100 # Create a new boot stage 2 target using the default implementation for the current build (PICO_BOA…
|
| /hal_rpi_pico-latest/src/rp2_common/pico_crt0/rp2350/ |
| D | BUILD.bazel | 31 # PICO_BUILD_DEFINE: PICO_COPY_TO_RAM, whether this is a 'copy_to_ram' build, type=bool, default=0,…
44 # PICO_BUILD_DEFINE: PICO_NO_FLASH, whether this is a 'no_flash' build, type=bool, default=0, but d…
|
| /hal_rpi_pico-latest/src/rp2_common/pico_standard_binary_info/ |
| D | BUILD.bazel | 13 …CMAKE_BUILD_TYPE, The type of build (e.g. Debug or Release) to embed in binary info, type=string, …
|
| /hal_rpi_pico-latest/bazel/constraint/ |
| D | BUILD.bazel | 5 # This constraint represents the dimension that guides the Pico SDK build. This
13 # This constraint value is used to guide the host build.
19 # This constraint value is used to guide parts of the build that are specific
26 # This constraint value is used to guide parts of the build that are specific
|
| /hal_rpi_pico-latest/src/rp2_common/cmsis/ |
| D | CMakeLists.txt | 4 …tory to locate CMSIS installation, type=string, default="included stub CORE only impl", group=build
13 …E_CONFIG: PICO_CMSIS_VENDOR, Vendor name for CMSIS, type=string, default="RaspberryPi", group=build
24 …_CMAKE_CONFIG: PICO_CMSIS_DEVICE, Device name for CMSIS, type=string, default="RP2040", group=build
|
| /hal_rpi_pico-latest/src/common/boot_picoboot_headers/ |
| D | BUILD.bazel | 3 # This needs to remain compatible with the host build since it's used by
|
| /hal_rpi_pico-latest/src/rp2_common/pico_standard_link/ |
| D | CMakeLists.txt | 74 …# PICO_BUILD_DEFINE: PICO_NO_FLASH, whether this is a 'no_flash' build, type=bool, default=0, but …
77 …# PICO_BUILD_DEFINE: PICO_USE_BLOCKED_RAM, whether this is a 'blocked_ram' build, type=bool, defau…
80 …# PICO_BUILD_DEFINE: PICO_COPY_TO_RAM, whether this is a 'copy_to_ram' build, type=bool, default=0…
91 …efined to 0; note if boot_stage2 headers not present, then boot_stage2 is omitted from build anyway
101 #target_link_options(pico_standard_link INTERFACE "LINKER:--build-id=none")
|
| /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
|
| /hal_rpi_pico-latest/src/common/pico_binary_info/ |
| D | binary_info.bzl | 7 …INE: PICO_TARGET_NAME, The name of the build target being compiled, type=string, default=target na…
|
| /hal_rpi_pico-latest/tools/ |
| D | Findpicotool.cmake | 30 …"It is recommended to build and install picotool separately, or to set PICOTOOL_FETCH_FROM_GIT_PAT…
67 "-DCMAKE_RULE_MESSAGES=OFF" # quieten the build
|
