Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The development branch of the plugin version of the GUI can be found in its own github repository: https://github.com/open-ephys/plugin-GUI 

Once it's been tested for stability, it will replace the current static version of the software.

Thanks to Yogi Patel for his initial contributions to the plugin architecture.

Downloading binaries

Precompiled binaries are available for the following systems:

Building the plugin-based GUI

Building the core GUI follows the same steps that the non-plugin version, listed on the Installation page for each operating system.

To compile the plugins follow these steps. By default, the build process will copy the plugins into the appropiate plugin folder inside the building path.

On Windows
  1. The GUI must be compiled prior to the plugins, as the plugin build process needs the open-ephys.lib file created by doing so in its default directory.
  2. Open the VS solution file Builds\Visualstudio2013\Plugins\Plugins.sln
  3. Select the appropiate architecture and release mode that matches the one the GUI was built with.
  4. Either build the complete solution to generate all plugins or build specific projects to compile just specific ones.
On Linux and Mac
  1. Using a console, enter the Builds/Linux or Builds/MacOSX directory
  2. Execute the following command: "make -f Makefile.plugins" to build all plugins
  • To clean the plugin build space, type "make -f Makefile.plugins clean"
  • To compile just a specific plugin, type "make -f Makefile.plugins <NameOfThePluginFolder>"
  • Only those plugins that have a Makefile file inside their source directory will be built

Running the plugin-based GUI

Running the plugin-based GUI is no different than running the regular GUI. All the plugins located on the "plugins" folder next to the excutable will be loaded at startup and available as usual.

Note that trying to load a signal chain from the non-plugin GUI into the plugin GUI or viceversa won't work and might result in a crash.

  • No labels