| malcontent-ui |
0.14.0 |
User-Interface for malcontent. |
meta-oe |
| mali-imx |
r54.0 |
Graphics libraries and driver for i.MX Mali GPU |
meta-freescale |
| mali450-userland |
r7p0 |
ARM Mali Utgard GPU User Space driver for HiKey (drm backend) |
meta-96boards |
| maliit-framework-qt5 |
0.99.0+gitX |
A virtual keyboard for touch-screen based user interfaces |
meta-qt5 |
| maliit-plugins-qt5 |
0.99.0+gitX |
Plugins for a virtual keyboard for touch-screen based user interfaces |
meta-qt5 |
| man-db |
2.13.1 |
An implementation of the standard Unix documentation system accessed using the man command |
openembedded-core |
| man-db |
2.13.1 |
An implementation of the standard Unix documentation system accessed using the man command |
meta-voltumna |
| man-pages |
6.18 |
Linux man-pages |
openembedded-core |
| man-pages |
6.17 |
Linux man-pages |
meta-voltumna |
| mbf-abstract-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros1-melodic |
| mbf-abstract-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros1-noetic |
| mbf-abstract-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros2-humble |
| mbf-abstract-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros2-jazzy |
| mbf-costmap-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the CostmapPlanner, CostmapController and CostmapRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_costmap_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and binds the system to a local and a global costmap. |
meta-ros1-melodic |
| mbf-costmap-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the CostmapPlanner, CostmapController and CostmapRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_costmap_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and binds the system to a local and a global costmap. |
meta-ros1-noetic |
| mbf-costmap-nav |
0.4.0-1 |
The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the <a href="wiki.ros.org/costmap_2d">costmap_2d</a> representation. It provides the Actions for planning, controlling and recovering. At the time of start MBF loads all defined plugins. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. Additionally the mbf_costmap_nav package comes with a wrapper for the old navigation stack and the plugins which inherits from the <a href="wiki.ros.org/nav_core">nav_core</a> base classes. Preferably it tries to load plugins for the new API. However, plugins could even support both <a href="wiki.ros.org/move_base">move_base</a> and <a href="wiki.ros.org/move_base_flex">move_base_flex</a> by inheriting both base class interfaces located in the <a href="wiki.ros.org/nav_core">nav_core</a> package and in the <a href="mbf_costmap_core">mbf_costmap_core</a> package. |
meta-ros1-melodic |
| mbf-costmap-nav |
0.4.0-1 |
The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the <a href="wiki.ros.org/costmap_2d">costmap_2d</a> representation. It provides the Actions for planning, controlling and recovering. At the time of start MBF loads all defined plugins. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. Additionally the mbf_costmap_nav package comes with a wrapper for the old navigation stack and the plugins which inherits from the <a href="wiki.ros.org/nav_core">nav_core</a> base classes. Preferably it tries to load plugins for the new API. However, plugins could even support both <a href="wiki.ros.org/move_base">move_base</a> and <a href="wiki.ros.org/move_base_flex">move_base_flex</a> by inheriting both base class interfaces located in the <a href="wiki.ros.org/nav_core">nav_core</a> package and in the <a href="mbf_costmap_core">mbf_costmap_core</a> package. |
meta-ros1-noetic |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-humble |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-jazzy |
| mbf-simple-nav |
0.4.0-1 |
The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. |
meta-ros1-melodic |
| mbf-simple-nav |
0.4.0-1 |
The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. |
meta-ros1-noetic |
| mbf-simple-nav |
1.0.5-1 |
The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. |
meta-ros2-humble |
| mbf-simple-nav |
1.0.5-1 |
The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. |
meta-ros2-jazzy |
| mbw |
2.0 |
MBW determines the copy memory bandwidth available to userspace programs |
meta-oe |
| media-export |
0.3.0-1 |
Placeholder package enabling generic export of media paths. |
meta-ros1-melodic |
| media-export |
0.3.0-1 |
Placeholder package enabling generic export of media paths. |
meta-ros1-noetic |
| mender-orchestrator-support |
0.4.0 |
Interfaces and Update Modules for mender-orchestrator |
meta-mender-commercial |
| mender-orchestrator-support |
main-gitX |
Interfaces and Update Modules for mender-orchestrator |
meta-mender-commercial |
| mender-orchestrator-support |
0.5.0 |
Interfaces and Update Modules for mender-orchestrator |
meta-mender-commercial |
| mender-orchestrator-support |
0.6.0 |
Interfaces and Update Modules for mender-orchestrator |
meta-mender-commercial |
| meson |
1.11.2 |
A high performance build system |
openembedded-core |
| meson |
0.62.1 |
A high performance build system |
meta-gstreamer10 |
| meson |
1.11.1 |
A high performance build system |
meta-voltumna |
| meson |
1.5.1 |
A high performance build system |
meta-webos-backports-5.1 |
| metee |
6.2.4 |
Intel(R) METEE Library |
meta-intel |
| metee |
6.0.2 |
Intel(R) METEE Library |
meta-voltumna |
| metrics-discovery |
1.14.182 |
Intel Metrics Discovery Application Programming Interface |
meta-intel |
| metrics-discovery |
1.14.182 |
Intel Metrics Discovery Application Programming Interface |
meta-voltumna |
| metro-benchmark-msgs |
0.1.1-1 |
ROS interfaces for recording compute time and other related benchmarking concepts |
meta-ros2-humble |
| micropython-serial |
0.2 |
pySerial-like interface for MicroPython (unix port) |
meta-micropython |
| minio |
01b87ecc02ffad47dfe13c2154ac31db3e3115df |
MinIO Client is a replacement for ls, cp, mkdir, diff and rsync commands for filesystems and object storage. |
meta-oe |
| mink-idl-compiler |
0.2.3 |
Mink IDL compiler |
meta-qcom |
| mixlib-shellout |
2.1.0 |
Provides a simplified interface to shelling |
meta-openstack |
| mmc-utils |
1.0 |
Userspace tools for MMC/SD devices |
openembedded-core |
| mmc-utils-cos |
0.1 |
Userspace tools for MMC/SD devices (Downstream version of Chromium OS Project) |
meta-toradex-demos |
| mocap4r2-msgs |
0.0.6-2 |
Interfaces for Mocap4ROS2 project |
meta-ros2-humble |
| mocap4r2-msgs |
0.1.0-1 |
Interfaces for Mocap4ROS2 project |
meta-ros2-jazzy |
| mocap4r2-msgs |
0.2.0-1 |
Interfaces for Mocap4ROS2 project |
meta-ros2-kilted |
| mod-wsgi |
5.0.2+gitX |
Supports the Python WSGI interface |
meta-openstack |
| module-build-tiny-perl |
0.039 |
Many Perl distributions use a Build.PL file instead of a Makefile.PL file to drive distribution configuration, build, test and installation. Traditionally, Build.PL uses Module::Build as the underlying build system. This module provides a simple, lightweight, drop-in replacement. |
meta-cpan |