Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 5811

SDK • Re: What is the code path to main()?

$
0
0
then spent about half an hour trying to verify whether it had actually used the arm compiler rather than plain old windows gcc
if it used an x86 gcc, it would have failed to even build, because there are chunks of arm asm in the build process

if your windows has an arm gcc, then thats a different story...
The light blinked, but I'm still not convinced it used the compiler I wanted it to use
https://cmake.org/cmake/help/latest/var ... EFILE.html

Code:

[nix-shell:~/apps/rpi/pico/pico-examples/build]$ cmake -DCMAKE_VERBOSE_MAKEFILE=1 ..[nix-shell:~/apps/rpi/pico/pico-examples/build]$ make[  0%] Building C object blink/CMakeFiles/blink.dir/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_clocks/clocks.c.objcd /home/clever/apps/rpi/pico/pico-examples/build/blink && /nix/store/h4mwry6mqgj5z8b4jmlf8r4j1m8ywv1p-arm-none-eabi-stage-final-gcc-debug-wrapper-10.2.0/bin/arm-none-eabi-gcc -DLIB_PICO_BIT_OPS=1 -DLIB_PICO_BIT_OPS_PICO=1 -DLIB_PICO_DIVIDER=1 -DLIB_PICO_DIVIDER_HARDWARE=1 -DLIB_PICO_DOUBLE=1 -DLIB_PICO_DOUBLE_PICO=1 -DLIB_PICO_FLOAT=1 -DLIB_PICO_FLOAT_PICO=1 -DLIB_PICO_INT64_OPS=1 -DLIB_PICO_INT64_OPS_PICO=1 -DLIB_PICO_MALLOC=1 -DLIB_PICO_MEM_OPS=1 -DLIB_PICO_MEM_OPS_PICO=1 -DLIB_PICO_PLATFORM=1 -DLIB_PICO_PRINTF=1 -DLIB_PICO_PRINTF_PICO=1 -DLIB_PICO_RUNTIME=1 -DLIB_PICO_STANDARD_LINK=1 -DLIB_PICO_STDIO=1 -DLIB_PICO_STDIO_UART=1 -DLIB_PICO_STDLIB=1 -DLIB_PICO_SYNC=1 -DLIB_PICO_SYNC_CRITICAL_SECTION=1 -DLIB_PICO_SYNC_MUTEX=1 -DLIB_PICO_SYNC_SEM=1 -DLIB_PICO_TIME=1 -DLIB_PICO_UTIL=1 -DPICO_BOARD=\"pico\" -DPICO_BUILD=1 -DPICO_CMAKE_BUILD_TYPE=\"Release\" -DPICO_COPY_TO_RAM=0 -DPICO_CXX_ENABLE_EXCEPTIONS=0 -DPICO_EXTRAS=1 -DPICO_NO_FLASH=0 -DPICO_NO_HARDWARE=0 -DPICO_ON_DEVICE=1 -DPICO_PROGRAM_URL=\"https://github.com/raspberrypi/pico-examples/tree/HEAD/blink\" -DPICO_TARGET_NAME=\"blink\" -DPICO_USE_BLOCKED_RAM=0 -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_stdlib/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_gpio/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_base/include -I/home/clever/apps/rpi/pico/pico-examples/build/generated/pico_base -I/home/clever/apps/rpi/pico/pico-sdk-master/src/boards/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_platform/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2040/hardware_regs/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_base/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2040/hardware_structs/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_claim/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_sync/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_irq/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_sync/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_time/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_timer/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_util/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_uart/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_resets/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_clocks/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_pll/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_vreg/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_watchdog/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_xosc/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_divider/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_runtime/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_printf/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_bit_ops/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_divider/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_double/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_float/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_malloc/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_bootrom/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/common/pico_binary_info/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_stdio/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_stdio_uart/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_int64_ops/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/pico_mem_ops/include -I/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/boot_stage2/include -mcpu=cortex-m0plus -mthumb -O3 -DNDEBUG -ffunction-sections -fdata-sections -std=gnu11 -o CMakeFiles/blink.dir/home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_clocks/clocks.c.obj -c /home/clever/apps/rpi/pico/pico-sdk-master/src/rp2_common/hardware_clocks/clocks.c
all of the details you wanted to see, with a single flag!

Statistics: Posted by cleverca22 — Fri May 03, 2024 3:45 pm



Viewing all articles
Browse latest Browse all 5811

Trending Articles