Hi permal,
I have successfully built your g3 project and I am trying to adjust mine project layout and cmakes according to your, however I get this odd behavior:
Code: Select all
[mchodzikiewicz@raczek:build|feature/bsp]$ cmake -DCMAKE_TOOLCHAIN_FILE=/home/mchodzikiewicz/CLionProjects/beerbob_fw_esp32/openbrewery_bsp_esp32/esp-idf/tools/cmake/toolchain-esp32.cmake ../
-- The C compiler identification is GNU 5.2.0
-- The CXX compiler identification is GNU 5.2.0
-- Check for working C compiler: /usr/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /usr/bin/xtensa-esp32-elf-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/xtensa-esp32-elf-g++
-- Check for working CXX compiler: /usr/bin/xtensa-esp32-elf-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at main/CMakeLists.txt:6 (project):
The CMAKE_C_COMPILER:
xtensa-esp32-elf-gcc
is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.
CMake Error at main/CMakeLists.txt:6 (project):
The CMAKE_CXX_COMPILER:
xtensa-esp32-elf-g++
is not a full path and was not found in the PATH.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
-- Configuring incomplete, errors occurred!
See also "/home/mchodzikiewicz/CLionProjects/beerbob_fw_esp32/build/CMakeFiles/CMakeOutput.log".
See also "/home/mchodzikiewicz/CLionProjects/beerbob_fw_esp32/build/CMakeFiles/CMakeError.log".
Have you encountered this problem?
Here is commit that behaves like that:
https://gitlab.com/OpenBrewery/Firmware ... b9bc5c85c7
Also: it behaves just the same with CLion and without providing external toolchain file, moreover - whole xtensa toolchain IS in my PATH