WxWindowsQuickRef - Revision history

Mloutris: Added comment to indicate where the resulting DLLs can be found.

2021-03-17T18:26:59Z

Added comment to indicate where the resulting DLLs can be found.

← Older revision		Revision as of 18:26, 17 March 2021
Line 36:		Line 36:
	* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.		* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.
	* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".		* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".
			* If the build is successful, gcc dlls will be placed at ../lib/gcc_dll/wxmsw<version>_gcc_custom.dll

	The "CXXFLAGS=-fno-keep-inline-dllexport" option is necessary with recent versions of GCC (not with MSVC), to prevent problems with memory usage when performing the final link step on the monolithic DLL.		The "CXXFLAGS=-fno-keep-inline-dllexport" option is necessary with recent versions of GCC (not with MSVC), to prevent problems with memory usage when performing the final link step on the monolithic DLL.

LETARTARE: 12.11 -> 17.12

2018-03-23T18:33:22Z

12.11 -> 17.12

← Older revision		Revision as of 18:33, 23 March 2018
Line 7:		Line 7:

	'''Important Requirements:'''		'''Important Requirements:'''
	* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 12~~.11~~ release] or [/index.php/board,20.0.html a recent nightly build].		* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 17.12 release] or [/index.php/board,20.0.html a recent nightly build].

	* '''Windows compiler''' - You need to have correctly installed either		* '''Windows compiler''' - You need to have correctly installed either

LETARTARE: /* Frequently Asked Questions */

2013-10-14T08:24:32Z

Frequently Asked Questions

← Older revision		Revision as of 08:24, 14 October 2013
Line 93:		Line 93:
	'''I get errors like "wx/setup.h: No such file or directory"'''		'''I get errors like "wx/setup.h: No such file or directory"'''

	You're missing an important compiler search path in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, then open your project's build options and add "$(#wx.lib)\gcc_dll\mswu" (assuming a <u>monolithic Unicode DLL</u> build) to the compiler search paths.		You're missing an important compiler search path in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, then open your project's build options and add "$(#wx.lib)\gcc_dll\mswu" (assuming a <u>monolithic Unicode DLL</u> build) or "$(#wx.lib)\gcc_lib\mswu" (assuming a <u>multilib Unicode </u> build)to the compiler search paths.

	'''I get errors like "cannot find -lwxmsw28u"'''		'''I get errors like "cannot find -lwxmsw28u"'''

LETARTARE: /* MONOLITHIC add 'u'*/

2013-10-14T06:20:48Z

MONOLITHIC add 'u'

← Older revision		Revision as of 06:20, 14 October 2013
Line 77:		Line 77:
	=== MONOLITHIC ===		=== MONOLITHIC ===
	MONOLITHIC controls whether a single library (MONOLITHIC=1) or multiple component libraries (MONOLITHIC=0) are built. With a monolithic build, project setup and development are much easier, and you only have one DLL to distribute if you're using a DLL build. With a non-monolithic (multilib) build, several different libraries are built and you can avoid linking with the entire wxWidgets codebase for programs that don't need it. You do have to ensure that you choose the correct component libraries.		MONOLITHIC controls whether a single library (MONOLITHIC=1) or multiple component libraries (MONOLITHIC=0) are built. With a monolithic build, project setup and development are much easier, and you only have one DLL to distribute if you're using a DLL build. With a non-monolithic (multilib) build, several different libraries are built and you can avoid linking with the entire wxWidgets codebase for programs that don't need it. You do have to ensure that you choose the correct component libraries.
	* A '''monolithic''' build of wxWidgets creates a single wxWidgets import library (such as ~~libwxmsw28~~.a) and a single DLL (such as wxmsw28_gcc_custom.dll).		* A '''monolithic''' build of wxWidgets creates a single wxWidgets import library (such as libwxmsw28u.a) and a single DLL (such as wxmsw28_gcc_custom.dll).
	* A '''multilib''' build of wxWidgets creates multiple import libraries (~~libwx28_base~~.a, etc.) and multiple DLLs.		* A '''multilib''' build of wxWidgets creates multiple import libraries (libwxbase28u.a, etc.) and multiple DLLs.
	* Additional '''static''' libraries are always created with any wxWidgets build (libwxexpat.a, libwxjpeg.a, etc.). These libraries do not normally need to be used with DLL builds of wxWidgets, but they are required when using static builds.		* Additional '''static''' libraries are always created with any wxWidgets build (libwxexpat.a, libwxjpeg.a, etc.). These libraries do not normally need to be used with DLL builds of wxWidgets, but they are required when using static builds.

WardXmodem: When steps followed, newer releases add a step, seeking doc on that

2013-05-11T03:45:09Z

When steps followed, newer releases add a step, seeking doc on that

← Older revision		Revision as of 03:45, 11 May 2013
Line 49:		Line 49:
	# Set your project title and location.		# Set your project title and location.
	# Enter author details if you wish (not required).		# Enter author details if you wish (not required).
			# ''At this point wiki member WardXmodem's gives a "select your GUI options" - can someone detail their meanings?''
	# Select options for automatic code and file generation.		# Select options for automatic code and file generation.
	# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.		# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.
Line 54:		Line 55:
	# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings". The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.		# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings". The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.
	# Select additional libraries if required. You should not need to select any of these for normal usage.		# Select additional libraries if required. You should not need to select any of these for normal usage.


	== Build and Run ==		== Build and Run ==

TDragon: Condense unnecessary introductory info; remove wxPack as it uses outdated GCC; update links to external components including wxWidgets

2013-01-30T00:53:51Z

Condense unnecessary introductory info; remove wxPack as it uses outdated GCC; update links to external components including wxWidgets

← Older revision		Revision as of 00:53, 30 January 2013
Line 7:		Line 7:

	'''Important Requirements:'''		'''Important Requirements:'''
	* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 10.05 release] or [/index.php/board,20.0.html a recent nightly build].		* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 12.11 release] or [/index.php/board,20.0.html a recent nightly build].

	~~<!-- Troyf, please see the Discussion page for this article for some objections to your changes here. -->~~		* '''Windows compiler''' - You need to have correctly installed either
	* '''Windows compiler''' - You need to have correctly installed ~~one of three options~~		**the [http://www.mingw.org/ MinGW/GCC] free compiler (or one of its forks), or
	**[http://www.mingw.org/ MinGW/GCC] free compiler~~, gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages are required~~, or		**[http://msdn.microsoft.com/vstudio/ Microsoft Visual C++] (the [http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products Express editions] are free, but you must also install the [http://www.microsoft.com/en-us/download/details.aspx?id=8279 Platform SDK]).
	**[http://msdn.microsoft.com/vstudio/ Microsoft~~'s compilers~~] (the [http://~~msdn~~.microsoft.com/~~vstudio~~/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/~~downloads~~/details.aspx?~~familyid~~=~~0baf2b35-c656-4969-ace8-e4c0c0716adb~~ Platform SDK])~~, or~~		When downloading an official Code::Blocks release, you have the option of downloading a bundle package that includes a full MinGW/GCC toolchain.
	**[https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW~~-bundled compiler which includes all necessary packages~~

	* '''Path properly defined.'''		* '''Path properly defined''' - Ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin, or C:\MinGW32\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable].
	** Ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable]~~. The path environment variable is changed by~~
	***right-clicking on 'my computer',
	***selecting properties,
	***click the advanced tab,
	***click the 'Environment Variables' button at the bottom.

	To verify the path is set correctly, open a DOS prompt and enter the command: mingw32-gcc, a reply of 'Not recognized' indicates a problem. 'no input files' means that the program was found and that the path environment variable is correct. For example...

	~~Microsoft Windows XP [Version 5.1.2600]~~		== Download wxWidgets Source Code ==
	~~(C) Copyright 1985-2001 Microsoft Corp~~.		wxWidgets is distributed in source code format, and you need to compile it into a library before you can use it in your own programs.
	~~C:\>mingw32-gcc~~
	~~mingw32-gcc: no input files~~
	~~C:\>~~

	~~== Download~~ wxWidgets ==		The current recommended version of wxWidgets to use is '''2.8.12'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.12-Setup.exe Click here to download the wxWidgets 2.8.12 sources for Windows] (wxMSW-2.8.12-Setup.exe; 12.2 MB). You can check [http://www.wxwidgets.org/downloads/ the wxWidgets download page] to see if a newer stable version is available. '''It is highly recommended that you install the sources to a path without spaces.''' You should choose a volume with at least 300 MB of free space.
	You can ~~choose to download~~ the wxWidgets ~~source code and compile it yourself, or~~ download ~~the "wxPack",~~ a ~~precompiled~~ version.
	* '''~~The wxWidgets~~ sources~~''' are~~ a ~~much smaller download, but you must also spend some time compiling them~~.
	* '''~~wxPack''' is~~ a ~~much larger download, but you don't have to spend time compiling it or worry about build options~~.

	~~=== wxWidgets Sources ===~~		'' '''wxPack''' is no longer recommended for use, as it is built with a much older version of GCC.''
	~~The current recommended version of wxWidgets to use is~~ '''~~2.8.10~~'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.10-Setup.exe Click here to download the wxWidgets 2.8.10 sources for Windows] (wxMSW-2.8.10-Setup.exe; 12.2 MB). You can check [http://www.wxwidgets.org/downloads/ the wxWidgets download page] to see if a newer stable version is available. ''~~'It~~ is ~~highly~~ recommended ~~that you install the sources to~~ a ~~path without spaces~~.''~~' You should choose a volume with at least 300 MB of free space.~~

	~~=== wxPack ===~~
	wxPack makes the next step of building wxWidgets unnecessary. The current stable release of wxPack is '''v2.8.8.04''', based on wxWidgets 2.8.8. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.8.04.exe?download Click here to download wxPack v2.8.8.04] (wxPack_v2.8.8.04.exe, 315.9 MB). You can check [http://wxpack.sourceforge.net/Main/Downloads the wxPack download page] to see if a newer stable version is available. '''It is highly recommended that you install wxPack in a path without spaces.''' You should choose a volume with at least 700 MB of free space for MSVC, or 2.2 GB of free space for MinGW/GCC.

	== Build wxWidgets ==		== Build wxWidgets ==
	~~''This step is unnecessary if you are using '''wxPack''' ''~~

	* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.		* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
	* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.9):		* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.12):
	cd /D <wxWidgets>\build\msw		cd /D <wxWidgets>\build\msw
	''Note: the <code>/D</code> flag after <code>cd</code> may be omitted from the command; it simply allows command prompt to change drives if necessary.		''Note: the <code>/D</code> flag after <code>cd</code> may be omitted from the command; it simply allows command prompt to change drives if necessary.
	* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:		* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:
	mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1		mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1 CXXFLAGS=-fno-keep-inline-dllexport
	* The recommended command to use for '''MSVC''' is:		* The recommended command to use for '''MSVC''' is:
	nmake -f makefile.vc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1		nmake -f makefile.vc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1
	* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.		* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.
	* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".		* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".

			The "CXXFLAGS=-fno-keep-inline-dllexport" option is necessary with recent versions of GCC (not with MSVC), to prevent problems with memory usage when performing the final link step on the monolithic DLL.

	See the section below titled "wxWidgets build options explained" for details on the meaning of the BUILD, SHARED, MONOLITHIC, and UNICODE options. These options are critically important, because they define the basic wxWidgets development environment you will be using. You must duplicate them exactly when running Code::Blocks' wxWidgets project wizard.		See the section below titled "wxWidgets build options explained" for details on the meaning of the BUILD, SHARED, MONOLITHIC, and UNICODE options. These options are critically important, because they define the basic wxWidgets development environment you will be using. You must duplicate them exactly when running Code::Blocks' wxWidgets project wizard.


	== Create a wxWidgets project in Code::Blocks ==		== Create a wxWidgets project in Code::Blocks ==
Line 67:		Line 52:
	# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.		# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.
	# Select debug and/or release configurations for your project. The debug configuration at least is recommended.		# Select debug and/or release configurations for your project. The debug configuration at least is recommended.
	# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings"~~. '''If you are using wxPack:''' wxPack includes each version, so you may select whichever options you prefer~~. The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.		# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings". The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.
	# Select additional libraries if required. You should not need to select any of these for normal usage.		# Select additional libraries if required. You should not need to select any of these for normal usage.


	== Build and Run ==		== Build and Run ==
Line 117:		Line 103:
	wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.		wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.

	==~~External Links~~==		==See also==
	[/index.php?topic=5359.0 Newbie problem in setting up wxwidgets and Codeblocks]		Forum thread - [/index.php?topic=5359.0 Newbie problem in setting up wxwidgets and Codeblocks]

Alpha: Added "/D" flag to "cd".

2011-09-24T13:10:03Z

Added "/D" flag to "cd".

← Older revision		Revision as of 13:10, 24 September 2011
Line 46:		Line 46:
	* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.		* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
	* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.9):		* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.9):
	cd <wxWidgets>\build\msw		cd /D <wxWidgets>\build\msw
			''Note: the <code>/D</code> flag after <code>cd</code> may be omitted from the command; it simply allows command prompt to change drives if necessary.
	* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:		* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:
	mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1		mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1

Greenbreen: Added link to forum thread that helped me resolve errors

2010-12-21T05:21:54Z

Added link to forum thread that helped me resolve errors

← Older revision		Revision as of 05:21, 21 December 2010
Line 115:		Line 115:

	wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.		wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.

			==External Links==
			[/index.php?topic=5359.0 Newbie problem in setting up wxwidgets and Codeblocks]

TDragon: /* Frequently Asked Questions */ Errors for differing GCC unwind versions

2010-09-05T14:54:04Z

Frequently Asked Questions: Errors for differing GCC unwind versions

← Older revision		Revision as of 14:54, 5 September 2010
Line 111:		Line 111:

	You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.		You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.

			'''I get errors like "undefined reference to _Unwind_*"'''

			wxWidgets was built with a different version of GCC than the one you're currently using. You need to rebuild wxWidgets with the same version of GCC that you use to compile your program.

Jens at 05:24, 26 August 2010

2010-08-26T05:24:53Z

← Older revision		Revision as of 05:24, 26 August 2010
Line 7:		Line 7:

	'''Important Requirements:'''		'''Important Requirements:'''
	* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/5 the 8.02 release] or [/index.php/board,20.0.html a recent nightly build].		* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 10.05 release] or [/index.php/board,20.0.html a recent nightly build].

	<!-- Troyf, please see the Discussion page for this article for some objections to your changes here. -->		<!-- Troyf, please see the Discussion page for this article for some objections to your changes here. -->