mikcatta how did you init the NFED directory?

Did you do these steps?

cd C:\
mkdir nfed
cd nfed
west init -m https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers --mr main

I did notice that my cmake is slightly older. How did you install it? Through choco?

      yes did the “west init -m…..” command

      Cmake I believe was installed from the installation routines (step 3) :- choco install cmake –installargs ‘ADD_CMAKE_TO_PATH=System’

        mikcatta hmm ok! I’m updating my setup here to see if I can reproduce the error.

            CMakeError.log

            Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: C:/Program Files (x86)/GNU Tools Arm Embedded/9 2019-q4-major/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/program files (x86)/gnu tools arm embedded/9 2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: c:/program files (x86)/gnu tools arm embedded/9 2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x2c): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status


Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: C:/Program Files (x86)/GNU Tools Arm Embedded/9 2019-q4-major/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/program files (x86)/gnu tools arm embedded/9 2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: c:/program files (x86)/gnu tools arm embedded/9 2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x2c): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status

              CMakeOutput.log

              The target system is: Generic - 2.3.0 - arm
The host system is: Windows - 10.0.18363 - AMD64
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: C:/Program Files (x86)/GNU Tools Arm Embedded/9 2019-q4-major/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags: -c 

The output was:
0


Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "CMakeCCompilerId.o"

The C compiler identification is GNU, found in "C:/nfed/nrf9160-feather/samples/blinky/build/CMakeFiles/3.19.1/CompilerIdC/CMakeCCompilerId.o"

Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
Compiler: C:/Program Files (x86)/GNU Tools Arm Embedded/9 2019-q4-major/bin/arm-none-eabi-gcc.exe 
Build flags: 
Id flags: -c 

The output was:
0


Compilation of the CXX compiler identification source "CMakeCXXCompilerId.cpp" produced "CMakeCXXCompilerId.o"

The CXX compiler identification is GNU, found in "C:/nfed/nrf9160-feather/samples/blinky/build/CMakeFiles/3.19.1/CompilerIdCXX/CMakeCXXCompilerId.o"

Checking whether the ASM compiler is GNU using "--version" matched "(GNU assembler)|(GCC)|(Free Software Foundation)":
arm-none-eabi-gcc.exe (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

                @mikcatta can you delete your build folder and try again with west build -b circuitdojo_feather_nrf9160ns

                  @jaredwolff Presumably that is the build directory in the C:\nfed\nrf9160-feather\samples\blinky directory?

                  Deleted that directory and build using west build -b circuitdojo_feather_nrf9160ns and I still get the same error.

                   Assertion failed: The toolchain is unable to build a dummy C file.  See
  CMakeError.log.
Call Stack (most recent call first):
  C:/nfed/zephyr/CMakeLists.txt:42 (assert)

                    mikcatta @jaredwolff Presumably that is the build directory in the C:\nfed\nrf9160-feather\samples\blinky directory?

                    Yes, C:\nfed\nrf9160-feather\samples\blinky\build delete the whole build directory if that’s where you’re running west build -b circuitdojo_feather_nrf9160ns

                    mikcatta hmm so this error happens when the cmake cache is mucked up for some reason. The solution for Mac is this. working on a Windows solution..

                          mikcatta try this:

                          Open up powershell.exe in Adminstrator mode and run:

                          choco uninstall cmake
choco install -y cmake --version 3.18.5

                          Then delete your build directory and try again.

                              Hi @jaredwolff

                              Tried that, and cmake didn’t seem to be added to the PATH, so had to add it manually and now it reports as:

                              C:\nfed\nrf9160-feather\samples\blinky>cmake -version
                              cmake version 3.18.5

                              But I still get the same error as before:-

                              CMake Error at C:/nfed/zephyr/cmake/extensions.cmake:1457 (message):
  Assertion failed: The toolchain is unable to build a dummy C file.  See
  CMakeError.log.
Call Stack (most recent call first):
  C:/nfed/zephyr/CMakeLists.txt:42 (assert)


-- Configuring incomplete, errors occurred!
See also "C:/nfed/nrf9160-feather/samples/blinky/build/CMakeFiles/CMakeOutput.log".
See also "C:/nfed/nrf9160-feather/samples/blinky/build/CMakeFiles/CMakeError.log".
FATAL ERROR: command exited with status 1: 'c:\program files\cmake\bin\cmake.EXE' '-BC:\nfed\nrf9160-feather\samples\blinky\build' '-SC:\nfed\nrf9160-feather\samples\blinky' -GNinja -DBOARD=circuitdojo_feather_nrf9160ns

                                mikcatta where are you running these commands? powershell.exe? You don’t have any other cmake installations before using choco correct?

                                    I will add, what are you using to do your edits? I’m starting to see that my setup is not working in standalone powershell.exe but in the shell provided by VSCode. (as that’s how I did my testing)

                                      @jaredwolff

                                      I am running the commands from the Windows cmd prompt, is that OK?

                                      I’ve done a search for cmake.exe and found the following:-

                                      `C:>dir /s cmake.exe
                                      Volume in drive C is OS
                                      Volume Serial Number is 52E2-0FD2

                                      Directory of C:\Program Files\CMake\bin

                                      18/11/2020 07:21 8,964,752 cmake.exe
                                      1 File(s) 8,964,752 bytes

                                      Directory of C:\Users\mike_\ncs\v1.3.2\toolchain\opt\bin

                                      14/11/2020 17:21 7,792,128 cmake.exe
                                      1 File(s) 7,792,128 bytes

                                      Directory of C:\Users\mike_\ncs\v1.4.0\toolchain\opt\bin

                                      15/11/2020 11:57 7,792,128 cmake.exe`

                                      But they don’t appear in the PATH…

                                      C:\>echo %PATH%
                                      C:\Python39\Scripts\;C:\Python39\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\app\mike_\product\11.2.0\odac;C:\app\mike_\product\11.2.0\odac\bin;C:\app\mike_\product\11.2.0\client_64bit_odac\bin;C:\app\mike_\product\11.2.0\client_64bit_odac;C:\Program Files (x86)\Intel\iCLS Client\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\Apache\maven\bin;C:\Program Files\Java\jdk1.8.0_161\bin;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin;C:\instantclient_11_1;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\NTP\bin;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Program Files\Git\cmd;C:\nRFConnectSDK\bin;c:\program files\cmake\bin;C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major\bin;C:\Users\mike_\AppData\Local\Microsoft\WindowsApps;C:\ProgramData\mike_\atom\bin;C:\Users\mike_\AppData\Local\Microsoft\WindowsApps;C:\Users\mike_\AppData\Roaming\npm;C:\Users\mike_\AppData\Local\Programs\Microsoft VS Code\bin

                                        Directory of C:\nfed

15/12/2020  19:48    <DIR>          .
15/12/2020  19:48    <DIR>          ..
15/12/2020  19:36    <DIR>          .west
15/12/2020  19:45    <DIR>          bootloader
15/12/2020  19:47    <DIR>          mbedtls
15/12/2020  19:52    <DIR>          modules
15/12/2020  19:37    <DIR>          nrf
15/12/2020  19:36    <DIR>          nrf9160-feather
15/12/2020  19:46    <DIR>          nrfxlib
15/12/2020  19:46    <DIR>          test
15/12/2020  19:52    <DIR>          tools
15/12/2020  19:59    <DIR>          zephyr

                                          mikcatta hmm looks ok. So you’re still getting the “Cannot compile dummy file” error on both Linux and Windows?

                                          What’s the version of your compiler?

                                              Terms and Conditions | Privacy Policy