Linking with nano specs: libg_nano vs libc_nano

Asked by Marjon on 2018-06-27

I am trying to duplicate a build using CMake, and I believe I have passed the CMake file all the correct flags. The problem shows when I compare the built map file vs the current project's map file. The current project links some functions using libc_nano, but my CMake build uses the libg_nano implementation. How can I force CMake to use libc_nano instead of libg_nano?

[CLOSING]: Additional info, I have edited the CMake file to set the CMAKE_LINKER to point to g++ and defined CMAKE_C_LINK_EXECUTABLE to contains the expected values. Map file now shows no libg_nano included.

Question information

Language:
English Edit question
Status:
Solved
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Solved by:
Marjon
Solved:
2018-06-28
Last query:
2018-06-28
Last reply:
Marjon (marjonz) said : #1

Updated the question with the solution I found.