ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Undefined references. Typically this happens when it looks for your cross compiled library, but picked up your native library instead. Some things to check:

  • Find your toolchain's library path (the one with libpthread-2.8.so in it, if you subtract the lib folder, this needs to match CMAKE_FIND_ROOT_PATH in your toolchain module.
  • Make sure your cross compiled libraries are there, otherwise it may fall back to trying to use your native libraries.

If you're not using a standard eros toolchain module you may have incorrectly specified these settings when attempting to create a custom toolchain module. Refer to the latter page for more hints on how to track down your library/header paths.

Undefined references. Typically this happens when it looks for your cross compiled library, but picked up your native library instead. Some things to check:

  • Your CMAKE_FIND_ROOT_PATH. This is where cmake expects to search for libs and headers. If its wrong, it falls back to native directories. Find your toolchain's library path (the one with libpthread-2.8.so in it, if you subtract the lib folder, this needs to match CMAKE_FIND_ROOT_PATH in your toolchain module.you have the correct string.
  • Make sure your cross compiled libraries are there, otherwise it may fall back to trying to use your native libraries.

If you're not using a standard eros toolchain module you may have incorrectly specified these settings when attempting to create a custom toolchain module. Refer to the latter page for more hints on how to track down your library/header paths.

Undefined references. Typically this happens when it looks for your cross compiled library, but picked up your native library instead. Some things to check:

  • Your CMAKE_FIND_ROOT_PATH. This is where cmake expects to search for libs and headers. If its wrong, it falls can fall back to native directories. Find your toolchain's library path (the one with libpthread-2.8.so in it, if you subtract the lib folder, you have the correct string.
  • Make sure your cross compiled libraries are there, otherwise it may fall back to trying to use your native libraries.

If you're not using a standard eros toolchain module you may have incorrectly specified these settings when attempting to create a custom toolchain module. Refer to the latter page for more hints on how to track down your library/header paths.

Undefined references. Typically this happens when it looks for your cross compiled library, but picked up your native library instead. Some things to check:

  • Your CMAKE_FIND_ROOT_PATH. This is where cmake expects to search for libs and headers. If its wrong, it can fall back to native directories. Find your toolchain's library path (the one with libpthread-2.8.so in it, if you subtract the lib folder, you have the correct string.
  • Make sure your cross compiled libraries are there, otherwise it may fall back to trying to use your native libraries.

If you're not using a standard eros toolchain module you may have incorrectly specified these the TOOLCHAIN_SYSROOT, TOOLCHAIN_INSTALL_PREFIX (and subsequently CMAKE_FIND_ROOT_PATH) settings when attempting to create a custom toolchain module. Refer to the latter page for more hints on how to track down your library/header paths.