Closed homalozoa closed 2 years ago
I'm actually going to close this one, since we are going to remove the log4cxx backend in #78.
@clalancette can #78 hit the galactic
branch? If not, I think this PR should be merged into the galactic
branch, or else the build error being addressed by this PR is still a problem in Galactic. One recent report: https://answers.ros.org/question/390793/ros2-fails-to-build-at-rcl_logging_log4cxx/
@clalancette can #78 hit the
galactic
branch? If not, I think this PR should be merged into thegalactic
branch, or else the build error being addressed by this PR is still a problem in Galactic. One recent report: https://answers.ros.org/question/390793/ros2-fails-to-build-at-rcl_logging_log4cxx/
Agreed
@clalancette can #78 hit the
galactic
branch?
Hm, tough one. Technically we could probably do it, as it is not being linked against by the rest of the core. But on the other hand, we don't know if any downstream packages are depending on it (unlikely, but hard to tell). So I think the safest thing would be to not merge #78 into galactic.
Thus, I'm fine with reopening this and targeting it strictly to Galactic.
Signed-off-by: Homalozoa xuhaiwang@xiaomi.com
Fix building error with log4cxx 0.12.0. shared_mutex is only available from C++ 17 onwards, ref: std::shared_mutex