On Fri, Aug 8, 2025 at 12:13 AM Pavel Pisa <ppisa4li...@pikron.com> wrote:
> Hello Alan and others, > > On Thursday 07 of August 2025 16:05:07 Alan C. Assis wrote: > > AFAIK NuttX doesn't have support to export apps side libraries. > > > > Actually it should be nice to have "real" support for libraries on apps/ > > Makefiles (we could use the approach that Google used originally on > Android > > Makefiles) since NuttX supports ELF loading for executable and for > > libraries (that was contributed by Neal Ferguson from WildernessLabs). > > the actual goal/problem solved is not library which is load > separately. The goal is to include next two external libraries > as an option into NuttX APPS build. > > 1) shv-libs4c > https://github.com/silicon-heaven/shv-libs4c > Silicon-heaven protocol support which is used > updater over network and pysimCoder. > The updater is small application which NuttX > version is planned to be submitter into mainline > and reside in > apps/examples/nx-shv-fwupdater/nx_shv_fwupdater.c > But the library is usable on more systems > and should be maintained at single place. > It is planned that it will be configured > and loaded from directory > apps/netutils/libshvc > same as some other libraries. It is build as static > library archive for NuttX > > 2) uLUt library > https://sourceforge.net/p/ulan/ulut > it is set of basic containers and other support > for many of our projects and it is dependency > of shv-libs4c. In actual experimental setup, > it is pulled as submodule of shv-libs4c > but I would prefer to have it as separate > configurable component probably placed in > apps/netutils/libulut > It is not strictly speaking directly NET component > but it is used for one of them and the netutils > location is used and setup to pull external libraries. > > When libshvc is enabled in KConfig then it would be > downloaded according to stores SHA1 has and used > for nx-shv-fwupdater or other similar apps build. > They need to gain access to the libshvc include directory > and library, *.a archive. > > But related includes should be provided even to application/ > firmware images which builds against NuttX export. > Stepan Pressl has already solved all that in his forks > > https://github.com/zdebanos/nuttx-apps > https://github.com/zdebanos/nuttx > > currently in branches nuttx-25-08-07-samocon. > > But we want to make all that as less intrusive as possible > and make it fit well for mainline and are opening discussion > about preferred solutions. > > Best wishes, > > Pavel > > Pavel Pisa > > phone: +420 603531357 > e-mail: p...@cmp.felk.cvut.cz > Department of Control Engineering FEE CVUT > Karlovo namesti 13, 121 35, Prague 2 > university: http://control.fel.cvut.cz/ > personal: http://cmp.felk.cvut.cz/~pisa > company: https://pikron.com/ PiKRON s.r.o. > Kankovskeho 1235, 182 00 Praha 8, Czech Republic > projects: https://www.openhub.net/accounts/ppisa > social: https://social.kernel.org/ppisa > CAN related:http://canbus.pages.fel.cvut.cz/ > RISC-V education: https://comparch.edu.cvut.cz/ > Open Technologies Research Education and Exchange Services > https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home >
