Hi,
A "static library" project is just a collection of object-files in a zip-file.
The C Linker is therefore not involved in the build process at all.
Normally the build process for a static library includes only the:
- C Pre-processor to expand all C macros / includes (tool: arm-none-eabi-cpp.exe)
- C Compiler - build each compilation unit (compilation unit = .c-file into .o-file) (tool: arm-none-eabi-gcc.exe)
- Archiver - create a .a-file (.a-file = archive) containing all object-files (tool: arm-none-eabi-ar.exe)
The object-files contains the instructions for each function that is built by the library project.
Careful the .o-file is in binary format you will need to use "objdump" to translate back to assembler...
The purpose is to allow customers to build static libraries to be shared across projects or MCUs...
But - I would not use that project type in the screenshot at all. It is a legacy project. Instead refer to the UM2609 as advised by @KDJEM.1 and use the approach shown in the chapter mentioned. That project type has the ability to set the "mcpu=cortex-m?" flag per build configuration which truly enables sharing code in libraries cross products/projects.
