I'm using Nucleo-F756ZG board from STM vendor. I'm using VS Code with PlatformIO extension. Here, I can provide various compiler/assembler/linker options which are considered during build and link process. I'm not sure how I should implement these flags because, as far as I know, its only instructed how to do this on Arduino platform. This are the instructions I'm referring to:
# Algorithm inclusion
* The static library path needs to be included in the platform.txt file.
* In the platforms.txt search ‘recipe.c.combine.pattern’ and adding where your library is located after ‘{object_files}’, just like this:
recipe.c.combine.pattern="{compiler.path}{compiler.c.elf.cmd}" "-Wl,--Map={build.path}/{build.project_name}.map" "-L{compiler.sdk.path}/lib" "-L{compiler.sdk.path}/ld" "-L{compiler.sdk.path}/{build.memory_type}" {compiler.c.elf.flags} {compiler.c.elf.extra_flags} {build.extra_flags} -Wl,--start-group {object_files} "C:\Users\Name\Documents\Projects\Bsec_Library\libalgobsec.a" "{archive_file_path}" {build.extra_libs} {compiler.c.elf.libs} {compiler.libraries.ldflags} -Wl,--end-group -Wl,-EL -o "{build.path}/{build.project_name}.elf"
* Configurations can be copied to files Selectivity_Config.c & Selectivity_Config.h which is included by default
* Note to not change the variable name as they are already linked in the repositrory.
I'm able to link against "libalgobsec.a" static library however I get more errors, which refer to inidividual output files within this library. So, translating these options to my platform might solve this issues I'm facing.
