Compiling On Non-Windows Platforms: Difference between revisions
Created page with "==Configure BCI2000 for Compilation== ===Run the CMake GUI=== Double-click "Configure.sh.cmd" in your BCI2000 build directory. ===Tell CMake which Qt installation to use===..." |
|||
| Line 23: | Line 23: | ||
Run: | Run: | ||
make | make | ||
from your BCI2000 build directory. Once this is finished your BCI2000 prog directory will contain a number of executables, one for each module, plus a few helper executables. | from your BCI2000 build directory. Once this is finished your BCI2000 prog directory will contain a number of executables, one for each module, plus a few helper executables. Not everything works the same or, in some cases, at all on non-windows platforms. See, [[Non-Windows Functionality]] for more information. | ||
Revision as of 16:22, 24 July 2022
Configure BCI2000 for Compilation
Run the CMake GUI
Double-click "Configure.sh.cmd" in your BCI2000 build directory.
Tell CMake which Qt installation to use
Click "AddEntry" in the CMake window (Note that checking off "Advanced" in Cmake is optional and does not impact the compilation) and enter the path to a Qt directory. Use CMAKE_PREFIX_PATH as the name for the new entry. Be aware that the entry's name is case sensitive. Currently, on non-windows platform, Qt 5 is the only version that is supported.
Note About Dependencies
There are three dependencies that must be installed prior to building on Non-Windows platforms: ffmpeg (version 4.4.1), sdl2, and portaudio. These will be automatically installed with a portable version of homebrew when cmake is run (this takes awhile). Alternatively, you can install them yourself and disable the automatic installation by setting the cmake variable INSTALL_NO_DEPENDENCIES to ON.
Perform the configuration step
In the CMake window, click "Configure" and choose a generator that is consistent with your compiler. This tutorial will be using Unix Makefiles. Then click "Done" to perform the configuration step. You will see a list of targets scrolling by, and a number of new entries in the variable list at the top of the window, marked in red.
Choose Build Options
Make sure the "Grouped" checkbox is checked, and configure the build by customizing values in the "BUILD" group, "EXTENSIONS" group, and "USE" group. Then, click "Generate" to create build files. When CMake displays its "Generating done" message, your BCI2000 build directory will now contain a Makefile (or a project file for your compiler of chioce), as well as a number of additional CMake-generated files.
Compile BCI2000
Open Terminal
Open a new terminal window and navigate to your BCI2000 build directory.
Build Makefiles
Run:
make
from your BCI2000 build directory. Once this is finished your BCI2000 prog directory will contain a number of executables, one for each module, plus a few helper executables. Not everything works the same or, in some cases, at all on non-windows platforms. See, Non-Windows Functionality for more information.