Jump to content

Category:Extension: Difference between revisions

From BCI2000 Wiki
Mellinger (talk | contribs)
Created page with "A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the..."
 
Mellinger (talk | contribs)
No edit summary
 
Line 1: Line 1:
A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the src/contrib/Extensions folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the Programming Howto:Quickstart Guide for a walkthrough that shows you how to recompile BCI2000 modules.
A framework ''Extension'' is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific [[User Reference:Logging Input|input-device loggers]] are provided in the <code>src/contrib/Extensions</code> folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the [[Programming Howto:Quickstart Guide]] for a walkthrough that shows you how to recompile BCI2000 modules.

Latest revision as of 16:41, 8 July 2022

A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the src/contrib/Extensions folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the Programming Howto:Quickstart Guide for a walkthrough that shows you how to recompile BCI2000 modules.