rm5248 commented on PR #242:
URL: https://github.com/apache/logging-log4cxx/pull/242#issuecomment-1666593297
> > there could be issues if a project (implictly) is using both
>
> The application code would not be able to use the Qt API methods if they
depend on a component that uses a non-Qt flavour liblog4cxx (not a common
occurance), unless they could rebuild the component against the liblog4cxxqt
library.
>
The problem Tobi is talking about is if we have:
```
application
--> libexample.so --> liblog4cxx.so
--> liblog4cxxqt.so
```
The same symbols would be in both liblog4cxx.so and liblog4cxxqt.so. We
could change the namespace if the library is built with Qt though, but that
doesn't seem too fun either...
> > Is it possible only to have the QT parts in the qt library and the qt
library using "under the hoods" the regular one?
>
> As Log4cxx is a C++ API, the interfaces are class methods which cannot be
separated AFAIK.
If we're adding methods to support QStrings, that sounds correct to me. The
current Qt support is in a separate library so it does not bring in any Qt
methods. So I would be more in favor of just adding an `operator<<` support
for QString, which should handle most of the logging cases.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
