|OpenViBE meta repository| |README|

Build Status :
Ubuntu 20.04 x64
Fedora 31 x64
Windows 10 x64
Windows 10 x86

OpenViBE project is now divided into 3 parts :

• SDK, that contains the certifiable core and plugins of OpenViBE
• Designer, the graphical interface for OpenViBE
• Extras, for community plugins and contributions

The current repository, OpenViBE-meta, exist to bring the three repositories together and build the project.

To build OpenViBE, follow these instructions :

• Pull this repository
• Pull its submodules
• Install the dependencies
• Build the project

Pulling this repository

Run the following command:

git pull git@gitlab.inria.fr:openvibe/meta.git

or with any GUI for git, like GitKraken.

Pulling the submodules

Pull the sdk, designer and extras repositories with the following:

git submodule update --init --recursive

Installing the dependencies

Windows

Run the following command:

> .\install_dependencies.cmd

Dependencies will be installed in a dependencies folder at the root of the project.

Linux

Run the following command:

$ ./install_dependencies.sh

Dependencies will be installed in a dependencies folder at the root of the project.
Some will be installed on the system.

Building the project

Windows

Execute the following command:

> .\build.cmd

You will require Visual Studio 2013 (Professional or Community editions)

Applications are installed in the dist folder at the root, and are launchable using their launch script: openvibe-[application-name].cmd

Generate Visual Studio Solution

To generate the visual studio solution of the project, run the following command:

> .\build.cmd --vsbuild

The solution will be in the folder build-vs
The solution allows you to view/edit code in Visual Studio, but not to compile the project for the moment.

Linux

Execute the following command:

$ ./build.sh

Applications are installed in the dist folder at the root, and are launchable using their launch script: openvibe-[application-name].sh

Updating the repository

You can update the whole directory (including submodules) with :

git pull
git submodule sync --recursive
git submodule update --init --recursive

Aliases can be created to ease the global update process : git config --global alias.spull '!git pull && git submodule sync --recursive && git submodule update --init --recursive'