How to Install and Uninstall eegdev.x86_64 Package on Fedora 35
Last updated: January 09,2025
1. Install "eegdev.x86_64" package
This guide covers the steps necessary to install eegdev.x86_64 on Fedora 35
$
sudo dnf update
Copied
$
sudo dnf install
eegdev.x86_64
Copied
2. Uninstall "eegdev.x86_64" package
This guide let you learn how to uninstall eegdev.x86_64 on Fedora 35:
$
sudo dnf remove
eegdev.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the eegdev.x86_64 package on Fedora 35
Last metadata expiration check: 4:54:39 ago on Wed Sep 7 08:25:01 2022.
Available Packages
Name : eegdev
Version : 0.2
Release : 13.fc35
Architecture : x86_64
Size : 31 k
Source : eegdev-0.2-13.fc35.src.rpm
Repository : fedora
Summary : Library to acquire data from various EEG recording devices
URL : http://cnbi.epfl.ch/software/eegdev.html
License : LGPLv3+
Description : eegdev is a library that provides a unified interface for accessing various EEG
: (and other biosignals) acquisition systems. This interface has been designed to
: be both flexible and efficient. The device specific part is implemented by the
: mean of plugins which makes adding new device backend fairly easy even if the
: library does not support them yet officially.
:
: The core library not only provides to users a unified and consistent interfaces
: to the acquisition device but it also provides many functionalities to the
: device backends (plugins) ranging from configuration to data casting and scaling
: making writing new device backend an easy task.
Available Packages
Name : eegdev
Version : 0.2
Release : 13.fc35
Architecture : x86_64
Size : 31 k
Source : eegdev-0.2-13.fc35.src.rpm
Repository : fedora
Summary : Library to acquire data from various EEG recording devices
URL : http://cnbi.epfl.ch/software/eegdev.html
License : LGPLv3+
Description : eegdev is a library that provides a unified interface for accessing various EEG
: (and other biosignals) acquisition systems. This interface has been designed to
: be both flexible and efficient. The device specific part is implemented by the
: mean of plugins which makes adding new device backend fairly easy even if the
: library does not support them yet officially.
:
: The core library not only provides to users a unified and consistent interfaces
: to the acquisition device but it also provides many functionalities to the
: device backends (plugins) ranging from configuration to data casting and scaling
: making writing new device backend an easy task.