Compiling wxWidgets 2.8.6 to develop Code::Blocks (MSW)
Note: This is an copy of Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW) http://wiki.codeblocks.org/index.php?title=Compiling_wxWidgets_2.6.2_to_develop_Code::Blocks_%28MSW%29
That is being updated for wxWidgets 2.6.3
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.
Although these instructions are targeted at the Windows operating system, it should be possible to apply them with slight adjustments to other platforms, since we make use of MinGW.
Directions to install MinGW for Code::Blocks can be found here. MinGW installation
Installing the wxWidgets source code
The wxWidgets 2.6.3 distribution can be found at the 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 patches wxWidgets 2.6.3 distribution can be found at the 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:\wxWidgets-2.6.3").
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:
cd <MINGW>\bin mingw32-make -v
The version should read 3.80 or greater, else you need to install a newer version.
Checking patch version
In order to patch the wxWidgets we need to verify that patch exists and is the correct version. Open a command prompt and type:
cd <MINGW>\bin patch -v
The version should read 2.5, if not recognized then you need to get the patch command. A way to do this is by getting UnxUtils.zip which contains patch 2.5. Unzip UnxUtils.zip to a temp folder then copy patch.exe to your <MINGW>\bin folder.
Note: The version 2.5.9 of patch from GnuWin32 seems to have a problem with unified diffs and can NOT be used to apply diffs to wxWidgets.
Ports of the most often used Unix utilities. Note that some tools in UnxUtils are quite a bit outdated, so make sure you do not overwrite already existing MinGW files with their UnxUtils counterparts.
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
NOTE: The following instructions do not work with MSYS, or other forms of Unix on Windows.
Now the first thing to do is to 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 (so it will actually 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 actually 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 against.
Now you can get a cup of coffee or do something else because this step takes some 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 this patch
Setting up paths
Before finally compiling Code::Blocks itself, you need to setup the paths:
- Open the Code::Blocks project (CodeBlocks.cbp).
- It will ask you to define a Global variable
- Set the path to where you have wxWidgets installed (e.g. "c:\wxWidgets-2.6.3").
- Compile Code::Blocks.
Post compilation steps
When the compilation process is finished, simply run the update.bat script. It will ensure that all resource files Code::Blocks uses are in the right place and up to date.
Building wxWidgets 2.6.2 using VC++ Toolkit 2003
I'll just throw in my notes on the process for both compiler versions as getting VC++ toolkit to work is quite a pain. Code::Blocks needs a couple of changes to support wxWidgets with the VC++ toolkit seamlessly.
install .NET Framework SDK Version 1.1
run PlatformSDK->Run all Windows XP 32-bit Build Environment (Retail) batch files (find them in PlatformSDK\Setup)
C:\Program Files\Microsoft Visual C++ Toolkit 2003\Vc7\bin\vcvars32.bat (not needed)
The following environment vars must be set/modified/added via 'Control Panel | System | Advanced | Environment Variables'.
set DOTNETSDK=C:\Program Files\Microsoft.NET\SDK\v1.1 (not needed)
set MSVC=C:\Program Files\Microsoft Visual C++ Toolkit 2003
set MSSDK=C:\Program Files\Microsoft Platform SDK
set VC7=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 CFG=NonUnicode clean
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 CFG=NonUnicode
cd <WXWIN>\lib; move vc_dll codeblocks_vc
project->build options directories->compiler <WXWIN>\lib\codeblocks_vc\msw <WXWIN>\include <WXWIN>\contrib\include directories->linker <WXWIN>\lib\codeblocks_vc directories->resource compiler <WXWIN>\include compiler->#defines WXUSINGDLL compiler->compiler flags enable c++ exception handling (or other options: /GX [same as /EHsc]) compiler->other options delete -D__GNUWIN32__ linker->link libraries delete ctl3d32 compile->compiler options programs->additional paths C:\wxWidgets-2.6.2\lib\codeblocks_vc -OR- copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_vc_custom.dll to application exe directory or c:\windows\system32 -OR- change project->properties->targets->execution working dir to C:\wxWidgets-2.6.2\lib\codeblocks_vc (not recommended) compile->compiler options programs->additional paths C:\Program Files\Microsoft Platform SDK\Bin directories->compiler add C:\Program Files\Microsoft Platform SDK\Include directories->linker add C:\Program Files\Microsoft Platform SDK\Lib copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26.exp to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw.exp copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26.lib to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw.lib copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_stc.exp to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw_stc.exp copy C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw26_stc.lib to C:\wxWidgets-2.6.2\lib\codeblocks_vc\wxmsw_stc.lib compile->rebuild
building from the commandline (wxwidgets demos)
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release