Build option PICO_TOOLCHAIN_PATH has no effect #258
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk#258
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Was trying to use
PICO_TOOLCHAIN_PATHto point to the location where I have it installed on my setup.(I do NOT have gcc it on my path)
Turns out that this option has no effect because it's always cleared here.
As soon as I comment out this line, I can set the
PICO_TOOLCHAIN_PATHoption andpico_find_compilerhappilly finds the compiler.I can submit a PR with this fix if you want.
how are you setting
PICO_TOOLCHAIN_PATH? was this a fresh build directory?Yes, it's a fresh build directory and I'm using VS Code ".vscode\cmake-variants.json" to set the build options.
what i meant was how is it getting set from a cmake perspective? command line define, environment?
I know it works with
-DPICO_TOOLCHAIN_PATH=on the command line, since i use that all the time!I was using cmake-variants.json to build with CMake with the CMake Tools extension.
@kilograham do you use just
-DPICO_TOOLCHAIN_PATH=or you actually have something in the path ahead of the=?I suspect Graham meant
-DPICO_TOOLCHAIN_PATH=/path/to/toolchainyes, that is what I meant... also what OS are you on?
Windows 10, 64bits
VS Code 1.54.1
CMake tools 1.6.0
Follows the CMake logs, for completeness. On both the
PICO_TOOLCHAIN_PATHis set trough.vscode\cmake-variants.json. Build folder cleaned.With the original code:
With line 3 @ pico_pre_load_toolchain.cmake commented:
Ah, well
-DPICO_TOOLCHAIN_PATH:STRING=...wasn't something i was even aware of, and is the reason for the difference in behavior.Can you check
works for you
Yes, that works.
🤔 I didn't think of adding the
"because, from the comment, I was under the impression that the intent of the line was precisely to clear the variable.I can still submit the PR with your fix, if you want to. Not sure if you prefer to handle this other way...
Just let me know.
sure, thx
merged into 1.1.1
Hello I am having this issue I believe
"CMake Warning at pico-sdk/cmake/preload/toolchains/find_compiler.cmake:22 (message):
PICO_TOOLCHAIN_PATH specified (/c/Program Files
(x86)/ARMgnu/mpac/bin/arm-none-eabi-gcc), but arm-none-eabi-gcc not found
there
"
I have tried a million different ways of setting the path to arm-none-eabi-gcc and it will not find it there. Is there any solution to this?
You're commenting on an issue that was fixed some time ago. You might have more luck raising a new issue if you think you have found a new problem. If you just want support - try the forum https://forums.raspberrypi.com/viewforum.php?f=144