[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

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

e.g. replacing dlopen() by the > libtool equivalent. IIRC it should be fairly trivial. PRs are happily > accepted. > > HTH > Rainer > El mar., 16 oct. 2018 a las 12:56, Satyam Sharma via rsyslog > () escribió: > > > > Hello all, > > > > I am porting rsyslog (latest) to a

Re: [rsyslog] rsyslog version numbering change

Hello Rainer, all, This scheme does seem most sound for multiple reasons. It retains a kind of 'major version numbering backward compatibility' for user expectations and encodes the date as well. Another way to make it less "wordy", apart from changing to YY, could be to drop the DD as