patacongo commented on PR #1819: URL: https://github.com/apache/nuttx-apps/pull/1819#issuecomment-1616672992
> If I had created that example, I would put both static and dynamic libraries under one example application and named it `libexample` to have all-in-one place.. but granularity of examples here may have its advantages too :-) I think there is a misconception here. The static libraries (archives) and shared libraries are very different: Archives are only used by the build system on the host. They are just containers for compiled .o files and are really only usable by the linker which draws out the .o files and links them into the binary image. So unless you have a linker in your target the static library is useless on the target. The shared libraries, on the the other hand, are created at build time but are ONLY used at run-time in the target when the target application calls dlopen() and gets the function addresses from the shared library. So these shared libraries are not useful on the host; they are used only in the target. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
