How to link an .so to a legato project

10

Hi @karlkuhn

Just made the test.
Sounds like it comes from the “.1.0” extension suffix…
GCC (at least the version embedded in the Legato toolchain) apparently requires simple .so files (without extra extension) when working with -l option.
Could you give a try by renaming the .so.1.0 file to a simple .so?

Another possibility (if you don’t want to rename the file) would be to specify the full file name in an ldflags section, without any option, so than ld takes it directly as an input.

ldflags: {
    ${TARGET_PATH}/libDL4Api-Linux.so.1.0
}
1 Like