BCI2000 Wiki - Recent changes [en]

User Tutorial:BCI2000 Tour

2013-06-18T17:02:12Z

Programming Reference:Building Qt for BCI2000

2013-06-17T16:57:26Z

‎Build and copy mingw libraries and auxiliary files:

Contributions:StatisticsFilter

2013-06-14T20:08:57Z

‎Weight function:

Programming Reference:Building Qt for BCI2000

2013-06-14T18:36:42Z

‎Build and copy MSVC libraries and auxiliary files:

Programming Tutorial:Implementing a Data Acquisition Module

2013-06-12T19:18:43Z

‎Writing the ADC Header File:

Programming Reference:GenericFilter Class

2013-06-12T18:38:46Z

‎Publish:

Programming Reference:Building Qt for BCI2000

2013-06-12T18:06:16Z

Programming Reference:Building BCI2000 for Win64

2013-06-11T16:18:46Z

Programming Reference:Build System

2013-06-11T16:16:13Z

‎Supported Environments:

BCI2000 Binaries

2013-06-11T15:48:07Z

‎Win64 Support:

Programming Reference:Building BCI2000 for Win64

2013-06-11T15:44:11Z

‎Install Qt for x64:

Programming Reference:Building Qt for BCI2000

2013-06-11T15:41:03Z

‎Prepare Qt include files for external use:

@@ Line 70: / Line 70: @@
 ==Stimulus Presentation==
 In addition to the cursor feedback paradigm, BCI2000 comes with a multi-purpose [[User Reference:StimulusPresentationTask|Stimulus Presentation]] module.
-This module has many of the features of dedicated programs like [http://www.neurobs.com/presentation Presentation] or [http://www.pstnet.com/products/e-prime/ e-Prime]. In BCI research, the BCI2000 StimulusPresentation module is often used for  [[User Tutorial:Obtaining Mu Rhythm Parameters in an Initial Session|an initial Mu rhythm session]]. Still, it has very good [[User Reference:Timing|timing precision]], and thus makes its use suitable for a wide range of psychophysiological experiments such as the ERP experiments described  [[User Tutorial:Introduction to the P300 Response|here]]. In addition, it can be used in conjunction with the P3SignalProcessing module (which can average and classify ERPs) to provide real-time feedback to evoked potentials.
+This module is able to deliver visual and auditory stimuli in user-defined or pseudo-random sequences, and may respond to input from external devices. Thus, in many situations, it omits the need for dedicated programs like [http://www.neurobs.com/presentation Presentation] or [http://www.pstnet.com/products/e-prime/ e-Prime]. In BCI research, the BCI2000 StimulusPresentation module is often used for  [[User Tutorial:Obtaining Mu Rhythm Parameters in an Initial Session|an initial Mu rhythm session]]. Still, it has very good [[User Reference:Timing|timing precision]], and thus makes its use suitable for a wide range of psychophysiological experiments such as the ERP experiments described  [[User Tutorial:Introduction to the P300 Response|here]]. In addition, it can be used in conjunction with the P3SignalProcessing module (which can average and classify ERPs) to provide real-time feedback to evoked potentials.
 To try the stimulus presentation module, start BCI2000 using the <tt>batch/StimulusPresentation_SignalGenerator.bat</tt> batch file.

@@ Line 76: / Line 76: @@
   -no-style-cde
 The full command line is:
-  configure -platform win32-g++ -static -no-sql-sqlite -no-qt3support -fast -qt-zlib-qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
+  configure -platform win32-g++ -static -no-sql-sqlite -no-qt3support -fast -qt-zlib -qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
 *When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
 *If you have previously done a full build, open a console window, and run <tt>mingw32-make</tt> in the following directories:
@@ Line 123: / Line 123: @@
 *Likewise, copy the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt> include directories to <tt>qt-x.y.z/include</tt>, omitting the respective <tt>private</tt> directories.
-==Remove debugging information from MSVC libraries==
+==Hide debugging information in MSVC libraries==
 *Despite current MSVC compilers store debugging information in .pdb files, .lib files still contain traditional debugging information. In addition, .lib debugging information refers to .pdb files, and the MSVC linker will issue a large number of warnings if it cannot find those .pdb files.
-*Basically, we can use the GNU objcopy tool in order to strip debugging information from MSVC .lib files. Due to nonstandard behavior of MSVC, it is necessary to do some fixup before and after running objdump on an MSVC-generated .lib file.
+*Basically, we might use GNU binutils, which are able to handle COFF binaries, in order to strip debugging information from those libraries. However, it seems that MSVC compilers store information in such a way that it is not possible to remove arbitrary sections without breaking the files. Thus, we keep all sections but change names of debugging sections such that the MSVC linker will not be able to identify them as such. While this has the disadvantage of retaining large file sizes, it still provides the benefit of fast linking, and suppression of linker warnings.
-*In cygwin, go to <tt>build/buildutils</tt>, and run
+*To hide debugging information, open a cygwin shell, and cd to the qt lib directory that contains MSVC libraries. There, execute
- g++ fixup_msvc_lib.cpp -o fixup_msvc_lib
+  /full/path/to/build/buildutils/strip_msvc_lib.sh *
- g++ coff_set_debug.cpp -o coff_set_debug
-*Then, go to the qt lib directory that contains the MSVC libraries to be stripped, and execute
-  /path/to/build/buildutils/strip_msvc_lib.sh *
-*To strip 64-bit libraries, you will need to have the cygwin-64-bit-toolchain installed, and to add -64 as a first argument to the script:
- /path/to/build/buildutils/strip_msvc_lib.sh -64 *
 ==Upload Qt to the BCI2000 server==

@@ Line 12: / Line 12: @@
 *Tested under: 4151
 *Known to compile under: 4164
 ==Functional Description==
@@ Line 67: / Line 121: @@
 =====obs.CentralMoment(n)=====
 The n-th central moment for each dimension of observer "obs".
-=====obs.Quantile(0>=p>=1)=====
+=====obs.Quantile(p)=====
-The value corresponding to the the given relative frequency in each dimension of observer "obs".
+The value corresponding to the the given relative frequency p in each dimension of observer "obs". p is restricted by <math>0\leq p \leq 1</math>.
 =====obs.QQuantiles(n)=====
 For each dimension of observer "obs", a vector of values corresponding to the n-th q-quantile. This vector has n+1 entries, with the minimum in the first entry, and the maximum in the last entry.

@@ Line 8: / Line 8: @@
 *Open the file <tt>qt/mkspecs/win32-msvc2008/qmake.conf</tt> in a text editor. <!--Add <tt>-Fd$(DESTDIR)$(QMAKE_TARGET).pdb</tt> as a compiler option to  <tt>QMAKE_CFLAGS_DEBUG</tt>.--> In <tt>QMAKE_CFLAGS_RELEASE</tt> and <tt>QMAKE_CFLAGS_DEBUG</tt>, replace the <tt>-MD</tt> and <tt>-MDd</tt> with <tt>-MT</tt> and  <tt>-MTd</tt>, respectively.
 <!--*To optimize for size rather than speed, replace the <tt>-O2</tt> option in <tt>QMAKE_CFLAGS_RELEASE</tt> with <tt>-O1</tt>.-->
 *Open the VS2008 console window from the start menu, and from the Qt installation's <tt>qt</tt> directory, run <tt>configure</tt> with the following options:
   -platform win32-msvc2008

@@ Line 51: / Line 51: @@
     ~TachyonADC();
     void Preflight( const SignalProperties&, SignalProperties& ) const;
     void Initialize( const SignalProperties&, const SignalProperties& );
@@ Line 57: / Line 59: @@
   private:
-    int  mSourceCh,
+   void* mHandle;
          mSampleBlockSize,
          mSamplingRate;

@@ Line 35: / Line 35: @@
 For successful filter instantiation at runtime, the strings must also be valid [[Technical Reference:Parameter Definition|parameter]] and [[Technical Reference:State Definition|state definitions]].
-'''NOTE:''' Traditionally, parameters and states have been published from inside a filter's constructor. For more flexibility, a separate <code>Publish()</code> function has been introduced. For backward compatibility, parameters and states may still be published from the constructor, but this is deprecated for newer code.
+'''NOTE:''' Traditionally, parameters and states have been published from inside a filter's constructor. For more flexibility, a separate <code>Publish()</code> function has been introduced. For backward compatibility, parameters and states may still be published from the constructor, but this is deprecated for new code.
 ===Preflight===
@@ Line 81: / Line 81: @@
 override their default implementation with your own version,
 depending on what your filter needs to do:
 ===StartRun===

@@ Line 32: / Line 32: @@
 *Inside the <tt>qt-x.y.z</tt> directory, create a subdirectory <tt>win32-msvc2008</tt>.
 *Copy the following files from <tt>qt/bin</tt> to <tt>qt-x.y.z/win32-msvc2008/bin</tt>:
   moc.exe
   qmake.exe
@@ Line 82: / Line 83: @@
 *Otherwise, run <tt>mingw32-make</tt> from the <tt>qt/src</tt> directory.
 *When the build is finished, copy the following files from <tt>qt/bin</tt> to <tt>qt-x.y.z/win32-g++/bin</tt>:
   moc.exe
   qmake.exe
@@ Line 95: / Line 97: @@
   libQtOpenGL.a
 *From <tt>qt/mkspecs</tt>, copy the file <tt>qconfig.pri</tt>, and recursively copy the contents of directories <tt>features</tt>, <tt>common</tt>, and <tt>win32-g++</tt> to <tt>qt-x.y.z/win32-g++/mkspecs</tt>.
 ==Prepare Qt include files for external use==
 *Most header files point to header files in the <tt>qt/src</tt> header files. We don't want to provide the entire <tt>qt/src</tt> directory, so we need to replace these header files with the content of the files they point to. There is a <tt>fixheader</tt> tool provided in the BCI2000 source tree at <tt>build/buildutils/fixheader.cpp</tt>. Under cygwin, execute
-  make fixheader
+  g++ fixheader.cpp -o fixheader
 from that directory to build the executable. Then, cd to the <tt>qt/include/Qt</tt> directory of your Qt installation, and execute
   for i in `find *.h`; do /full/path/to/fixheader $i; done
@@ Line 104: / Line 121: @@
 *Copy the contents of the directory <tt>qt/include/Qt</tt> into <tt>qt-x.y.z/include/Qt</tt>, omitting the <tt>private</tt> directory.
 *Likewise, copy the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt> include directories to <tt>qt-x.y.z/include</tt>, omitting the respective <tt>private</tt> directories.
 ==Upload Qt to the BCI2000 server==
-*Create a self-extracting 7z archive from each subfolder of the <tt>qt-x.y.z</tt> directory. In order to expand correctly, the archive must contain the <tt>qt-x.y.z</tt> directory as well. For CMake to find an archive on the server, it must be located at the following http path: <tt>/externals/qt/qt-x.y.z.subdirname</tt>
+*Create a self-extracting 7z archive from each subfolder of the <tt>qt-x.y.z</tt> directory. In order to expand correctly, the archive must contain the <tt>qt-x.y.z</tt> directory as well.
 Note that archives may not have an <tt>.exe</tt> file extension on the server. It will be added when the file is downloaded by CMake (see <tt>BCI2000/build/cmake/FindQt.cmake</tt> for details).

← Older revision		Revision as of 16:18, 11 June 2013
Line 1:		Line 1:
		+	'''NOTE:''' This page is outdated, and only retained as a reference. Building BCI2000 for 64-bit target does no longer require the manual steps described here.
		+
	This information applies if you intend to build 64-bit executables. Alternatively, you may build 32-bit executables and run them on 64-bit platforms as well. In oder to build BCI2000 for the Win64 target, you will need to manually perform a number of steps.		This information applies if you intend to build 64-bit executables. Alternatively, you may build 32-bit executables and run them on 64-bit platforms as well. In oder to build BCI2000 for the Win64 target, you will need to manually perform a number of steps.
	==Install Qt for x64==		==Install Qt for x64==

@@ Line 1: / Line 1: @@
 == Introduction ==
-Previous versions of BCI2000 (2.x and earlier) were dependent on the visual components library (VCL) by Borland and could only be built using the Borland compiler.  For version 3.0, we made BCI2000 compiler-independent, and therefore had to choose a portable replacement for VCL.  Qt was chosen to replace VCL because it is not only compiler-independent, but also platform-independent; a future goal for BCI2000.
+Previous versions of BCI2000 (2.x and earlier) were dependent on the visual components library (VCL) by Borland and could only be built using the Borland compiler.  For version 3.0, we made BCI2000 compiler-independent, and therefore had to choose a portable replacement for VCL.  Qt was chosen to replace VCL because it is not only compiler-independent, but also platform-independent.
-−
-As such, Qt is required for compiling the BCI2000 source on a non-Borland platform.  If Borland is still being used as the build environment, VCL is still temporarily supported and the project will be built using the VCL for its graphical elements.  For Visual Studio or MinGW builds of BCI2000, a stripped-down version of the Qt SDK is provided in the BCI2000 source tree.
-−
-To support such a large number of platforms and compilers, BCI2000 is using CMake http://www.cmake.org to generate Makefiles, project files, and Visual Studio solutions.  CMake can be thought of as a meta-makefile; it examines your build environment and sets up a Visual Studio project, a Code::Blocks project, or a Unix Makefile which is custom tailored to your environment.  Due to the wide variation in possible build environments, BCI2000 can not come with a fixed Visual Studio solution file, or a fixed Eclipse project file (such fixed solutions would always end up costing users a lot of effort).  Once remaining dependencies on the Win32 API are removed, the number of platforms BCI2000 supports will only be limited by the number of platforms and compilers for which CMake has generators.
 <!--
 == Dependencies ==
@@ Line 17: / Line 12: @@
 *'''Supported Operating Systems'''
-**Windows XP, Windows 2000 (Vista and Windows 7 have poor Audio Video latencies - not recommended for BCI2000)
+**Windows XP, Windows 2000, Windows 7 (Vista not recommended)
-**64-bit Windows systems--[[Programming Reference:Building BCI2000 for Win64|please read this information]]
+**64-bit Windows systems
 **Macintosh OSX: Compiles and passes standard tests on 10.5 and newer systems
-**Linux: Compiles and passes standard tests on both Debian Squeeze (stable) and Wheezy (currently unstable)
+**Linux: Compiles and passes standard tests on Wheezy (currently stable)
 *'''Supported Compilers'''
 **Visual Studio 9 (2008) and 10, download free Express version from [http://www.microsoft.com/express/downloads/ here] (although some BCI2000 modules require MFC, most modules may be built using the Express version)
 **MinGW with gcc 4.x
 *'''Supported IDEs'''
-**Visual Studio 9 (2008), Visual Studio 10 (via CMake)
+**Qt Creator
-**Code::Blocks - MinGW Makefiles (via CMake)
+**Visual Studio 9 (2008), Visual Studio 10
 **Other IDEs supported by CMake generators (Eclipse CDT, ...), as long as these use the compilers listed above
 == Setting up MinGW to build BCI2000 ==
@@ Line 73: / Line 67: @@
 == Building against a Qt distribution outside the BCI2000 source tree ==
-BCI2000 may be built against a standard Qt distribution rather than the stripped-down, precompiled version of Qt coming with the BCI2000 source code. Depending on your compiler and desired configuration (e.g., when using Visual Studio), you might need to re-build that distribution from source before building BCI2000.
+BCI2000 comes with a stripped-down, precompiled version of Qt, which is downloaded by CMake at configuration time. This is a static version of the Qt libraries, and allows to distribute the resulting executable without hindsight to DLL dependencies. The complex and annoying implications of such dependencies has been termed "DLL hell" for good reasons, so we strongly recommend linking against the BCI2000-specific Qt libraries for Windows builds.
-To enable the BCI2000 build system to use the external Qt distribution, open the file <tt>BCI2000/build/cmake/FindQt.cmake</tt>
+When running CMake, it determines the current compiler/OS combination, and tries to download an appropriate version of the BCI2000-specific Qt build. If no such build is available, it expects a local Qt installation to be available, and fails with an error message if this is not the case.
-in a text editor.
-There, in line 10, replace
+If a BCI2000-specific Qt build is available for the current configuration, you will still have the option of using a locally installed version of Qt. This is a CMake option <tt>USE_EXTERNAL_QT</tt> appearing in the <tt>CMakeCache.txt</tt> file after CMake has been run for the first time. Such options may be changed using the CMake GUI, or a text editor. After changing the option, run CMake again to apply the change to the created project files.
- SET( USE_STD_QT FALSE )
 with
- SET( USE_STD_QT TRUE )
-Then, go to the directory <tt>BCI2000/build</tt> and remove the file <tt>CMakeCache.txt</tt> before re-creating project files using the appropriate batch file in <tt>BCI2000/build</tt>.
 == How To Test ==
@@ Line 105: / Line 95: @@
 == Conclusions ==
-Now that BCI2000 is open to other compilers - and soon - other platforms, support may not exist for every possible compiler/platform available. Certain compilers do not optimize code as well as others, and this behavior may lead to poor system latencies during BCI2000 experiments. The supported compilers have been rigorously tested and confirmed to be adequate for compiling the BCI2000 sources.  If you wish to use a different compiler,
+Now that BCI2000 is open to a number of platforms, and compilers, support may not exist for every possible compiler/platform available. Certain compilers do not optimize code as well as others, and this behavior may lead to poor system latencies during BCI2000 experiments. The supported compilers have been rigorously tested and confirmed to be adequate for compiling the BCI2000 sources.  If you wish to use a different compiler,
 be sure to run tools/BCI2000Certification in order to confirm your setup.  CMake is a powerful tool, but in the end, ability to compile the sources is completely up to the IDE/compiler choice.  If your IDE/compiler choice is not listed above, it is strongly urged that you to consider using one which is supported.  If you run into problems using an unsupported IDE/compiler combination, you can try to find help at the BBS - http://www.bci2000.org/phpbb/index.php.  BCI2000 should compile as effortlessly as possible on supported platforms.
@@ Line 116: / Line 106: @@
 |MSVC2008||Win XP SP3||1||static
 |-
-|MSVC2008||Win 7 64bit||1||dynamic
+|MSVC2008||Win 7 32bit||1||static
 |-
 |MSVC2010||Win XP SP3||1||static
@@ Line 125: / Line 117: @@
 |-
 |MinGW > 4||Win XP SP3||1||dynamic
 |}
 ==Status on other OSes==
@@ Line 142: / Line 130: @@
 ==See also==
-[[Programming Reference:Building Qt for BCI2000]], [[Programming Reference:Building BCI2000 for Win64]]
+[[Programming Reference:Building Qt for BCI2000]]
 [[Category:Framework API]][[Category:Development]]

@@ Line 20: / Line 20: @@
 ==Win64 Support==
-Currently, the BCI2000 binary distribution is 32-bit only. It is possible to run these 32-bit executables on 64-bit Windows systems as well. In addition, BCI2000 may be compiled into native 64-bit executables from its source code as described [[Programming_Reference:Building_BCI2000_for_Win64|on this page]].
+Currently, the BCI2000 binary distribution is 32-bit only. It is possible to run these 32-bit executables on 64-bit Windows systems as well. In addition, BCI2000 may be compiled into native 64-bit executables from its source code as described [[Programming Howto:Building BCI2000|on this page]].
 ==Non-Windows Operating Systems==
 BCI2000 runs on both Linux and OS X systems. However, there is no binary distribution for those systems, so it will be necessary to compile BCI2000 before using it (instructions may be found [[Programming_Howto:Quickstart_Guide|here]]).

@@ Line 18: / Line 18: @@
   -fast
   -qt-zlib
   -qt-libpng
   -qt-libmng
@@ Line 42: / Line 41: @@
 After successful execution, you will have a Visual Studio solution file ready to compile BCI2000.
-==Limitations==
+==Notes==
-*You cannot build BCI2000 modules that depend on 32-bit libraries, as do most source modules. Consider building 32-bit executables instead--these will run fine on Win64.
-*Note that the g.USBamp source module comes with a 64-bit library, so it is supported natively on Win64.
 *You cannot build x64 targets using Visual C++ 2008 Express Edition except after considerable [http://wiki.blender.org/index.php/Dev:2.5/Doc/Building_Blender/Windows/Visual_C%2B%2B_2008_Express unsupported modifications].

@@ Line 25: / Line 25: @@
   -no-style-motif
   -no-style-cde
-For convenience, the same options on a single line:
+As a full command line:
-  -platform win32-msvc2008 -static -no-sql-sqlite -no-qt3support -fast -qt-zlib -qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
+  configure -platform win32-msvc2008 -static -no-sql-sqlite -no-qt3support -fast -qt-zlib -qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
 *When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
@@ Line 37: / Line 37: @@
   uic.exe
 Make sure to leave the <tt>qt.conf</tt> file unaffected.
-*From <tt>qt/lib</tt>, copy the following files to <tt>BCI2000/src/extlib/qt/msvc/lib</tt>:
+*From <tt>qt/lib</tt>, copy the following files to <tt>qt-x.y.z/win32-msvc2008/lib</tt>:
   QtCore.lib
   QtCored.lib
@@ Line 44: / Line 44: @@
   QtOpenGL.lib
   QtOpenGLd.lib
 *From <tt>qt/mkspecs</tt>, copy the file <tt>qconfig.pri</tt>, and recursively copy the contents of the <tt>features</tt> and the <tt>win32-msvc2008</tt> directories to <tt>qt-x.y.z/win32-msvc2008/mkspecs</tt>.
 <!--*In <tt>qt-x.y.z/win32-msvc2008/mkspecs/win32-msvc2008/qmake.conf</tt>, remove the <tt>-Fd$(DESTDIR)$(QMAKE_TARGET).pdb</tt> compiler option from <tt>QMAKE_CFLAGS_DEBUG</tt>.-->
 *Repeat the entire process with MSVC2010, with results going into a <tt>win32-msvc2010</tt> directory rather than the <tt>win32-msvc2008</tt> directory.
 <!--
 ===Note: Why do we need debug libraries?===
@@ Line 74: / Line 73: @@
   -no-style-motif
   -no-style-cde
-For copy-and-paste, the same options on a single line:
+The full command line is:
   configure -platform win32-g++ -static -no-sql-sqlite -no-qt3support -fast -qt-zlib-qt-libpng -qt-libmng -no-libtiff -no-libjpeg -no-phonon -no-webkit -no-scripttools -no-style-plastique -no-style-motif -no-style-cde
 *When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
@@ Line 97: / Line 96: @@
 *From <tt>qt/mkspecs</tt>, copy the file <tt>qconfig.pri</tt>, and recursively copy the contents of directories <tt>features</tt>, <tt>common</tt>, and <tt>win32-g++</tt> to <tt>qt-x.y.z/win32-g++/mkspecs</tt>.
-==Copy Qt include files to the BCI2000 directory==
+==Prepare Qt include files for external use==
 *Most header files point to header files in the <tt>qt/src</tt> header files. We don't want to provide the entire <tt>qt/src</tt> directory, so we need to replace these header files with the content of the files they point to. There is a <tt>fixheader</tt> tool provided in the BCI2000 source tree at <tt>build/buildutils/fixheader.cpp</tt>. Under cygwin, execute
   make fixheader
 from that directory to build the executable. Then, cd to the <tt>qt/include/Qt</tt> directory of your Qt installation, and execute
   for i in `find *.h`; do /full/path/to/fixheader $i; done
-Repeat this step for the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt>, and <tt>QtScript</tt> include directories.
+Repeat this step for the <tt>QtCore</tt>, <tt>QtGui</tt>, and <tt>QtOpenGL</tt> include directories.
-*Copy the contents of the directory <tt>qt/include/Qt</tt> into <tt>BCI2000/src/extlib/qt/include/Qt</tt>, omitting the <tt>private</tt> directory.
+*Copy the contents of the directory <tt>qt/include/Qt</tt> into <tt>qt-x.y.z/include/Qt</tt>, omitting the <tt>private</tt> directory.
-*Likewise, copy the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt>, <tt>QtScript</tt> include directories to <tt>BCI2000/src/extlib/qt/include</tt>, omitting the respective <tt>private</tt> directories.
+*Likewise, copy the <tt>QtCore</tt>, <tt>QtGui</tt>, <tt>QtOpenGL</tt> include directories to <tt>qt-x.y.z/include</tt>, omitting the respective <tt>private</tt> directories.
 ==See also==