How to Install and Uninstall mraa Package on openSUSE Leap
Last updated: December 24,2024
1. Install "mraa" package
This is a short guide on how to install mraa on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
mraa
Copied
2. Uninstall "mraa" package
Here is a brief guide to show you how to uninstall mraa on openSUSE Leap:
$
sudo zypper remove
mraa
Copied
3. Information about the mraa package on openSUSE Leap
Information for package mraa:
-----------------------------
Repository : Main Repository
Name : mraa
Version : 2.2.0-bp155.2.13
Arch : x86_64
Vendor : openSUSE
Installed Size : 76.0 KiB
Installed : No
Status : not installed
Source package : mraa-2.2.0-bp155.2.13.src
Upstream URL : https://github.com/eclipse/mraa
Summary : Low Level Skeleton Library for IO Communication
Description :
libmraa is a C/C++ library with bindings to Java, Python and JavaScript to
interface with the IO on Galileo, Edison & other platforms, with a
structured and sane API where port names/numbering matches the board that
you are on. Use of libmraa does not tie you to specific hardware with board
detection done at runtime you can create portable code that will work
across the supported platforms.
The intent is to make it easier for developers and sensor manufacturers to
map their sensors & actuators on top of supported hardware and to allow
control of low level communication protocol by high level languages &
constructs.
-----------------------------
Repository : Main Repository
Name : mraa
Version : 2.2.0-bp155.2.13
Arch : x86_64
Vendor : openSUSE
Installed Size : 76.0 KiB
Installed : No
Status : not installed
Source package : mraa-2.2.0-bp155.2.13.src
Upstream URL : https://github.com/eclipse/mraa
Summary : Low Level Skeleton Library for IO Communication
Description :
libmraa is a C/C++ library with bindings to Java, Python and JavaScript to
interface with the IO on Galileo, Edison & other platforms, with a
structured and sane API where port names/numbering matches the board that
you are on. Use of libmraa does not tie you to specific hardware with board
detection done at runtime you can create portable code that will work
across the supported platforms.
The intent is to make it easier for developers and sensor manufacturers to
map their sensors & actuators on top of supported hardware and to allow
control of low level communication protocol by high level languages &
constructs.