You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pico examples project (picow_blink) configured with -DCMAKE_PREFIX_PATH=path_to_arm_none_eabi_toolchain command line option fails to configure. Before the C compiler test step, it loses the content of the CMAKE_PREFIX_PATH. -- Detecting C compiler ABI info CMake Error at C:/Projects/pico/pico-sdk/cmake/preload/toolchains/find_compiler.cmake:28 (message): Compiler 'arm-none-eabi-gcc' not found, you can specify search path with "PICO_TOOLCHAIN_PATH". configure_issue.txt
The text was updated successfully, but these errors were encountered:
The problem is that try try_compile creates a CMakeFiles.txt that includes the preload/toolchains/pico_arm_gcc.cmake. I'm not sure how this mechanism should work, but seems like bad practice to depend on a specific ways to pass the variable. If something, I suggest using the variable above to pass the previously found compiler paths directly, instead of trying to find it again - since there may be other factors causing a different compiler is found in the toplevel cmake, and a different one is found in the generated try-compile cmake.
Pico examples project (picow_blink) configured with -DCMAKE_PREFIX_PATH=path_to_arm_none_eabi_toolchain command line option fails to configure. Before the C compiler test step, it loses the content of the CMAKE_PREFIX_PATH.
-- Detecting C compiler ABI info CMake Error at C:/Projects/pico/pico-sdk/cmake/preload/toolchains/find_compiler.cmake:28 (message): Compiler 'arm-none-eabi-gcc' not found, you can specify search path with "PICO_TOOLCHAIN_PATH".
configure_issue.txt
The text was updated successfully, but these errors were encountered: