<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.bci2000.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mayaudlo</id>
	<title>BCI2000 Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.bci2000.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mayaudlo"/>
	<link rel="alternate" type="text/html" href="https://www.bci2000.org/mediawiki/index.php/Special:Contributions/Mayaudlo"/>
	<updated>2026-06-10T23:59:27Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://www.bci2000.org/mediawiki/index.php?title=Programming_Howto:Building_BCI2000&amp;diff=1832</id>
		<title>Programming Howto:Building BCI2000</title>
		<link rel="alternate" type="text/html" href="https://www.bci2000.org/mediawiki/index.php?title=Programming_Howto:Building_BCI2000&amp;diff=1832"/>
		<updated>2007-07-25T17:25:32Z</updated>

		<summary type="html">&lt;p&gt;Mayaudlo: /* Compiling BCI2000 with Borland C++ Builder 2006 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This document describes how to build BCI2000, i.e. how to create the BCI2000 executables from their source code.&lt;br /&gt;
&lt;br /&gt;
== Why to build ==&lt;br /&gt;
Typically, you will install BCI2000 from its binary distribution, and do not need to build BCI2000, unless&lt;br /&gt;
*you want to always use its most current SVN version,&lt;br /&gt;
*you create your own module by modifying an existing one, or create a new one from scratch.&lt;br /&gt;
&lt;br /&gt;
== Tools required ==&lt;br /&gt;
As of BCI2000 version 2.0, building all parts of BCI2000 requires Borland&#039;s C++ Builder 6, or a more recent version.&lt;br /&gt;
The operator GUI and Application modules currently require the Borland VCL library.&lt;br /&gt;
Non-GUI related parts of BCI2000 can be built using the freely available Borland C++ compiler:&lt;br /&gt;
*[[Command line tools]] &lt;br /&gt;
*[[Matlab mex files]]&lt;br /&gt;
&lt;br /&gt;
Matlab mex files can also be built on platforms other than Win32. Please use the src/tools/mex/buildmex.m Matlab script (tested with gcc).&lt;br /&gt;
&lt;br /&gt;
==How to build==&lt;br /&gt;
===Compiling BCI2000 from the command line===&lt;br /&gt;
# Open a Windows cmd shell, e.g. by choosing &amp;quot;Run...&amp;quot; from the Start Menu and entering &amp;quot;cmd&amp;quot;. &lt;br /&gt;
# Change to the &amp;quot;src&amp;quot; directory where this document resides.&lt;br /&gt;
# Execute &amp;quot;make&amp;quot; from the command prompt.&lt;br /&gt;
# If you updated or edited any of the source files, and experience linker errors or other unexpected behavior, execute &amp;quot;make clean &amp;amp;&amp;amp; make all&amp;quot;.&lt;br /&gt;
    &lt;br /&gt;
===Compiling BCI2000 using the Borland C++ Builder 6 IDE===&lt;br /&gt;
# Open the file &amp;quot;BCI2000.bpg&amp;quot; with the IDE by double-clicking it.&lt;br /&gt;
# Make sure the &amp;quot;ProjectManager&amp;quot; view is visible to the left.&lt;br /&gt;
# Right-click the topmost project (located immediately below the line reading &amp;quot;BCI2000&amp;quot;), and choose &amp;quot;Make all from here&amp;quot;.&lt;br /&gt;
# To get rid of possible inconsistencies from earlier builds, choose &amp;quot;Build all from here&amp;quot; rather than &amp;quot;Make all from here&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Starting up BCI2000===&lt;br /&gt;
# After compilation, a desired configuration of BCI2000 may be started by executing an appropriate batch file from the top level &amp;quot;batch&amp;quot; directory. Once a particular configuration of BCI2000 is started, simply load a parameter file with the same name as the batch file from the &amp;quot;parms&amp;quot; directory.&lt;br /&gt;
# If you need a configuration for which no batch file exists, just modify a copy of a batch file that is close to your needs.&lt;br /&gt;
&lt;br /&gt;
===Compiling BCI2000 with Borland C++ Builder 2006===&lt;br /&gt;
# Open the file &amp;quot;BCI2000.bpg&amp;quot; from within Borland Developer Studio. This will import all existing projects into BDS project files.&lt;br /&gt;
# For each project, open the &amp;quot;Options...&amp;quot; dialog, go to &amp;quot;C++ Compiler-&amp;gt;Precompiled Headers&amp;quot;, and uncheck all check boxes. Then, go to &amp;quot;Link (ilink32)-&amp;gt;Path and Definitions&amp;quot;, and add &amp;quot;$(BDS)\lib\psdk&amp;quot; to &amp;quot;Library Research Path (-L)&amp;quot;. &lt;br /&gt;
# In the project manager (at the top right), right-click the topmost project and choose &amp;quot;Make all from here&amp;quot;.&lt;br /&gt;
# To get rid of possible inconsistencies from earlier builds, choose &amp;quot;Build all from here&amp;quot; instead of &amp;quot;Make all from here&amp;quot;.&lt;br /&gt;
# Command-line builds cannot be done with Borland C++ Builder 2006 because it lacks a project-to-makefile conversion utility.&lt;/div&gt;</summary>
		<author><name>Mayaudlo</name></author>
	</entry>
</feed>