Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automotive GenIVI DLT appender #290

Closed
alexandrzvezdin opened this issue Feb 5, 2018 · 7 comments
Closed

Automotive GenIVI DLT appender #290

alexandrzvezdin opened this issue Feb 5, 2018 · 7 comments
Assignees

Comments

@alexandrzvezdin
Copy link

Hi,
I am planning to implement GenIVI DLT logging appender for log4cplus. It is popular automotive specific logging infrastructure. Are anybody interested in me to upstream such a specific appender?

@wilx wilx self-assigned this Feb 5, 2018
@wilx
Copy link
Contributor

wilx commented Feb 5, 2018

I think this depends on how complex it is and how many, if any, external libraries it needs to work. If you want to put it into log4cplus repository, then it should be a separate library/binary from the core appenders, unless it is not very complex to implement. If it requires external libraries then it should probably be a separate project repository. I wouldn't be able to test it so maintenance burden would be on you.

@alexandrzvezdin
Copy link
Author

Ok, thank you. It will require an external library libdlt.so and also a daemon where all log messages are aggregated. Seems better to have a separate repository for that.

@rpannek
Copy link

rpannek commented Feb 5, 2018

Would it still be possible to build it together and have log4cplus as a git submodule for the other repo? Or would the integration be so interwined with the original code that the only way to integrate DLT would be forking the project?

@wilx
Copy link
Contributor

wilx commented Feb 5, 2018

@rpannek commented on Feb 5, 2018, 5:29 PM GMT+1:

Would it still be possible to build it together and have log4cplus as a git submodule for the other repo? Or would the integration be so interwined with the original code that the only way to integrate DLT would be forking the project?

Personally, it is fine with me. IANAL but I do not see a problem either.

@rpannek
Copy link

rpannek commented Feb 6, 2018

Sorry for not being clear, I didn't mean from a license perspective, the Apache / BSD license makes a fork possible. I just had a quick look at the code structure, etc. and it didn't look to me that one could easily add a new appender from a different git-repo without rewriting parts of this one (there seems not to be any plugin API implemented or something like that), so I wanted to know if you had some tips on how to do that. Forking would be the last resort because it has so many drawbacks.

@wilx
Copy link
Contributor

wilx commented Feb 6, 2018

@rpannek See https://github.com/log4cplus/log4cplus/blob/master/qt5debugappender/qt5debugappender.cxx#L103 It shows how you invoke LOG4CPLUS_REG_APPENDER() macro to register appender. See https://github.com/log4cplus/log4cplus/blob/master/src/factory.cxx for some more details.

@rpannek
Copy link

rpannek commented Feb 6, 2018

Great! Thanks a lot!

@wilx wilx closed this as completed Aug 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants