class_loader
class_loader copied to clipboard
ros
ROS-independent library for dynamic class (i.e. plugin) introspection and loading from runtime libraries
Currently in Noetic/Focal the script cannot be run with rosrun: ``` /usr/bin/env: ‘python’: No such file or directory ```
Using the ClassLoader (version `0.4.1`) via pluginlib as recommended, we could detect some memory leaks. My guess is that metaobjects are not destroyed after they have been inserted into the...
``` CMake Error at /home/janr/.cache/yay/ros-melodic-class-loader/src/build/devel/share/class_loader/cmake/class_loaderConfig.cmake:113 (message): Project 'class_loader' specifies '/include' as an include dir, which is not found. It does neither exist as an absolute directory nor in '/home/janr/.cache/yay/ros-melodic-class-loader/src/class_loader-0.4.1//include'. Check...
I found below notes in code. It say `RTLD_GLOBAL` will cause static global variable initialization problem when reopen the library. I try load and unload the library, and the static...
I wonder `num_meta_objs_for_lib_bound_to_loader` will always less than `num_meta_objs_for_lib`, because `num_meta_objs_for_lib_bound_to_loader` is look forward in `allMetaObjectsForLibrary(library_path)` and `num_meta_objs_for_lib` is equal with `allMetaObjectsForLibrary(library_path).size()` https://github.com/ros/class_loader/blob/8864be372a83921f15906ae80752be9d6a300b81/src/class_loader_core.cpp#L304-L312
There is a lock `load_ref_lock` and `class_loader::impl::loadLibrary(getLibraryPath(), this)` will not load .so library twice. Why not just use a bool `is_loaded` to load and unload the .so library. I didn't...
See https://github.com/ros/class_loader/pull/163#issuecomment-673150432
Have possibly identified a bug in dependency detection. I am not sure if this should be filed against this library, catkin, and/or conda. Environment: Docker image w/ Ubuntu 18.04 Miniconda...
@nuclearsandwich do you mind to activate DCO ? this is a required step to reach Quality Level 1 in ROS 2
The `MultiClassLoaderTest.noWarningOnLazyLoad` test case produces a scary looking warning. Judging by the name of the case, (1) the warning should not happen (2) the test case is broken for failing...
