s/This are/These are/

On 8/1/21, Alan Carvalho de Assis <acas...@gmail.com> wrote:
> Hi Everyone,
>
> I'm trying to build NuttX using CMake build system, but the
> apps/CMakeLists.txt is not finding the cmake scripts that are at
> nuttx/cmake/ directory.
>
> I appreciate if someone with experience on CMake give a hand.
>
> This are the step I'm following:
>
> $ git clone https://github.com/protobits/incubator-nuttx nuttx
>
> $ git clone https://github.com/protobits/incubator-nuttx-apps apps
>
> $ cd apps/
> $ git checkout -b cmake origin/cmake
>
> $ cd ../nuttx
> $ git checkout -b cmake origin/cmake
>
> $ mkdir build
>
> $ export NUTTX_APPS_DIR=/home/alan/nuttxspace/cmake/apps
>
> $ cmake -DNUTTX_BOARD="arm/stm32/stm32f4discovery" -DNUTTX_CONFIG="nsh"
> -- Initializing NuttX
> --   Board: arm/stm32/stm32f4discovery
> --   Config: nsh
> --   Appdir: ../apps
> -- Use NuttX math.h: no
> -- The ASM compiler identification is GNU
> -- Found assembler: /usr/bin/arm-none-eabi-gcc
> -- The C compiler identification is GNU 9.2.1
> -- The CXX compiler identification is GNU 9.2.1
> -- Check for working C compiler: /usr/bin/arm-none-eabi-gcc
> -- Check for working C compiler: /usr/bin/arm-none-eabi-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/arm-none-eabi-g++
> -- Check for working CXX compiler: /usr/bin/arm-none-eabi-g++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Detected system: x86_64
> CMake Error at /home/alan/nuttxspace/cmake/apps/CMakeLists.txt:4
> (nuttx_add_library):
>   Unknown CMake command "nuttx_add_library".
>
>
> -- Configuring incomplete, errors occurred!
> See also
> "/home/alan/nuttxspace/cmake/nuttx/build/CMakeFiles/CMakeOutput.log".
> See also
> "/home/alan/nuttxspace/cmake/nuttx/build/CMakeFiles/CMakeError.log".
>
>
> Thank you,
>
> Alan
>

Reply via email to