Compiling wxWidgets (MSW) 2.8.12 on Windows using makefile.gcc - Revision history

Mgimenez: Mention Direct2D and newer wxWidgets versions.

2023-11-16T15:30:07Z

Mention Direct2D and newer wxWidgets versions.

Stahta01: /* Errors while building wxWidgets */

2016-12-14T01:11:16Z

Errors while building wxWidgets

Stahta01: /* Errors while building wxWidgets */

2016-12-14T01:05:28Z

Errors while building wxWidgets

Stahta01 at 01:02, 14 December 2016

2016-12-14T01:02:37Z

Stahta01: /* Building wxWidgets */

2016-12-14T01:01:49Z

Building wxWidgets

Stahta01 at 01:01, 14 December 2016

2016-12-14T01:01:08Z

Stahta01: /* Installing the wxWidgets Source Code */

2016-12-13T20:36:41Z

Installing the wxWidgets Source Code

Stahta01: /* Building wxWidgets */

2016-12-13T17:36:40Z

Building wxWidgets

Stahta01: /* Installing the wxWidgets Source Code */

2016-12-13T17:32:04Z

Installing the wxWidgets Source Code

Stahta01: Started directions based on 2.8.6 directions; still need to update them.

2016-12-13T17:29:45Z

Started directions based on 2.8.6 directions; still need to update them.

New page

THESE DIRECTIONS ARE STILL BEING WRITTEN; PLEASE WAIT TO USE THEM.

These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.

== Installing MinGW ==
Directions to install MinGW for Code::Blocks can be found here.
[[MinGW installation]]

== Installing the wxWidgets Source Code ==
The wxWidgets 2.8.12 distribution can be found at the [http://www.wxwidgets.org/downloads/#previous_stable wxWidgets download site]. (Note that there is also a winhelp file available.) You can choose between an installer and a zip file. You can just get the zip file because the installer is also a zipped version.

If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.

The future patches for wxWidgets 2.8.12 distribution will be found at the
[http://www.wxwidgets.org/downloads/patch.htm wxWidgets download site].

'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.8.6-1\wxWidgets-2.8.6").

'''NOTE:''' You do not need MSYS. Furthermore, you cannot have MSYS in your path, or the wxWidgets compilation will fail. Thus, if you have MSYS installed, ensure that ''<MSYS>\bin'' '''is not''' in your path before compiling wxWidgets. wxWidgets must be compiled from a "regular" command line (like cmd.exe), not from a Unix-like shell. The same problem could arise if Cygwin is in the path.

'''NOTE:''' For the remainder of these instructions we call the MinGW directory ''<MINGW>''. You have to change it to your corresponding directory (e.g. "C:\MinGW").

== Checking make Version ==
If you didn't install MinGW yourself you have to ensure you are using a recent enough version of the make utility. Open a command prompt and type:
<tt>cd /D <MINGW>\bin
mingw32-make -v</tt>
The version should read 3.80 or higher.

'''NOTE:''' the <code>/D</code> flag after <code>cd</code> may be omitted from all commands; it simply allows command prompt to change drives if necessary.

== Building wxWidgets ==
To compile wxWidgets, open the command prompt window and change to the wxWidgets directory:
<tt>cd /D <WXWIN>\build\msw</tt>

<tt>SET PATH=<MINGW>\bin;<MINGW>\mingw32\bin</tt>
'''NOTE:''' This is normally SET PATH=C:\MingGW\bin;C:\MingGW\mingw32\bin

Now clean up the source:
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release clean
'''NOTE:''' Make sure you use exactly the same options for this step and for the build step below. The clean target uses these variables and only cleans the specified version of the generated object and library files. (It will not clean the intended files if these variables are not identical.)

'''NOTE:''' If you still have problems with compiling after cleaning, you could try to manually remove the gcc_msw directory under the build\msw directory. This directory is the place where the object files are stored.

When everything is clean you can start compiling wxWidgets:
mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release

'''NOTE:''' These options are the officially-supported Code::Blocks options. If you want another version of wxWidgets (debug or non-Unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for linking Code::Blocks.

Patience. This step takes time. Make sure there was no compilation error before you continue.

'''NOTE:''' If you're having errors because of libjpeg, you might want to look at [http://sourceforge.net/tracker/?func=detail&atid=309863&aid=1606032&group_id=9863 this patch]

@@ Line 45: / Line 45: @@
 == Errors while building wxWidgets ==
-Navigate to the folder build/msw inside either wxWidgets directory. In this folder is a text file named config.gcc which you can edit with notepad to control the build options. There are two lines to note, CFLAGS ?= and CXXFLAGS ?=. The options given here will go in either or both of those lines.
+Navigate to the folder build/msw inside wxWidgets directory. In this folder is a text file named config.gcc which you can edit with notepad to control the build options. There are two lines to note, CFLAGS ?= and CXXFLAGS ?=. The options given here will go in either or both of those lines.
 If your linker runs out of memory while building use:

← Older revision		Revision as of 01:05, 14 December 2016
Line 45:		Line 45:

	== Errors while building wxWidgets ==		== Errors while building wxWidgets ==
		+	Navigate to the folder build/msw inside either wxWidgets directory. In this folder is a text file named config.gcc which you can edit with notepad to control the build options. There are two lines to note, CFLAGS ?= and CXXFLAGS ?=. The options given here will go in either or both of those lines.
		+
		+	If your linker runs out of memory while building use:
		+
		+	-fno-keep-inline-dllexport
		+
		+	If your compiler errors out, usually referencing monotree.dll or similar:
		+
		+	-D_WIN32_IE=0x0603
		+
		+	To silence warnings that can significantly slow down the compilation process:
		+
		+	-Wno-unused-local-typedefs
		+
		+	and
		+
		+	-Wno-deprecated-declarations
		+
		+	All of these options apply to both <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> so the two lines containing all the options would look like this:
		+
		+	CFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations
		+
		+	CXXFLAGS ?= -fno-keep-inline-dllexport -D_WIN32_IE=0x0603 -Wno-unused-local-typedefs -Wno-deprecated-declarations

← Older revision		Revision as of 01:02, 14 December 2016
Line 43:		Line 43:

	Patience. This step takes time. Make sure there was no compilation error before you continue.		Patience. This step takes time. Make sure there was no compilation error before you continue.
		+
		+	== Errors while building wxWidgets ==

← Older revision		Revision as of 01:01, 14 December 2016
Line 1:		Line 1:
−	~~THESE DIRECTIONS ARE STILL BEING WRITTEN; PLEASE WAIT TO USE THEM.~~
−
	These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.		These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.

← Older revision		Revision as of 17:36, 13 December 2016
Line 45:		Line 45:

	Patience. This step takes time. Make sure there was no compilation error before you continue.		Patience. This step takes time. Make sure there was no compilation error before you continue.
−
−	~~'''NOTE:''' If you're having errors because of libjpeg, you might want to look at [http://sourceforge.net/tracker/?func=detail&atid=309863&aid=1606032&group_id=9863 this patch]~~

@@ Line 1: / Line 1: @@
 These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.
 == Installing MinGW ==
@@ Line 15: / Line 17: @@
 '''NOTE:''' For the remainder of these instructions we call the MinGW directory ''<MINGW>''. You have to change it to your corresponding directory (e.g. "C:\MinGW").
 == Checking make Version ==

@@ Line 40: / Line 40: @@
   mingw32-make -f makefile.gcc  MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=release
-'''NOTE:''' These options are the officially-supported Code::Blocks options. If you want another version of wxWidgets (debug or non-Unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for linking Code::Blocks.
+'''NOTE:''' These options are the officially-supported Code::Blocks options. If you want another version of wxWidgets (debug or non-Unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for building Code::Blocks.
 Patience. This step takes time. Make sure there was no compilation error before you continue.

@@ Line 12: / Line 12: @@
 If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.
-'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.8.6-1\wxWidgets-2.8.6").
+'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "C:\wxMSW-2.8.12\wxMSW-2.8.12" or "C:\wxWidgets-2.8.12\wxWidgets-2.8.12").
 '''NOTE:''' You do not need MSYS. Furthermore, you cannot have MSYS in your path, or the wxWidgets compilation will fail. Thus, if you have MSYS installed, ensure that ''<MSYS>\bin'' '''is not''' in your path before compiling wxWidgets. wxWidgets must be compiled from a "regular" command line (like cmd.exe), not from a Unix-like shell. The same problem could arise if Cygwin is in the path.

← Older revision		Revision as of 17:32, 13 December 2016
Line 11:		Line 11:

	If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.		If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.
−
−	~~The future patches for wxWidgets 2.8.12 distribution will be found at the~~
−	~~[http://www.wxwidgets.org/downloads/patch.htm wxWidgets download site].~~

	'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.8.6-1\wxWidgets-2.8.6").		'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.8.6-1\wxWidgets-2.8.6").