Skip to content

Linux

Jump to bottom Edit New page
jsiegle edited this page Dec 14, 2012 · 11 revisions

If it's not clear already, the GUI was built on Linux machines, and its creators intend to use it on Linux machines. If it's all possible, we recommend doing your development with Linux.

However, because all of the libraries are cross-platform, we're not too concerned that it won't run anywhere eventually. To this end, the software has been periodically tested on a Mac to make sure things are working. So far, we haven't hit any major snags with making the software sufficiently general. Almost all of the platform-specific code is handled by the Juce library, so we need very few conditional preprocessor definitions in the code.

To get the software running on Ubuntu 10.10, the following is necessary:

  1. Install the Juce dependencies (freeglut3-dev, libfreetype6-dev, libxinerama-dev, libxcursor-dev, libasound2-dev), as well as libFTDI and FTGL.
  2. cd to the /Builds/Linux folder and type make at the bash cursor

There may be other dependencies on other distros. Please let us know if you discover any.

Notes on distributions

  • Linux Mint 13 Maya (recommended) - everything compiles and runs, although there are a few compiler warning related to the Juce library.
  • Ubuntu 10.10 and lower - the software will run, but there are problems loading the Opal Kelly DLL, apparently related to the version of gcc. Upgrading gcc won't fix the problem, so we currently don't recommend using older versions of Ubuntu if you want to use the Open Ephys acquisition board.
  • Ubuntu 12.10 and higher - the software will run, but certain fonts won't load. This is due to unresolved issues with the LinuxFontFileIterator() method in juce_linux_Fonts.cpp

Problems with audio hardware

If the GUI won't start and prints out the message "Program received signal SIGSEGV ... juce_String.cpp:203" after printing "Got audio device." it means the software is having trouble communicating with your audio hardware. Either you have the wrong drivers (or no drivers) installed, or (more commonly) the audio hardware is in use by another application. If exiting other applications doesn't help, typing sudo alsa force-reload in a terminal usually fixes the problem

<< Back to Installation | Continue to OS X issues >>

Add a custom footer
Add a custom sidebar

Clone this wiki locally