ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
The CMakeLists.txt uses pkg-config to find LOG4CXX. Could it be that liblog4cxx.pc
is missing from your $PKG_CONFIG_PATH
? See: https://github.com/strawlab/ros_comm/blob/master/tools/rosconsole/CMakeLists.txt#L38
2 | No.2 Revision |
The CMakeLists.txt uses pkg-config to find LOG4CXX. Could it be that liblog4cxx.pc is missing from your $PKG_CONFIG_PATH?
See: https://github.com/strawlab/ros_comm/blob/master/tools/rosconsole/CMakeLists.txt#L38
3 | No.3 Revision |
The CMakeLists.txt uses pkg-config to find LOG4CXX. Could it be that liblog4cxx.pc is missing from your $PKG_CONFIG_PATH?
See: https://github.com/strawlab/ros_comm/blob/master/tools/rosconsole/CMakeLists.txt#L38
UPDATE: oops! I had failed to notice that the link above is to the wrong repository.
The correct groovy_devel
version is here: https://github.com/ros/ros_comm/blob/groovy-devel/tools/rosconsole/CMakeLists.txt#L6
That file uses CMAKE find_package()
instead of pkg-config
to locate log4cxx.
Unfortunately, I don't know where that CMake module is supposed to be defined. The Debian liblog4cxx10-dev
package seems to provide the pkg-config file, but not CMake module.
This may be a bug that only crops up when cross-compiling. I just don't know.
4 | No.4 Revision |
The CMakeLists.txt uses pkg-config to find LOG4CXX. Could it be that liblog4cxx.pc is missing from your $PKG_CONFIG_PATH?
See: https://github.com/strawlab/ros_comm/blob/master/tools/rosconsole/CMakeLists.txt#L38
UPDATE: oops! I had failed to notice that the link above is to the wrong repository.
The correct groovy_devel
version is here: https://github.com/ros/ros_comm/blob/groovy-devel/tools/rosconsole/CMakeLists.txt#L6
That file uses CMAKE find_package()
instead of pkg-config
to locate log4cxx.
Unfortunately, I don't know where that CMake module is supposed to be defined. The Debian liblog4cxx10-dev
package seems to provide the pkg-config file, but not no CMake module.
This may be a bug that only crops up when cross-compiling. I just don't know.