Re: [rsyslog] Porting rsyslog to an OS that does not support dynamic linking or shared libraries

El mar., 16 oct. 2018 a las 15:48, Satyam Sharma () escribió: > > Hi Rainer, > > Thanks much for responding. > > Your recommendation to use libtool's dlopen()-equivalent API for > static libraries does seem nicely workable for my problem without much > disturbance to existing code. I will

Re: [rsyslog] Porting rsyslog to an OS that does not support dynamic linking or shared libraries

Hi Rainer, Thanks much for responding. Your recommendation to use libtool's dlopen()-equivalent API for static libraries does seem nicely workable for my problem without much disturbance to existing code. I will definitely try this, and would be happy to contribute a generalized patch if it

Re: [rsyslog] Porting rsyslog to an OS that does not support dynamic linking or shared libraries

just a quick answer after having just a glimpse over your mail: look into libtool, it supports that use case. Fully utilizing this may require some changes to rsyslog, e.g. replacing dlopen() by the libtool equivalent. IIRC it should be fairly trivial. PRs are happily accepted. HTH Rainer El

[rsyslog] Porting rsyslog to an OS that does not support dynamic linking or shared libraries

Hello all, I am porting rsyslog (latest) to an embedded OS that does not support shared libraries or dynamic linking at all. My system does not provide dlopen()/dlsym() and friends, and my toolchain does not create .so's in the first place, so my porting effort is having to update the sources