How to link third-party static library

[nicolaas]

I have searched Hi and Low and cannot find a example of how to link a third-party static library in a legato application , the reason I am in this scenario is because the only library I do have and can compile is a static library. Any Help or advice would be appreciated .

[jyijyi]

Did you try adding the following in .cdef file:

---

bundles:
{
file:
{
[rx] /home/owner/Downloads/libmodule.so /lib/
}
}
requires: {
lib: {
/home/owner/Downloads/libmodule.so
}

---

For more information, please see:

How to link an .so to a legato project

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. ldfl…

[nicolaas]

Hi Guys thanks for the reply but it was quite simple linking a third party static library eg. azure iot client.

ldflags:
{
-lssl → shared library
-lcrypto → shared library
-L $CURDIR/third-party/lib → PATH of static third party libs
-liothub_client → static
-liothub_client_mqtt_transport → static
-liothub_client_mqtt_ws_transport – static
-laziotsharedutil – static
-lserializer – static
-lumqtt – static
}