Rebuild BCI2000 - Revision history

Mellinger at 14:26, 5 March 2026

2026-03-05T14:26:58Z

← Older revision		Revision as of 14:26, 5 March 2026
Line 31:		Line 31:

	''Final Result'': Only '''one''' executable in the <code>prog</code> folder has been updated!		''Final Result'': Only '''one''' executable in the <code>prog</code> folder has been updated!

			==See also==
			[[Programming Howto:Building and Customizing BCI2000]]

			[[Category:Development]]

Wengelhardt at 20:13, 13 May 2025

2025-05-13T20:13:48Z

@@ Line 10: / Line 10: @@
 =Full rebuild=
 #Run ''Configure.sh.cmd'' in the BCI2000 <code>build</code> directory [[File:Use cmake 1.PNG|thumb|Step 1 - Run ''Configure.sh.cmd'']]
 #Press <code>Generate</code> (this automatically runs <code>Configure</code> then <code>Generate</code>). This runs CMake to reconfigure the BCI2000 solution. Essentially, it draws all the paths between the files and makes everything ready to compile. [[File:Use cmake 9.PNG|thumb|Step 3 - CMake is reconfigured and generated]]
@@ Line 15: / Line 16: @@
 #In Visual Studio, go to <code>Build → Build Solution</code>, or right-click ''Solution 'BCI2000''' in the ''Solution Explorer''. [[File:Use vs2017 3.png|thumb|Step 4 - Build full solution]]
 ''Final Result'': Every executable in the <code>prog</code> folder has been updated!

Wengelhardt at 18:59, 13 May 2025

2025-05-13T18:59:18Z

← Older revision		Revision as of 18:59, 13 May 2025
Line 8:		Line 8:

	We will first go over the steps to completely rebuild BCI2000, then detail how this process can be streamlined for specific cases.		We will first go over the steps to completely rebuild BCI2000, then detail how this process can be streamlined for specific cases.

			=Full rebuild=
			#Run ''Configure.sh.cmd'' in the BCI2000 <code>build</code> directory [[File:Use cmake 1.PNG\|thumb\|Step 1 - Run ''Configure.sh.cmd'']]
			#Press <code>Generate</code> (this automatically runs <code>Configure</code> then <code>Generate</code>). This runs CMake to reconfigure the BCI2000 solution. Essentially, it draws all the paths between the files and makes everything ready to compile. [[File:Use cmake 9.PNG\|thumb\|Step 3 - CMake is reconfigured and generated]]
			#Press the <code>Open Project</code> button or open <code>BCI2000.sln</code> in the <code>build</code> folder to open it in Visual Studio.
			#In Visual Studio, go to <code>Build → Build Solution</code>, or right-click ''Solution 'BCI2000''' in the ''Solution Explorer''. [[File:Use vs2017 3.png\|thumb\|Step 4 - Build full solution]]
			''Final Result'': Every executable in the <code>prog</code> folder has been updated!

Wengelhardt: Created page with "This tutorial is for developers who have downloaded the prerequisites and have the source code. If the follow the previous steps, you will have the full, default version of BCI2000 on your local computer. This maximizes the ease-of-use and flexibility for any custom uses. However, if you want to include any changes in the BCI2000 infrastructure, '''you will need to rebuild the appropriate modules in BCI2000'''. This..."

2025-05-13T16:46:32Z

Created page with "This tutorial is for developers who have downloaded the prerequisites and have the source code. If the follow the previous steps, you will have the full, default version of BCI2000 on your local computer. This maximizes the ease-of-use and flexibility for any custom uses. However, if you want to include any changes in the BCI2000 infrastructure, '''you will need to rebuild the appropriate modules in BCI2000'''. This..."

New page

This tutorial is for developers who have [[Programming Howto:Building and Customizing BCI2000|downloaded the prerequisites and have the source code]]. If the follow the previous steps, you will have the full, default version of BCI2000 on your local computer. This maximizes the ease-of-use and flexibility for any custom uses.

However, if you want to include any changes in the BCI2000 infrastructure, '''you will need to rebuild the appropriate modules in BCI2000'''. This page will first detail ''how'' to choose what needs to be rebuilt, and then ''what'' steps are needed to rebuild BCI2000 with your changes.

=What needs to be rebuilt?=
[[File:Modules.png|thumb|BCI2000 design. Each module is an executable.]]
BCI2000 always runs 4 modules (executables, .exe), as shown here. To run BCI2000, all 4 executables are run. Therefore, to update BCI2000, these executables need to be updated. In fact, only the executable that includes custom changes need to be updated. Therefore, in most cases (e.g., adding a custom filter, module, or extension), '''only one executable needs to be updated'''.

We will first go over the steps to completely rebuild BCI2000, then detail how this process can be streamlined for specific cases.