asaki can you give me any hints and links?
thank you

    You can search in google.

    asaki instead of Make - can you provide a setup for CMake?
    It is widely supported under Windows and Linux and also Make projects are being slowly abandoned
    Thanks

      make does not support in cmake win11 due to cmake issue ,you can use ninja instead.

      Which setup for cmake? I do not know what do you mean.

        pull code then you can use make.

          asaki

          make does not support in cmake win11 due to cmake issue ,you can use ninja instead.

          Which setup for cmake? I do not know what do you mean.

          For example I am able to compile SDK and examples for Kendryte K210 RiscV with CMake only on Windows 11
          No errors

          asaki
          Works better but still errors

          `PS C:\IoT\Bouffalo\bl_mcu_sdk\examples\helloworld> make ninja CHIP=bl808 CPU_ID=d0 BOARD=bl808dk
          ./../../tools/cmake/bin/cmake.exe -S . -B build -G Ninja -DCROSS_COMPILE=riscv64-unknown-elf- -DCHIP=bl808 -DCPU_ID=d0 -DBOARD=bl808dk -DBOARD_DIR= -DCONFIG_DEBUG=y -DCONFIG_ROMAPI=y -DCONFIG_USB_HS=y -DCONFIG_COMX=COM5 -DCMAKE_EXPORT_COMPILE_COMMANDS=OFF -DCONFIG_TLSF=y
          -- The C compiler identification is unknown
          -- The CXX compiler identification is unknown
          -- The ASM compiler identification is unknown
          -- Found assembler: riscv64-unknown-elf-gcc.exe
          CMake Error at C:/IoT/Bouffalo/bl_mcu_sdk/cmake/bouffalo_sdk-config.cmake:21 (enable_language):
          The CMAKE_C_COMPILER:

          riscv64-unknown-elf-gcc.exe

          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.
          Call Stack (most recent call first):
          CMakeLists.txt:5 (find_package)

          CMake Error at C:/IoT/Bouffalo/bl_mcu_sdk/cmake/bouffalo_sdk-config.cmake:21 (enable_language):
          The CMAKE_CXX_COMPILER:

          riscv64-unknown-elf-g++.exe

          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.
          Call Stack (most recent call first):
          CMakeLists.txt:5 (find_package)

          CMake Error at C:/IoT/Bouffalo/bl_mcu_sdk/cmake/bouffalo_sdk-config.cmake:21 (enable_language):
          The CMAKE_ASM_COMPILER:

          riscv64-unknown-elf-gcc.exe

          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 "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
          to the compiler, or to the compiler name if it is in the PATH.
          Call Stack (most recent call first):
          CMakeLists.txt:5 (find_package)

          -- Warning: Did not find file Compiler/-ASM
          -- Configuring incomplete, errors occurred!
          See also "C:/IoT/Bouffalo/bl_mcu_sdk/examples/helloworld/build/CMakeFiles/CMakeOutput.log".
          See also "C:/IoT/Bouffalo/bl_mcu_sdk/examples/helloworld/build/CMakeFiles/CMakeError.log".
          make: *** [../../project.build:47: ninja] Error 1`

            Don't you read the doc? This is a simple issue.

              Just add toolchain into system path, please read the doc, thanks.

              asaki this seems to be issue with Windows 10 - PATH was added
              same setup works on Windows 11 and I was able to compile the project with exactly same paths and toolchain
              Well I will have to use Windows 11 I guess

              Thanks for help

                12 days later

                I don't work with windows, but this seems unlikely to be Windows 10 vs. 11; it's a system setup thing. The error seems self-explanatory:

                riscv64-unknown-elf-gcc.exe is not a full path and was not found in the PATH.

                If you can type that at a shell prompt and it says "not found", then it's not included in your PATH. This is how UNIX and DOS systems have worked for decades. It's really fundamental.

                  Write a Reply...
                  @ 2025 Bouffalo Lab (Nanjing) Co., Ltd. All rights reserved.