Difference between revisions of "Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)"

From CodeBlocks
Jump to: navigation, search
(Too much changes to summarize, sorry!)
Line 1: Line 1:
[[Category:Installation\Build Instructions]]
+
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 to compile wxWidgets so that you can compile Code::Blocks on your own.
+
 
 +
'''NOTE:''' These instructions are specific to the Windows operating system, but since we use MinGW it should be possible to apply them with slight adjustments to other platforms.
  
'''NOTE:''' These instructions are MS Windows (TM) specific, but because we are using MinGW it should be possible to use these instructions with some modifications on other platforms.
+
== Installing MinGW ==
 +
'''If you have installed the Code::Blocks and MinGW bundle, or already installed MinGW on your own, you can skip this section.'''
  
== Install MinGW ==
+
Grab the latest MinGW files from the [http://www.mingw.org/download.shtml MinGW download site] and install them into a directory of your choice.
If you don't have the Code::Blocks + MinGW bundle, grab the latest MinGW stuff from the [http://www.mingw.org/download.shtml#hdr2 MinGW site] and install it under a directory you like.
+
'''NOTE:''' In these instructions we're calling the MinGW directory <MINGW>, so you have to replace that with you're own directory.
+
  
'''If you DO have the Code::Blocks + MinGW bundle, or have already installed MINGW on your own, you can skip this section.'''
+
'''NOTE:''' In these instructions we call the MinGW directory ''<MINGW>'', therefore you have to replace it with your corresponding directory.
  
'''NOTE:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)
+
'''NOTE:''' The files are compressed tarballs. You may need a third-party extraction utility like [http://www.7-zip.org/ 7-Zip] in order to extract them.
  
 
You need at least the following files:
 
You need at least the following files:
Line 20: Line 20:
 
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]
 
* [http://prdownloads.sf.net/mingw/binutils-2.15.91-20040904-1.tar.gz?download binutils-2.15.91-20040904-1.tar.gz]
 
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]
 
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]
* [http://prdownloads.sourceforge.net/mingw/gdb-6.3-2.exe?download?download gdb-6.3-2.exe]
+
* [http://prdownloads.sourceforge.net/mingw/gdb-6.3-2.exe?download?download gdb-6.3-2.exe] (GDB is not mandatory, but useful for debugging purposes)
GDB is not really needed, but could be usefull for debugging.
+
  
After you install, make sure you have the following directories under your path:
+
After successful installation of the above, make sure you have the following directories included in your PATH environment variable:
 
* <MINGW>\bin;
 
* <MINGW>\bin;
 
* <MINGW>\mingw32\bin;
 
* <MINGW>\mingw32\bin;
  
== Download and Install the wxWidgets source code ==
+
(You can add them by right-clicking the ''My Computer'' icon on your desktop and selecting ''Properties''. Then select the ''Advanced'' tab and choose ''Environment Variables''.)
The wxWidgets 2.6.2 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (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.
+
 
 +
== Installing the wxWidgets source code ==
 +
The wxWidgets 2.6.2 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#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.
 
If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.
  
'''NOTE:''' In the rest of these instructions we are calling the wxWidgets directory <WXWIN> you have to change it to your own directory. (e.g. "c:\wxWidgets-2.6.2")
+
'''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.2").
  
'''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 (cmd.exe), not from a unix-like shell. BTW, The same problem would probably arise as well if cygwin is in the path.
+
'''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.
  
== Check make version ==
+
== Checking make version ==
If you didn't install MingW yourself you have to make sure you have the right version of make. Open the command prompt and type:
+
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>mingw32-make -v</tt>
 
  <tt>mingw32-make -v</tt>
If the version is 3.80 or greater it is allright to go on, else you have to install the new make.
+
The version should read 3.80 or greater, else you need to install a newer version.
  
 
== Building wxWidgets ==
 
== Building wxWidgets ==
 
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
 
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
 
  <tt>cd <WXWIN>\build\msw</tt>
 
  <tt>cd <WXWIN>\build\msw</tt>
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.'''<BR><BR>
+
'''NOTE: The following instructions do not work with MSYS, or other forms of Unix on Windows.'''
''Regaurding warning: type attributes are honored only at type definition: ''<BR>
+
''the warnings are because the makefile turned all warnings on... you can easily edit it at ur wishes
+
''-lowjoel (Moderator wxWidgets forum) http://wxforum.shadonet.com/viewtopic.php?t=3324''<BR><BR>
+
Now we are on the right place we are first going to clean up the source:
+
<tt>mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 clean</tt>
+
'''NOTE:''' make sure you use the same options to clean that you use for the build step below.  the clean target uses these environment variables and only cleans that version of the generated object and library files (so it will actually not clean the intended files if these variables are not present) <br>
+
'''NOTE:''' if you still have problems with compiling after cleaning, you may want to remove the directory in the build\msw directory. (it contains object files...)
+
When everything is clean we can compile wxWidgets:
+
<tt>mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1</tt>
+
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (non-unicode or debug) you have to make sure you build a MONOLITHIC version. (One big dll)
+
Now you can get a cup of coffee, or do something else, because this could take a long time.
+
  
== Copy libraries ==
+
'''NOTE:''' You can safely ignore warnings like ''warning: type attributes are honored only at type definition'', which are caused by the makefile turning all warnings (gcc's -Wall) on.
When compilation is finished it is usefull to copy the libs to another directory. By doing this you can make several builds (e.g. debug and release).
+
* So first we create a directory this could be done in <WXWIN>\lib.
+
* Then we go to the directory <WXWIN>\lib\gcc_dll (could called diffrent when you changed the build options)
+
* Now we move all the files (.a .dll) and the directory (msw) to the directory of your choice. (for me it is <WXWIN>\lib\codeblocks)
+
'''NOTE:''' Make sure you everything is removed from the directory <WXWIN>\lib\gcc_dll else you can get trouble when compiling another version.
+
  
== Setting up paths ==
+
Now the first thing to do is to clean up the source:
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
+
<tt>mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 SHARED=1 UNICODE=1 clean</tt>
 +
'''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).
  
*Open the Code::Blocks project (CodeBlocks.cbp).
+
'''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.
*It will ask you to define a [[Global_compiler_variables|Global variable]]
+
*Set the path to where you have wxWidgets installed. Eg. ("c:\wxWidgets-2.6.2").
+
*Compile Code::Blocks.
+
  
== Post compilation steps (before running C::B) ==
+
When everything is clean you can start actually compiling wxWidgets:
 +
<tt>mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 SHARED=1 UNICODE=1</tt>
  
When compilation process is finished, simply run the update.bat script. It will ensure that all resource files (that C::B uses) are in the right place and up to date.
+
'''NOTE:''' These options are the officially supported Code::Blocks options. When you want another version of wxWidgets (debug or non-unicode) you have to make sure you build a MONOLITHIC version (one big DLL).
  
Note: This step requires appropriate zip command, which you likely have already set up and working. However, in case you have not, you should find something usable  [ftp://ftp.uu.net/pub/archiving/zip/WIN32/ here].
+
'''NOTE:''' If you wish to compile wxWidgets for developing purposes, you may want to change the build options accordingly (e.g. SHARED=0 for a statically linked library, MONOLITHIC=0 for being able to pick only the libraries you really need etc.). See also INSTALL-MSW.txt in your ''<WXWIN>'' directory.
 +
 
 +
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.
 +
 
 +
== Copying libraries ==
 +
After compilation is finished it is useful to copy the resulting libraries to another directory. By doing this you can make several different builds (e.g. debug and release).
 +
* First create a directory you would like to store the files in. (This could be done in ''<WXWIN>\lib''.)
 +
* Then go to the directory ''<WXWIN>\lib\gcc_dll''. The directory could be called diffrent depending on your build options (e.g. ''<WXWIN>\lib\gcc_lib'' for a static build).
 +
* Now move all the files (ending in .a and .dll) and the directory msw to the directory of your choice. (This could be ''<WXWIN>\lib\codeblocks''.)
 +
 
 +
'''NOTE:''' Make sure you moved everything out of ''<WXWIN>\lib\gcc_dll'', otherwise you could get into trouble when compiling another version.
 +
 
 +
== Compiling Code::Blocks ==
 +
=== 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 compiler variables|Global variable]]
 +
*Set the path to where you have wxWidgets installed (e.g. "c:\wxWidgets-2.6.2").
 +
*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 & VC++ Toolkit 2003 ==
+
'''NOTE''': This step requires an appropriate zip command, which you likely already got. However, in case not, you should find something suitable [ftp://ftp.uu.net/pub/archiving/zip/WIN32/ here].
  
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 on the vc++ toolkit seamlessly.
+
== 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.
  
<br />
 
 
install VCToolkitSetup.exe <br>
 
install VCToolkitSetup.exe <br>
 
install PlatformSDK <br>
 
install PlatformSDK <br>
Line 162: Line 166:
 
building from the commandline (wxwidgets demos) <br>
 
building from the commandline (wxwidgets demos) <br>
 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release
 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release
 +
 +
[[Category:Installation\Build Instructions]]

Revision as of 18:16, 19 April 2006

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.

NOTE: These instructions are specific to the Windows operating system, but since we use MinGW it should be possible to apply them with slight adjustments to other platforms.

Installing MinGW

If you have installed the Code::Blocks and MinGW bundle, or already installed MinGW on your own, you can skip this section.

Grab the latest MinGW files from the MinGW download site and install them into a directory of your choice.

NOTE: In these instructions we call the MinGW directory <MINGW>, therefore you have to replace it with your corresponding directory.

NOTE: The files are compressed tarballs. You may need a third-party extraction utility like 7-Zip in order to extract them.

You need at least the following files:

After successful installation of the above, make sure you have the following directories included in your PATH environment variable:

  • <MINGW>\bin;
  • <MINGW>\mingw32\bin;

(You can add them by right-clicking the My Computer icon on your desktop and selecting Properties. Then select the Advanced tab and choose Environment Variables.)

Installing the wxWidgets source code

The wxWidgets 2.6.2 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.

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.2").

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.

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:

mingw32-make -v

The version should read 3.80 or greater, else you need to install a newer version.

Building wxWidgets

Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:

cd <WXWIN>\build\msw

NOTE: The following instructions do not work with MSYS, or other forms of Unix on Windows.

NOTE: You can safely ignore warnings like warning: type attributes are honored only at type definition, which are caused by the makefile turning all warnings (gcc's -Wall) on.

Now the first thing to do is to clean up the source:

mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 SHARED=1 UNICODE=1 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 BUILD=release MONOLITHIC=1 SHARED=1 UNICODE=1

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

NOTE: If you wish to compile wxWidgets for developing purposes, you may want to change the build options accordingly (e.g. SHARED=0 for a statically linked library, MONOLITHIC=0 for being able to pick only the libraries you really need etc.). See also INSTALL-MSW.txt in your <WXWIN> directory.

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.

Copying libraries

After compilation is finished it is useful to copy the resulting libraries to another directory. By doing this you can make several different builds (e.g. debug and release).

  • First create a directory you would like to store the files in. (This could be done in <WXWIN>\lib.)
  • Then go to the directory <WXWIN>\lib\gcc_dll. The directory could be called diffrent depending on your build options (e.g. <WXWIN>\lib\gcc_lib for a static build).
  • Now move all the files (ending in .a and .dll) and the directory msw to the directory of your choice. (This could be <WXWIN>\lib\codeblocks.)

NOTE: Make sure you moved everything out of <WXWIN>\lib\gcc_dll, otherwise you could get into trouble when compiling another version.

Compiling Code::Blocks

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.2").
  • 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.

NOTE: This step requires an appropriate zip command, which you likely already got. However, in case not, you should find something suitable here.

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 VCToolkitSetup.exe
install PlatformSDK
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
set INCLUDE=%MSVC%\include;%MSSDK%\include
set LIB=%MSVC%\lib;%MSSDK%\lib;%VC7%\lib
set PATH=%MSVC%\bin;%MSSDK%\bin;%PATH%
set PATH=%PATH%;%MSSDK%\bin\Win64

cd <WXWIN>\build\msw
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

codeblocks

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