Programming Reference:Building Qt for BCI2000 (obsolete) - Revision history

Mellinger: Mellinger moved page Programming Reference:Building Qt for BCI2000 to Programming Reference:Building Qt for BCI2000 (obsolete)

2020-07-10T18:58:39Z

Mellinger moved page Programming Reference:Building Qt for BCI2000 to Programming Reference:Building Qt for BCI2000 (obsolete)

← Older revision		Revision as of 18:58, 10 July 2020
(No difference)

Mellinger: /* Build and copy MSVC libraries and auxiliary files */

2015-08-08T19:00:39Z

Build and copy MSVC libraries and auxiliary files

← Older revision		Revision as of 19:00, 8 August 2015
Line 16:		Line 16:
	-no-openssl -no-qml-debug ^		-no-openssl -no-qml-debug ^
	-opengl desktop ^		-opengl desktop ^
	~~-no-audio-backend ^~~
	~~-no-wmf-backend ^~~
	-skip qtdeclarative ^		-skip qtdeclarative ^
	-skip qtquick1 ^		-skip qtquick1 ^
Line 25:		Line 23:
	-skip qtwebkit-examples ^		-skip qtwebkit-examples ^
	-skip qtxmlpatterns ^		-skip qtxmlpatterns ^
	~~-skip qtmultimedia ^~~
	-nomake tests ^		-nomake tests ^
	-nomake examples		-nomake examples

Mellinger: /* Build and copy MSVC libraries and auxiliary files */

2015-08-08T17:14:44Z

Build and copy MSVC libraries and auxiliary files

← Older revision		Revision as of 17:14, 8 August 2015
Line 15:		Line 15:
	-no-vcproj -mp ^		-no-vcproj -mp ^
	-no-openssl -no-qml-debug ^		-no-openssl -no-qml-debug ^
	~~-no~~-opengl ^		-opengl desktop ^
	~~-no-openvg ^~~
	~~-no-direct2d ^~~
	~~-no-angle ^~~
	~~-no-dbus~~ ^
	-no-audio-backend ^		-no-audio-backend ^
	-no-wmf-backend ^		-no-wmf-backend ^
Line 121:		Line 117:
	/full/path/to/build/buildutils/strip_msvc_lib.sh *		/full/path/to/build/buildutils/strip_msvc_lib.sh *
	-->		-->

	==Upload Qt to the BCI2000 server==		==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.		*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.

Mellinger at 17:13, 8 August 2015

2015-08-08T17:13:35Z

← Older revision		Revision as of 17:13, 8 August 2015
Line 48:		Line 48:

	*For 64-bit versions of the libraries, proceed as above, but run <tt>configure</tt> and <tt>nmake</tt> steps from a 64-bit Visual Studio command line prompt. The target directory should be named <tt>win32-amd64-msvc2012</tt> for MSVC 2012 64-bit builds.		*For 64-bit versions of the libraries, proceed as above, but run <tt>configure</tt> and <tt>nmake</tt> steps from a 64-bit Visual Studio command line prompt. The target directory should be named <tt>win32-amd64-msvc2012</tt> for MSVC 2012 64-bit builds.
			<!--
	==Build and copy mingw libraries and auxiliary files==		==Build and copy mingw libraries and auxiliary files==
	*From the Qt installation's <tt>qt</tt> directory, run <tt>configure</tt> with the following options:		*From the Qt installation's <tt>qt</tt> directory, run <tt>configure</tt> with the following options:
Line 120:		Line 120:
	*To hide debugging information, open a cygwin shell, and cd to the qt lib directory that contains MSVC libraries. There, execute		*To hide debugging information, open a cygwin shell, and cd to the qt lib directory that contains MSVC libraries. There, execute
	/full/path/to/build/buildutils/strip_msvc_lib.sh *		/full/path/to/build/buildutils/strip_msvc_lib.sh *
			-->
	==Upload Qt to the BCI2000 server==		==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.		*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.

Mellinger: /* Build and copy MSVC libraries and auxiliary files */

2015-08-08T13:53:27Z

Build and copy MSVC libraries and auxiliary files

← Older revision		Revision as of 13:53, 8 August 2015
Line 15:		Line 15:
	-no-vcproj -mp ^		-no-vcproj -mp ^
	-no-openssl -no-qml-debug ^		-no-openssl -no-qml-debug ^
	-opengl ~~desktop~~ ^		-no-opengl ^
			-no-openvg ^
			-no-direct2d ^
			-no-angle ^
			-no-dbus ^
			-no-audio-backend ^
			-no-wmf-backend ^
	-skip qtdeclarative ^		-skip qtdeclarative ^
	-skip qtquick1 ^		-skip qtquick1 ^
Line 23:		Line 29:
	-skip qtwebkit-examples ^		-skip qtwebkit-examples ^
	-skip qtxmlpatterns ^		-skip qtxmlpatterns ^
			-skip qtmultimedia ^
	-nomake tests ^		-nomake tests ^
	-nomake examples		-nomake examples

	*This should be a single command line, so make sure that the caret character is actually the last character in each line, and not followed by white space.		*This should be a single command line, so make sure that the caret character is actually the last character in each line, and not followed by white space.
Line 33:		Line 40:
	*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.		*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
	*Run <tt>nmake</tt> as suggested by <tt>configure</tt>.		*Run <tt>nmake</tt> as suggested by <tt>configure</tt>.
			*After a successful build, <tt>nmake install</tt> will copy libraries and headers to the location specified by the <tt>-prefix</tt> option.
			*The following files must be present in bin:

	*~~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>~~:
	~~idc.exe~~
	moc.exe		moc.exe
	qmake.exe		qmake.exe
	rcc.exe		rcc.exe
	uic.exe		uic.exe
	~~Make sure to leave the <tt>qt.conf</tt> file unaffected.~~
	*From <tt>qt/lib</tt>, copy the following files to <tt>qt-x.y.z/win32-msvc2008/lib</tt>:		*For 64-bit versions of the libraries, proceed as above, but run <tt>configure</tt> and <tt>nmake</tt> steps from a 64-bit Visual Studio command line prompt. The target directory should be named <tt>win32-amd64-msvc2012</tt> for MSVC 2012 64-bit builds.
	~~QtCore.lib~~
	~~QtCored.lib~~
	~~QtGui.lib~~
	~~QtGuid.lib~~
	~~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.
	*For 64-bit versions of the libraries, proceed as above, but run <tt>configure</tt> and <tt>nmake</tt> steps from a 64-bit Visual Studio command line prompt. The target directory should be named <tt>win32-amd64-~~msvc2008~~</tt> for MSVC ~~2008~~ 64-bit builds.
	~~<!--~~
	~~===Note: Why do we need debug libraries?===~~
	For the stripped-down version of Qt provided in the BCI2000 source tree, no source code is available, and debugging information in the Qt libraries cannot be used for debugging. Thus, it appears that always linking to the release version of the Qt libraries would be sufficient, saving considerable space in the SVN data base, and download time for the user. Unfortunately, it turns out that this is not sufficient, and that both debugging versions of the Qt libraries, and associated pdb files, are required in the BCI2000 source tree.
	*MSVC does not cleanly separate between compile and link stages. Rather, the compiler provides /M switches that determine the runtime libraries to be used in the linking stage.
	*Due to this dependency of object code on certain runtime libraries, it is not cleanly possible to link together static libraries compiled with one /M switch with application code compiled with another /M switch. Thus, we need to provide both release and debug versions of the Qt libraries.
	~~-->~~

	==Build and copy mingw libraries and auxiliary files==		==Build and copy mingw libraries and auxiliary files==

Mellinger: /* Build and copy MSVC libraries and auxiliary files */

2015-08-08T12:35:04Z

Build and copy MSVC libraries and auxiliary files

← Older revision		Revision as of 12:35, 8 August 2015
Line 6:		Line 6:
	*Download the Qt source code [http://qt-project.org/downloads] to your machine.		*Download the Qt source code [http://qt-project.org/downloads] to your machine.
	*Outside the Qt source tree, create a directory tree, e.g. <tt>d:\Qt\5.3\build-msvc12</tt>. A Qt build may require an enormous amount of temporary disk space (50GB and more), so it is recommended to build Qt on a separate (virtual) empty disk drive.		*Outside the Qt source tree, create a directory tree, e.g. <tt>d:\Qt\5.3\build-msvc12</tt>. A Qt build may require an enormous amount of temporary disk space (50GB and more), so it is recommended to build Qt on a separate (virtual) empty disk drive.
	*~~Within~~ the newly created empty build directory, place a <tt>do_configure.bat</tt> script file with the following content:		*Into the newly created empty build directory, place a <tt>do_configure.bat</tt> script file with the following content:

	c:\Qt\5.3\Src\configure ^		c:\Qt\5.3\Src\configure ^

Mellinger at 12:34, 8 August 2015

2015-08-08T12:34:07Z

← Older revision		Revision as of 12:34, 8 August 2015
Line 33:		Line 33:
	*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.		*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
	*Run <tt>nmake</tt> as suggested by <tt>configure</tt>.		*Run <tt>nmake</tt> as suggested by <tt>configure</tt>.



	*Inside the <tt>qt-x.y.z</tt> directory, create a subdirectory <tt>win32-msvc2008</tt>.		*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>:		*Copy the following files from <tt>qt/bin</tt> to <tt>qt-x.y.z/win32-msvc2008/bin</tt>:

Mellinger at 12:24, 8 August 2015

2015-08-08T12:24:31Z

← Older revision		Revision as of 12:24, 8 August 2015
Line 28:		Line 28:
	*This should be a single command line, so make sure that the caret character is actually the last character in each line, and not followed by white space.		*This should be a single command line, so make sure that the caret character is actually the last character in each line, and not followed by white space.
	*Note that the first path should point to your Qt source location, and the "prefix" path should point to a location on your build drive. This is the path that will contain Qt headers and libraries after the build.		*Note that the first path should point to your Qt source location, and the "prefix" path should point to a location on your build drive. This is the path that will contain Qt headers and libraries after the build.
	*In your Qt source directory, open the file <tt>qtbase/mkspecs/win32-msvc2012/qmake.conf</tt> in a text editor.		*In your Qt source directory, open the file <tt>qtbase/mkspecs/win32-msvc2012/qmake.conf</tt> in a text editor. 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.
	*Open ~~the~~ appropriate Visual Studio console window from the start menu. Whether you build a 64 or 32 bit version of Qt will depend on the type of VS Command Prompt you choose.		*Open an appropriate Visual Studio console window from the start menu. Whether you build a 64 or 32 bit version of Qt will depend on the type of VS Command Prompt you choose.
	*Change directory to the build directory containing the script described above, and execute it.		*Change directory to the build directory containing the script described above, and execute it.
	*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.		*When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.

Mellinger: /* Build and copy MSVC libraries and auxiliary files */

2015-08-08T12:22:52Z

Build and copy MSVC libraries and auxiliary files

@@ Line 6: / Line 6: @@
 *Download the Qt source code [http://qt-project.org/downloads] to your machine.
 *Outside the Qt source tree, create a directory tree, e.g. <tt>d:\Qt\5.3\build-msvc12</tt>. A Qt build may require an enormous amount of temporary disk space (50GB and more), so it is recommended to build Qt on a separate (virtual) empty disk drive.
-*Open the file <tt>qt/mkspecs/win32-msvc2008/qmake.conf</tt> in a text editor.
+*Within the newly created empty build directory, place a <tt>do_configure.bat</tt> script file with the following content:
 *When prompted for the type of license, choose "Open Source", and answer "yes" when asked whether you accept the terms of the license.
 *Run <tt>nmake</tt> as suggested by <tt>configure</tt>.

Mellinger at 12:07, 8 August 2015

2015-08-08T12:07:22Z

← Older revision		Revision as of 12:07, 8 August 2015
Line 1:		Line 1:
	This document describes how to build Qt for installation in the BCI2000 source tree. It is current as of Qt 4.~~8.4~~.		This document describes how to build Qt for installation in the BCI2000 source tree. It is current as of Qt 5.3.

	'''Note:''' Following this procedure is only required if you are a member of the BCI2000 team, and if your task is to update the Qt build coming with BCI2000. In case you just want to build BCI2000 against a version of Qt outside the source tree, run CMake a first time, then open the file <tt>BCI2000/build/CMakeCache.txt</tt> in the CMake GUI, or in a text editor, and set the value of the USE_EXTERNAL_QT option to "ON".		'''Note:''' Following this procedure is only required if you are a member of the BCI2000 team, and if your task is to update the Qt build coming with BCI2000. In case you just want to build BCI2000 against a version of Qt outside the source tree, run CMake a first time, then open the file <tt>BCI2000/build/CMakeCache.txt</tt> in the CMake GUI, or in a text editor, and set the value of the USE_EXTERNAL_QT option to "ON".
Line 5:		Line 5:
	==Build and copy MSVC libraries and auxiliary files==		==Build and copy MSVC libraries and auxiliary files==
	*Download the Qt source code [http://qt-project.org/downloads] to your machine.		*Download the Qt source code [http://qt-project.org/downloads] to your machine.
	*Outside the Qt source tree, create a directory ~~<tt>qt-x.y.z</tt>~~, e.g. <tt>qt-~~4.7.0~~</tt> ~~for version 4~~.~~7.0~~.		*Outside the Qt source tree, create a directory tree, e.g. <tt>d:\Qt\5.3\build-msvc12</tt>. A Qt build may require an enormous amount of temporary disk space (50GB and more), so it is recommended to build Qt on a separate (virtual) empty disk drive.
	*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.		*Open the file <tt>qt/mkspecs/win32-msvc2008/qmake.conf</tt> in a text editor.
	~~<!--*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 file <tt>qt/projects.pro</tt>, and put a comment sign in front of "examples demos" near the top of the file.		*Open the file <tt>qt/projects.pro</tt>, and put a comment sign in front of "examples demos" near the top of the file.
	*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:		*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: