Code::Blocks - User contributions [en]

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-12-17T16:51:52Z

Grv: /* Building unicode wxWidgets & CodeBlocks */

These are the instructions to compile wxWidgets so that you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 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.

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

'''NOTE:''' Download and apply the patches for wxWidgets 2.6.1 source code. wxWidgets Patches for 2.6.1. Various wxMSW fixes:
http://www.wxwindows.org/patch.htm
ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip

'''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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt> 
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.''' 
''Regaurding warning: type attributes are honored only at type definition: '' 
''the warnings are because the makefile turned all warnings on... you can easily edit it at ur wishes
''-lowjoel (Moderator wxWidgets forum) {http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?t=3324&start=0&postdays=0&postorder=asc&highlight=&sid=12dc997430a4cb2bc99f0175699f58de}'' 
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library (Not needed for CVS HEAD version of Code::Blocks) ==
If you closed the command prompt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using with codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks does not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by yourself.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. You have three possibilities
* put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in your PATH
* or put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32
* or add C:\wxWidgets-2.6.1\lib\codeblocks to compile -> compiler options -> programs -> additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move gcc_dll codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building unicode wxWidgets & CodeBlocks====

I'm assuming you're using wxWidgets-2.6.2 and it's installed in c:\. Modify for different minor revisions or install paths.

<pre>
1. grab the latest SVN source
2. open CodeBlocks-NewBuild.cbp with a text editor:
replace all occurances of wxmsw26 with wxmsw26u
replace all occurances of msw" with mswu"
save this as CodeBlocks-NewBuild-unicode.cbp
3. open up a recent version of codeblocks which supports the new build .cbp files. one of the latest svn binaries which you can find in the forums is your best bet
4. open the CodeBlocks-NewBuild-unicode.cbp project file
5. goto Project->Build options->Custom variables
set WX_CFG=Unicode
6. save the project and close codeblocks for the changes to take effect (reload the custom variables for the project)
7. open codeblocks again and the project file

8. rename any existing rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllNonUnicode
9. open a start menu->run->cmd.exe prompt
cd to c:\wxWidgets-2.6.2\build\msw
10. type:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
11. rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllUnicode
12. open c:\wxWidgets-2.6.2\lib\gcc_dllUnicode\msw\wx\setup.h
make sure you have
#define wxUSE_UNICODE 1
(and not 0)

13. go back to codeblocks and select compile->rebuild
set the wx global variable to c:\wxWidgets-2.6.2 if it prompts
14. once it finishes, run update.bat
</pre>

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

 
Note:
 
If you are compiling the unicode version of wxWidgets (UNICODE=1) and CodeBlocks, then linker errors like:
 
wxscintilla.cpp:2551: undefined reference to `_imp___ZNK8wxString11BeforeFirstEc'
wxscintilla.cpp:2552: undefined reference to `_imp___ZNK8wxString10AfterFirstEc'
wxscintilla.cpp:2724: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'
wxscintilla.cpp:2736: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'

mean that you forgot to change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1" in wx\setup.h

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-12-17T16:48:12Z

Grv: /* Building unicode wxWidgets & CodeBlocks */

These are the instructions to compile wxWidgets so that you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 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.

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

'''NOTE:''' Download and apply the patches for wxWidgets 2.6.1 source code. wxWidgets Patches for 2.6.1. Various wxMSW fixes:
http://www.wxwindows.org/patch.htm
ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip

'''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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt> 
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.''' 
''Regaurding warning: type attributes are honored only at type definition: '' 
''the warnings are because the makefile turned all warnings on... you can easily edit it at ur wishes
''-lowjoel (Moderator wxWidgets forum) {http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?t=3324&start=0&postdays=0&postorder=asc&highlight=&sid=12dc997430a4cb2bc99f0175699f58de}'' 
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library (Not needed for CVS HEAD version of Code::Blocks) ==
If you closed the command prompt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using with codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks does not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by yourself.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. You have three possibilities
* put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in your PATH
* or put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32
* or add C:\wxWidgets-2.6.1\lib\codeblocks to compile -> compiler options -> programs -> additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move gcc_dll codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building unicode wxWidgets & CodeBlocks====

I'm assuming you're using wxWidgets-2.6.2 and it's installed in c:\. Modify for different minor revisions or install paths.

<pre>
1. grab the latest SVN source
2. open CodeBlocks-NewBuild.cbp with a text editor:
replace all occurances of wxmsw26 with wxmsw26u
replace all occurances of msw" with mswu"
3. open up a recent version of codeblocks which supports the new build .cbp files. one of the latest svn binaries which you can find in the forums is your best bet
4. open the CodeBlocks-NewBuild.cbp project file
5. goto Project->Build options->Custom variables
set WX_CFG=Unicode
6. save the project and close codeblocks for the changes to take effect (reload the custom variables for the project)
7. open codeblocks again and the project file

8. rename any existing rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllNonUnicode
9. open a start menu->run->cmd.exe prompt
cd to c:\wxWidgets-2.6.2\build\msw
10. type:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
11. rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllUnicode
12. open c:\wxWidgets-2.6.2\lib\gcc_dllUnicode\msw\wx\setup.h
make sure you have
#define wxUSE_UNICODE 1
(and not 0)

13. go back to codeblocks and select compile->rebuild
set the wx global variable to c:\wxWidgets-2.6.2 if it prompts
14. once it finishes, run update.bat
</pre>

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

 
Note:
 
If you are compiling the unicode version of wxWidgets (UNICODE=1) and CodeBlocks, then linker errors like:
 
wxscintilla.cpp:2551: undefined reference to `_imp___ZNK8wxString11BeforeFirstEc'
wxscintilla.cpp:2552: undefined reference to `_imp___ZNK8wxString10AfterFirstEc'
wxscintilla.cpp:2724: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'
wxscintilla.cpp:2736: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'

mean that you forgot to change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1" in wx\setup.h

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-12-17T16:45:23Z

Grv: /* Building codeblocks from source (using makefile) */

These are the instructions to compile wxWidgets so that you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 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.

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

'''NOTE:''' Download and apply the patches for wxWidgets 2.6.1 source code. wxWidgets Patches for 2.6.1. Various wxMSW fixes:
http://www.wxwindows.org/patch.htm
ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip

'''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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt> 
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.''' 
''Regaurding warning: type attributes are honored only at type definition: '' 
''the warnings are because the makefile turned all warnings on... you can easily edit it at ur wishes
''-lowjoel (Moderator wxWidgets forum) {http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?t=3324&start=0&postdays=0&postorder=asc&highlight=&sid=12dc997430a4cb2bc99f0175699f58de}'' 
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library (Not needed for CVS HEAD version of Code::Blocks) ==
If you closed the command prompt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using with codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks does not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by yourself.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. You have three possibilities
* put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in your PATH
* or put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32
* or add C:\wxWidgets-2.6.1\lib\codeblocks to compile -> compiler options -> programs -> additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move gcc_dll codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building unicode wxWidgets & CodeBlocks====

I'm assuming you're using wxWidgets-2.6.2 and it's installed in c:\. Modify for different minor revisions or install paths.

<pre>
1. grab the latest SVN source
2. open CodeBlocks-NewBuild.cbp with a text editor:
replace all occurances of wxmsw26 with wxmsw26u
replace all occurances of msw" with mswu"
3. open up a recent version of codeblocks which supports the new build .cbp files. one of the latest svn binaries which you can find in the forums is your best bet
4. open the CodeBlocks-NewBuild.cbp project file
5. goto Project->Build options->Custom variables
set WX_CFG=Unicode
6. save the project and close codeblocks for the changes to take effect (reload the custom variables for the project)
7. open codeblocks again and the project file

8. rename any existing rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllNonUnicode
9. open a start menu->run->cmd.exe prompt
cd to c:\wxWidgets-2.6.2\build\msw
10. type:
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
11. rename c:\wxWidgets-2.6.2\lib\gcc_dll to c:\wxWidgets-2.6.2\lib\gcc_dllUnicode
12. open c:\wxWidgets-2.6.2\lib\gcc_dllUnicode\msw\wx\setup.h
make sure you have
#define wxUSE_UNICODE 1
(and not 0)

13. go back to codeblocks and hit compile
set the wx global variable to c:\wxWidgets-2.6.2 if it prompts
</pre>

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

 
Note:
 
If you are compiling the unicode version of wxWidgets (UNICODE=1) and CodeBlocks, then linker errors like:
 
wxscintilla.cpp:2551: undefined reference to `_imp___ZNK8wxString11BeforeFirstEc'
wxscintilla.cpp:2552: undefined reference to `_imp___ZNK8wxString10AfterFirstEc'
wxscintilla.cpp:2724: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'
wxscintilla.cpp:2736: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'

mean that you forgot to change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1" in wx\setup.h

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-12-15T22:47:32Z

Grv: /* Building codeblocks from source (using makefile) */

These are the instructions to compile wxWidgets so that you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 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.

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

'''NOTE:''' Download and apply the patches for wxWidgets 2.6.1 source code. wxWidgets Patches for 2.6.1. Various wxMSW fixes:
http://www.wxwindows.org/patch.htm
ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip

'''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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt> 
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.''' 
''Regaurding warning: type attributes are honored only at type definition: '' 
''the warnings are because the makefile turned all warnings on... you can easily edit it at ur wishes
''-lowjoel (Moderator wxWidgets forum) {http://www.solidsteel.nl/users/wxwidgets/viewtopic.php?t=3324&start=0&postdays=0&postorder=asc&highlight=&sid=12dc997430a4cb2bc99f0175699f58de}'' 
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library (Not needed for CVS HEAD version of Code::Blocks) ==
If you closed the command prompt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using with codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks does not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by yourself.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. You have three possibilities
* put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in your PATH
* or put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32
* or add C:\wxWidgets-2.6.1\lib\codeblocks to compile -> compiler options -> programs -> additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move gcc_dll codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

 
Note:
 
If you are compiling the unicode version of wxWidgets (UNICODE=1) and CodeBlocks, then linker errors like:
 
wxscintilla.cpp:2551: undefined reference to `_imp___ZNK8wxString11BeforeFirstEc'
wxscintilla.cpp:2552: undefined reference to `_imp___ZNK8wxString10AfterFirstEc'
wxscintilla.cpp:2724: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'
wxscintilla.cpp:2736: undefined reference to `_imp___ZN6wxFileC1EPKcNS_8OpenModeE'

mean that you forgot to change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1" in wx\setup.h

Installing Code::Blocks from source on Linux

2005-09-17T18:22:52Z

Grv: /* Building Code::Blocks */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig
source /etc/profile

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

.............................................

If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from cvs). If you get errors like:
aclocal:configure.in:61: warning: macro `AM_OPTIONS_WXCONFIG' not found in library
Then aclocal is having trouble finding the wxWidgets .m4 files. You can do one of two things:
To just get bootstrap to find the path this time do:
export ACLOCAL_FLAGS="--acdir=`wx-config --prefix`/share/aclocal"
To change the aclocal search path more permanently do:
echo `wx-config --prefix`/share/aclocal >> /usr/share/aclocal/dirlist
Then aclocal will also search somewhere like /opt/wx/2.6/share/aclocal

Once you've run the bootstrap script, installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-cvs
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-cvs
followed by 'make && make install' as usual.

Installing Code::Blocks from source on Linux

2005-09-17T18:10:23Z

Grv: /* wxWidgets 2.6.1 build */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig
source /etc/profile

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

.............................................

If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from cvs).

Then installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-cvs
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-cvs
followed by 'make && make install' as usual.

Installing Code::Blocks from source on Linux

2005-09-17T08:54:29Z

Grv: /* Building Code::Blocks */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

.............................................

If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from cvs).

Then installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-cvs
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-cvs
followed by 'make && make install' as usual.

Installing Code::Blocks from source on Linux

2005-09-17T08:50:13Z

Grv: /* Building Code::Blocks */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

----

If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from cvs).

Then installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-cvs
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-cvs
followed by 'make && make install' as usual.

Installing Code::Blocks from source on Linux

2005-09-17T08:49:42Z

Grv: /* Building Code::Blocks */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

<hr>

If you're compiling the cvs HEAD verions of CodeBlocks (or future versions) then the unix build has switched to autotools. So first build wxWidgets as described above and then build CodeBlocks as follows:

./bootstrap

This sets up the configure script and it's dependencies. It only needs to be run once (after downloading the source from cvs).

Then installing is as simple as:
./configure
make
make install

To uninstall you can later run:
make uninstall

If you want to recompile everything, first run:
make clean
and then follow the above sequence for installing.

By default, CodeBlocks will install to /usr/local. If you want it in its own tree (so you can have multiple versions of CodeBlocks, each in its own subdirectory of /opt) replace the above ./configure command with:
./configure --prefix=/opt/codeblocks-cvs
or similar. Then you can later install a different build like:
./configure --prefix=/opt/codeblocks2-cvs
followed by 'make && make install' as usual.

Installing Code::Blocks from source on Linux

2005-09-17T08:38:45Z

Grv: /* wxWidgets 2.6.1 build */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

(Note: it's not necessary to make or install stc if you're compiling cvs HEAD)

add /opt/wx/2.6/bin to the PATH (if you're shell is bash then edit /etc/profile or ~/.bash_profile). an example PATH
export PATH=/usr/bin:/opt/wx/2.6/bin:$PATH
add /opt/wx/2.6/lib to /etc/ld.so.conf (nano /etc/ld.so.conf)
then run:
ldconfig

That's it. Now the linker will look in /opt/wx/2.6/lib for wx libraries and you will have a monolithic shared library unicode build.

To check that things are working, type:
wx-config --prefix
which should give you /opt/wx/2.6
wx-config --libs
which should have at least
-L/opt/wx/2.6/lib -lwx_gtk2-2.6
but can contain other flags as well.
which wx-config
should return /opt/wx/2.6/bin/wx-config

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-09-09T04:55:26Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move gcc_dll codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; move vc_dll codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

FAQ

2005-08-28T18:35:45Z

Grv: /* When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? */

= General =

== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==

Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)

== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==

Since version 1.0-beta5, no it is not. Code::Blocks works with GNU "make" [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to "Project/Build options", switch to the "Other" tab and select the build method you prefer.

== What licence is Code::Blocks released under? ==

GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])

= Compiling =

== What compiler can I use with Code::Blocks? ==

Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.

As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.

== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==

A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==

''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''

You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under "Settings/Configure plugins/Compiler" in the "Programs" tab...
Second, you have to add two additional compiler (include) dirs. Go to "Settings/Configure plugins/Compiler" and in the "Compiler dirs" tab add "dev-cpp\include\c++" and "dev-cpp\include\c++\mingw32" (substituting "dev-cpp" with the actual dev-cpp installation folder).

== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==

BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.

== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==

Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a "Custom Makefile" checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.
Also make sure that "GNU make" is the selected build method for the specific compiler.

== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==

Click on "Project/Build options" and select the compiler you want for your project/target.

== When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ==

You need to add WXUSINGDLL in "Project->Build options->Compiler #defines" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
Other errors with the same resolution are:
'unresolved external symbol "char const * const wxEmptyString" (?wxEmptyString@@3PBDB)' or similar.
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==

sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download MinGW :)

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (VCT3)
LIBCPMTD.LIB Multithreaded, static link (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

== Where are the libraries for the OpenGL / SDL / etc. projects? ==

They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.
In common terms, "batteries not included" :)

== Is it possible to use Visual C++ 6.0 with Code::Blocks? ==

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-26T13:58:54Z

Grv: /* Building wxWidgets */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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) 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-26T13:56:51Z

Grv: /* Build the STC library */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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 to only clean that version of the generated object and library files 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-26T13:56:17Z

Grv: /* Building wxWidgets */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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 to only clean that version of the generated object and library files 
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-26T13:55:52Z

Grv: /* Building wxWidgets */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 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 to only clean that version of the generated object and library files
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

Tips'n'Tricks

2005-08-25T15:42:35Z

Grv: /* Compiling from source */

====[[Personalities]]====
====[[Fixing Internal Errors]]====
====[[Setting the WX_VER variable]]====
====[[Running under colinux]]====

Tips'n'Tricks

2005-08-25T15:42:05Z

Grv: /* Running under colinux */

====[[Personalities]]====
====[[Fixing Internal Errors]]====
====[[Setting the WX_VER variable]]====
====[[Running under colinux]]====

===Compiling from source===

The reason to want to do this is if you want to use a different kernel than the one provided by the colinux installer (currently 2.6.11). If you want to compile your own modules or add something to the kernel then this might be the way to go. If you just try to compile a new kernel and then run it under the existing colinux binaries you will get an ABI mismatch unless you compiled with their version of gcc they used (3.3.x) to cross compile the colinux binaries, so it's probably best to just setup your own cross compiler under linux and recompile the source. Note that colinux runs in kernel mode, but does not allow linux to do direct hardware access. It writes a layer and then hands hardware requests to windows. So no sound output is supported (yet) and X doesn't run under linux (yet - but you can use xmingw as described above). It's best not to modify the kernel settings from what the colinux .config file provides too much. You will need a working linux installation and an internet connection to compile from source. 

- grab the source
[http://www.colinux.org/snapshots/stable-colinux-20050524.tar.gz]

- switch to linux
I actually recompiled everything from within colinux which works fine. You could also reboot into linux. 

- extract the source and compile
I used /usr/src as the base directory. You can use /home/username if desired. 
cd /usr/src; tar xfz stable-colinux-20050524.tar.gz
cd stable-colinux-20050524

Your linux distribution needs a couple of things to be able to setup the cross compiler and compile the daemons. I needed to grab and install: 
unix2dos-2.2.src.tar.gz

The configure script will let you know about any other missing dependencies (Everything else was present here: LFS & BLFS installation). Make sure you have wget installed since all needed mingw packages are fetched with it. 

Edit bin/build-common.sh 
GCC_VERSION="3.4.4"
GCC_RELEASE="$GCC_VERSION-20050522-1"
GCC_PATCH="gcc-core-$GCC_RELEASE-src-fix1.patch"
MXML_URL=http://ftp.easysw.com/pub/mxml/1.3

Needed patch: 
<nowiki>#########</nowiki>begin gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>##########</nowiki>
<pre>
diff -urN gcc-3.4.4-20050522-1.old/gcc/crtstuff.c gcc-3.4.4-20050522-1/gcc/crtstuff.c
--- gcc-3.4.4-20050522-1.old/gcc/crtstuff.c 2005-08-18 15:46:45.000000000 -0400
+++ gcc-3.4.4-20050522-1/gcc/crtstuff.c 2005-08-18 15:53:00.000000000 -0400
@@ -602,7 +602,8 @@
#if defined (USE_EH_FRAME_REGISTRY) \
&& !__USING_SJLJ_EXCEPTIONS__
static int __EH_FRAME_END__[]
- __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME),
+/* __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME), */
+ __attribute__ ((unused, section(EH_FRAME_SECTION_NAME),
aligned(4)))
= { 0 };
static void __reg_frame_ctor (void) __attribute__ ((constructor));
</pre>
<nowiki>#########</nowiki>end gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>#########</nowiki> 
Save the above (between the <nowiki>###</nowiki> marks) to gcc-core-3.4.4-20050522-1-src-fix1.patch 
mkdir /usr/src/download (mkdir /home/username/download if using home directory)
mv gcc-core-3.4.4-20050522-1-src-fix1.patch /usr/src/download

The patch is needed for gcc 3.4.4 to compile as a cross compiler using sjlj exceptions (dwarf exceptions don't work well under windows it seems). Otherwise you get errors about the mode(SI) statement. 

Compile: 
./configure
make
make # I got md5sum creation errors, but things resumed ok -- just type make again...
make install

This will download and install a mingw cross compiler under linux. It will then proceed to compile the windows colinux daemons and finally the colinux kernel. The kernel source will be in a subdirectory of the directory you are compiling from (/usr/src/linux-2.6.11-co or something). You can later recompile the colinux kernel by switching to this directory and doing: 
make menuconfig # set kernel options...don't change too much or it may not work with colinux
make vmlinux
make modules modules_install # installed to /lib/linux-2.6.11-co i believe

Then just move the /usr/src/linux-2.6.11-co/vmlinux kernel image to c:\coLinux (backup the old one in case). Fyi, the kernel patch they are using is under stable-colinux-20050524/patch/linux and the kernel .config file is stable-colinux-20050524/config/linux-config 
(tar xfz linux-2.6.11-12.tar.gz; cd linux-2.6.11-12; patch -p1 -i stable-colinux-20050524/patch/linux; cp stable-colinux-20050524/config/linux-config .config) 
to start from fresh kernel.org sources. note that only up to 2.6.11-X is working. A patch is available on colinux.org for 2.6.12 but I haven't tried it. 

Btw the make install above just installs to a subdirectory (dist/). It won't touch /usr or /usr/local. Once everything completes you can just tar the dist directory and copy to your windows directory: 
tar cfz dist.tar.gz dist
mount /mnt/cofs
mv dist.tar.gz /mnt/cofs
Winrar supports extracting from .tar.gz and .tar.bz2 archives (7zip does too I believe).
That's all that should be required to build colinux from source and compile custom colinux kernels.
Make sure you use the same gcc major version (gcc 3.4.x here) to compile both the daemons and kernel (the automatic kernel build run by the colinux install scripts does this by default).

Running under colinux

2005-08-25T15:41:15Z

Grv:

====[[Running under colinux]]====

Setting up a dual-boot system is easy to do these days, but switching to linux requires a reboot. What colinux does is let you run your linux distribution under windows. They also have the option of downloading a debian or gentoo filesystem instead and using that basic linux system (it's missing lots of packages though, but they do support apt-get/emerge). This is a walkthrough for setting up colinux to work with an existing linux distribution on another hard drive partition, since it's the more complicated (and useful) of the two options.

- download colinux
[http://www.colinux.org/snapshots/stable-coLinux-20050524.exe]
That's the 5/24/05 snapshot under Development Snapshots from the homepage. It's stable as far as I can tell and they've fixed a couple major bugs since stable.

- run the installer
check everything except uncheck "Root Filesystem image Download" 
install to c:\coLinux and not c:\Program Files\coLinux, since /dev paths are relative to the installation directory 
don't bother downloading and installing WinPCAP (the included TAP driver works fine) 
hit "continue anyway" for the tap driver installation 
goto Network Connections under control panel and right click on the newly installed LAN connection (TAP-Win32 Adapter V8 (colinux)). You may want to set configure->advanced->media status to "always connected". Set the ip (tcp/ip properties) to a new ip address on your lan. E.g. my hardware firewall my internet address 68.x.x.x. Then one computer gets 192.168.1.2 and the other one (wireless connection) gets 192.168.1.3. They both set the gateway field to 192.168.1.1 (configured in the hardware firewall settings). So I set the TAP adapter ip to 192.168.1.4, it's gatway to 192.168.1.1 and the dns servers to those given to me by my isp (68.x.x.x). Now select both your network connection and the TAP lan connection (ctrl-click) and then right click on one of them and select Bridge Connections. Now right-click the Network Bridge and set the tcp/ip address to the same one your internet connection uses (192.168.1.3 here). Also put in the dns servers and gateway. You may need to right-click the Network Bridge and click Disable followed by Enable to get the connection working. What happens is that your windows internet connection is still the same ip (192.168.1.3) but from within colinux, your TAP eth0 connection will use the new ip given to the TAP connection (192.168.1.4). So colinux looks like a new box on your LAN. 

- create a configuration script
first you need to find out which partitions your linux distribution uses as seen by windows. download either Dmdiag.exe from Microsoft or WinObj.zip from Sysinternals. 
[http://download.microsoft.com/download/win2000platform/WebPacks/1.00.0.1/NT5/EN-US/Dmdiag.exe]
[http://www.sysinternals.com/Files/WinObj.zip]

usage: 
dmdiag > out.txt 
winobj - 
check \GLOBAL?? for the name of your windows partitions (C:, D:). I have \Device\HarddiskVolume1 and \Device\HarddiskVolume2 for C: and D:. The next partition is probably the linux one. Goto \Device\Harddisk0 to see all the partitions on the disk. 

now create a batch script (c:\coLinux\colinux.bat) to launch colinux: 
colinux-daemon.exe -t nt mem=256 kernel=vmlinux hda6=\Device\Harddisk0\Partition3 hda7=\Device\Harddisk0\Partition4 root=/dev/hda6 eth0=tuntap cofs0=c:\coLinux 3 

This means use the standard NT console (better because you can cut&paste using the mouse), give 256mb of ram to colinux, specifies the name of the kernel, the linux partitiions, virtual ethernet adapter, and a shared directory which can be used to copy files between the colinux and windows systems. 

My linux root (/) partition is /dev/hda6 and swap partition is /dev/hda7. These correspond to \Device\Harddisk0\Partition3 and \Device\Harddisk0\Partition4 under windows (note that windows doesn't reserve a partition name for the extended partition -- my linux partitions are logical and not primary partitions). The root is given to be /dev/hda6, and you can just put tuntap for eth0, which will find the TAP connection we setup. cofs0 will be the device name of the shared folder to use to transfer files to/from windows. The 3 on the end is passed to the kernel as a kernel parameter. It means enter runlevel 3 (init 3). I need to do this since my default runlevel on boot is 5 which starts KDE, but this will crash colinux since it doesn't support X under colinux. 

- run the batch file and create some linux scripts 
run the .bat file just created and see that everything works. now create a couple of linux scripts for convenience. I created /usr/bin/colinuxnet.sh to start the network, /usr/bin/off.sh to shutdown, and a config file /etc/colinuxdisplay to set the DISPLAY environment variable. 
<nowiki>#</nowiki>!/bin/sh 
<nowiki>#</nowiki>/usr/bin/colinuxnet.sh 
ifconfig eth0 192.168.1.4 && route add default gw 192.168.1.1 

<nowiki>#</nowiki>!/bin/sh 
<nowiki>#</nowiki>/usr/bin/off.sh 
shutdown -h now 

<nowiki>#</nowiki>/etc/colinuxdisplay 
export DISPLAY=192.168.1.3:0.0 

be sure to make the shell scripts executable: chmod a+x /usr/bin/colinux.net /usr/bin/off.sh
Note that shutdown -h now is the proper way to stop colinux (don't just click the console X button). The 192.168.1.3 address is the address of my ethernet connection under windows. 0.0 specifies the first X display. 

Modify /etc/fstab to mount the cofs0 windows directory: 
<nowiki>#</nowiki>/etc/fstab 
... 
cofs0 /mnt/cofs cofs noauto,users,defaults 0 0 

Notice there is no /dev prefix. This won't automount and will be mountable by normal users (and not fsck checked). 
Create /mnt/cofs: 
mkdir /mnt/cofs 
chmod 777 /mnt/cofs (or chown username:users /mnt/cofs) 
To mount: 
mount /mnt/cofs 

You can copy both to and from c:\coLinux now. 

- setup Xming
[http://www.freedesktop.org/~ago/Xming/Xming-20050705-setup.exe]
Run the installer and don't bother to configure xlaunch. It just writes out a config file for later use but we'll just pass everything on the commandline anyway. 

create some batch files to run X: 
rem c:\coLinux\runx.bat 
@echo off 
SET DISPLAY=127.0.0.1:0.0 
SET REMOTE_HOST=192.168.1.4 
SET LOCAL_HOST=192.168.1.3 
start C:\Progra~1\Xming\Xming.exe -query %REMOTE_HOST% -nodecoration -lesspointer -from %LOCAL_HOST% -clipboard 

rem c:\coLinux\runx_multiwindow.bat 
@echo off 
SET DISPLAY=127.0.0.1:0.0 
SET REMOTE_HOST=192.168.1.4 
SET LOCAL_HOST=192.168.1.3 
start C:\Progra~1\Xming\Xming.exe -nodecoration -lesspointer -from %LOCAL_HOST% -clipboard -multiwindow -ac 

Remote host is the colinux host and local host is the windows host. You may need to forward TCP port 6000 on your firewall to allow colinux to communicate over TCP with the Xming server. The first batch script is for use with XDMCP ([http://freedesktop.org/wiki/Xming]). This will allow KDE to run under Xming. Details: 
vi /opt/kde/share/config/kdm/Xaccess 
*
This will allow access from all hosts 
vi /opt/kde/share/config/kdm/kdmrc 
[Xdmcp] Enable=true
Enables XDMCP 
vi /usr/X11/xdm/Xservers 
#:0 local /usr/X11R6/bin/X
Comment out that line so that the linux X doesn't start by default. 
vi /usr/X11/xdm/Xaccess 
*
Not sure if that's really needed. Same idea as the kdm/Xaccess though. I think this is similar to doing xhost +. 
Note that everything still starts up and runs normally if I reboot into linux through grub/lilo. These changes didn't prevent KDE or X from starting up. 

The second batch file (multiwindow) is used for when you don't want a full KDE on windows, but just want the linux consoles (alt-f4 to get multiple consoles does work) and a couple graphical linux applications to run under Xming. The -ac flag disables access control (needed since we are not using XDMCP and otherwise you get errors involving mit cookies or access denied). To test this mode: 
run colinux.bat 
run runx_multiwindow.bat 
under linux: 
. /etc/colinuxdisplay (or source /etc/colinuxdisplay) 
try: ddd (assuming it's installed on your linux distro). 

That should be all there is to it to get codeblocks running under colinux (after compiling codeblocks under linux of course). 

===Compiling from source===

The reason to want to do this is if you want to use a different kernel than the one provided by the colinux installer (currently 2.6.11). If you want to compile your own modules or add something to the kernel then this might be the way to go. If you just try to compile a new kernel and then run it under the existing colinux binaries you will get an ABI mismatch unless you compiled with their version of gcc they used (3.3.x) to cross compile the colinux binaries, so it's probably best to just setup your own cross compiler under linux and recompile the source. Note that colinux runs in kernel mode, but does not allow linux to do direct hardware access. It writes a layer and then hands hardware requests to windows. So no sound output is supported (yet) and X doesn't run under linux (yet - but you can use xmingw as described above). It's best not to modify the kernel settings from what the colinux .config file provides too much. You will need a working linux installation and an internet connection to compile from source. 

- grab the source
[http://www.colinux.org/snapshots/stable-colinux-20050524.tar.gz]

- switch to linux
I actually recompiled everything from within colinux which works fine. You could also reboot into linux. 

- extract the source and compile
I used /usr/src as the base directory. You can use /home/username if desired. 
cd /usr/src; tar xfz stable-colinux-20050524.tar.gz
cd stable-colinux-20050524

Your linux distribution needs a couple of things to be able to setup the cross compiler and compile the daemons. I needed to grab and install: 
unix2dos-2.2.src.tar.gz

The configure script will let you know about any other missing dependencies (Everything else was present here: LFS & BLFS installation). Make sure you have wget installed since all needed mingw packages are fetched with it. 

Edit bin/build-common.sh 
GCC_VERSION="3.4.4"
GCC_RELEASE="$GCC_VERSION-20050522-1"
GCC_PATCH="gcc-core-$GCC_RELEASE-src-fix1.patch"
MXML_URL=http://ftp.easysw.com/pub/mxml/1.3

Needed patch: 
<nowiki>#########</nowiki>begin gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>##########</nowiki>
<pre>
diff -urN gcc-3.4.4-20050522-1.old/gcc/crtstuff.c gcc-3.4.4-20050522-1/gcc/crtstuff.c
--- gcc-3.4.4-20050522-1.old/gcc/crtstuff.c 2005-08-18 15:46:45.000000000 -0400
+++ gcc-3.4.4-20050522-1/gcc/crtstuff.c 2005-08-18 15:53:00.000000000 -0400
@@ -602,7 +602,8 @@
#if defined (USE_EH_FRAME_REGISTRY) \
&& !__USING_SJLJ_EXCEPTIONS__
static int __EH_FRAME_END__[]
- __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME),
+/* __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME), */
+ __attribute__ ((unused, section(EH_FRAME_SECTION_NAME),
aligned(4)))
= { 0 };
static void __reg_frame_ctor (void) __attribute__ ((constructor));
</pre>
<nowiki>#########</nowiki>end gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>#########</nowiki> 
Save the above (between the <nowiki>###</nowiki> marks) to gcc-core-3.4.4-20050522-1-src-fix1.patch 
mkdir /usr/src/download (mkdir /home/username/download if using home directory)
mv gcc-core-3.4.4-20050522-1-src-fix1.patch /usr/src/download

The patch is needed for gcc 3.4.4 to compile as a cross compiler using sjlj exceptions (dwarf exceptions don't work well under windows it seems). Otherwise you get errors about the mode(SI) statement. 

Compile: 
./configure
make
make # I got md5sum creation errors, but things resumed ok -- just type make again...
make install

This will download and install a mingw cross compiler under linux. It will then proceed to compile the windows colinux daemons and finally the colinux kernel. The kernel source will be in a subdirectory of the directory you are compiling from (/usr/src/linux-2.6.11-co or something). You can later recompile the colinux kernel by switching to this directory and doing: 
make menuconfig # set kernel options...don't change too much or it may not work with colinux
make vmlinux
make modules modules_install # installed to /lib/linux-2.6.11-co i believe

Then just move the /usr/src/linux-2.6.11-co/vmlinux kernel image to c:\coLinux (backup the old one in case). Fyi, the kernel patch they are using is under stable-colinux-20050524/patch/linux and the kernel .config file is stable-colinux-20050524/config/linux-config 
(tar xfz linux-2.6.11-12.tar.gz; cd linux-2.6.11-12; patch -p1 -i stable-colinux-20050524/patch/linux; cp stable-colinux-20050524/config/linux-config .config) 
to start from fresh kernel.org sources. note that only up to 2.6.11-X is working. A patch is available on colinux.org for 2.6.12 but I haven't tried it. 

Btw the make install above just installs to a subdirectory (dist/). It won't touch /usr or /usr/local. Once everything completes you can just tar the dist directory and copy to your windows directory: 
tar cfz dist.tar.gz dist
mount /mnt/cofs
mv dist.tar.gz /mnt/cofs
Winrar supports extracting from .tar.gz and .tar.bz2 archives (7zip does too I believe).
That's all that should be required to build colinux from source and compile custom colinux kernels.
Make sure you use the same gcc major version (gcc 3.4.x here) to compile both the daemons and kernel (the automatic kernel build run by the colinux install scripts does this by default).

Tips'n'Tricks

2005-08-25T15:40:28Z

Grv: /* Running under colinux */

====[[Personalities]]====
====[[Fixing Internal Errors]]====
====[[Setting the WX_VER variable]]====
====[[Running under colinux]]====

Setting up a dual-boot system is easy to do these days, but switching to linux requires a reboot. What colinux does is let you run your linux distribution under windows. They also have the option of downloading a debian or gentoo filesystem instead and using that basic linux system (it's missing lots of packages though, but they do support apt-get/emerge). This is a walkthrough for setting up colinux to work with an existing linux distribution on another hard drive partition, since it's the more complicated (and useful) of the two options.

- download colinux
[http://www.colinux.org/snapshots/stable-coLinux-20050524.exe]
That's the 5/24/05 snapshot under Development Snapshots from the homepage. It's stable as far as I can tell and they've fixed a couple major bugs since stable.

- run the installer
check everything except uncheck "Root Filesystem image Download" 
install to c:\coLinux and not c:\Program Files\coLinux, since /dev paths are relative to the installation directory 
don't bother downloading and installing WinPCAP (the included TAP driver works fine) 
hit "continue anyway" for the tap driver installation 
goto Network Connections under control panel and right click on the newly installed LAN connection (TAP-Win32 Adapter V8 (colinux)). You may want to set configure->advanced->media status to "always connected". Set the ip (tcp/ip properties) to a new ip address on your lan. E.g. my hardware firewall my internet address 68.x.x.x. Then one computer gets 192.168.1.2 and the other one (wireless connection) gets 192.168.1.3. They both set the gateway field to 192.168.1.1 (configured in the hardware firewall settings). So I set the TAP adapter ip to 192.168.1.4, it's gatway to 192.168.1.1 and the dns servers to those given to me by my isp (68.x.x.x). Now select both your network connection and the TAP lan connection (ctrl-click) and then right click on one of them and select Bridge Connections. Now right-click the Network Bridge and set the tcp/ip address to the same one your internet connection uses (192.168.1.3 here). Also put in the dns servers and gateway. You may need to right-click the Network Bridge and click Disable followed by Enable to get the connection working. What happens is that your windows internet connection is still the same ip (192.168.1.3) but from within colinux, your TAP eth0 connection will use the new ip given to the TAP connection (192.168.1.4). So colinux looks like a new box on your LAN. 

- create a configuration script
first you need to find out which partitions your linux distribution uses as seen by windows. download either Dmdiag.exe from Microsoft or WinObj.zip from Sysinternals. 
[http://download.microsoft.com/download/win2000platform/WebPacks/1.00.0.1/NT5/EN-US/Dmdiag.exe]
[http://www.sysinternals.com/Files/WinObj.zip]

usage: 
dmdiag > out.txt 
winobj - 
check \GLOBAL?? for the name of your windows partitions (C:, D:). I have \Device\HarddiskVolume1 and \Device\HarddiskVolume2 for C: and D:. The next partition is probably the linux one. Goto \Device\Harddisk0 to see all the partitions on the disk. 

now create a batch script (c:\coLinux\colinux.bat) to launch colinux: 
colinux-daemon.exe -t nt mem=256 kernel=vmlinux hda6=\Device\Harddisk0\Partition3 hda7=\Device\Harddisk0\Partition4 root=/dev/hda6 eth0=tuntap cofs0=c:\coLinux 3 

This means use the standard NT console (better because you can cut&paste using the mouse), give 256mb of ram to colinux, specifies the name of the kernel, the linux partitiions, virtual ethernet adapter, and a shared directory which can be used to copy files between the colinux and windows systems. 

My linux root (/) partition is /dev/hda6 and swap partition is /dev/hda7. These correspond to \Device\Harddisk0\Partition3 and \Device\Harddisk0\Partition4 under windows (note that windows doesn't reserve a partition name for the extended partition -- my linux partitions are logical and not primary partitions). The root is given to be /dev/hda6, and you can just put tuntap for eth0, which will find the TAP connection we setup. cofs0 will be the device name of the shared folder to use to transfer files to/from windows. The 3 on the end is passed to the kernel as a kernel parameter. It means enter runlevel 3 (init 3). I need to do this since my default runlevel on boot is 5 which starts KDE, but this will crash colinux since it doesn't support X under colinux. 

- run the batch file and create some linux scripts 
run the .bat file just created and see that everything works. now create a couple of linux scripts for convenience. I created /usr/bin/colinuxnet.sh to start the network, /usr/bin/off.sh to shutdown, and a config file /etc/colinuxdisplay to set the DISPLAY environment variable. 
<nowiki>#</nowiki>!/bin/sh 
<nowiki>#</nowiki>/usr/bin/colinuxnet.sh 
ifconfig eth0 192.168.1.4 && route add default gw 192.168.1.1 

<nowiki>#</nowiki>!/bin/sh 
<nowiki>#</nowiki>/usr/bin/off.sh 
shutdown -h now 

<nowiki>#</nowiki>/etc/colinuxdisplay 
export DISPLAY=192.168.1.3:0.0 

be sure to make the shell scripts executable: chmod a+x /usr/bin/colinux.net /usr/bin/off.sh
Note that shutdown -h now is the proper way to stop colinux (don't just click the console X button). The 192.168.1.3 address is the address of my ethernet connection under windows. 0.0 specifies the first X display. 

Modify /etc/fstab to mount the cofs0 windows directory: 
<nowiki>#</nowiki>/etc/fstab 
... 
cofs0 /mnt/cofs cofs noauto,users,defaults 0 0 

Notice there is no /dev prefix. This won't automount and will be mountable by normal users (and not fsck checked). 
Create /mnt/cofs: 
mkdir /mnt/cofs 
chmod 777 /mnt/cofs (or chown username:users /mnt/cofs) 
To mount: 
mount /mnt/cofs 

You can copy both to and from c:\coLinux now. 

- setup Xming
[http://www.freedesktop.org/~ago/Xming/Xming-20050705-setup.exe]
Run the installer and don't bother to configure xlaunch. It just writes out a config file for later use but we'll just pass everything on the commandline anyway. 

create some batch files to run X: 
rem c:\coLinux\runx.bat 
@echo off 
SET DISPLAY=127.0.0.1:0.0 
SET REMOTE_HOST=192.168.1.4 
SET LOCAL_HOST=192.168.1.3 
start C:\Progra~1\Xming\Xming.exe -query %REMOTE_HOST% -nodecoration -lesspointer -from %LOCAL_HOST% -clipboard 

rem c:\coLinux\runx_multiwindow.bat 
@echo off 
SET DISPLAY=127.0.0.1:0.0 
SET REMOTE_HOST=192.168.1.4 
SET LOCAL_HOST=192.168.1.3 
start C:\Progra~1\Xming\Xming.exe -nodecoration -lesspointer -from %LOCAL_HOST% -clipboard -multiwindow -ac 

Remote host is the colinux host and local host is the windows host. You may need to forward TCP port 6000 on your firewall to allow colinux to communicate over TCP with the Xming server. The first batch script is for use with XDMCP ([http://freedesktop.org/wiki/Xming]). This will allow KDE to run under Xming. Details: 
vi /opt/kde/share/config/kdm/Xaccess 
*
This will allow access from all hosts 
vi /opt/kde/share/config/kdm/kdmrc 
[Xdmcp] Enable=true
Enables XDMCP 
vi /usr/X11/xdm/Xservers 
#:0 local /usr/X11R6/bin/X
Comment out that line so that the linux X doesn't start by default. 
vi /usr/X11/xdm/Xaccess 
*
Not sure if that's really needed. Same idea as the kdm/Xaccess though. I think this is similar to doing xhost +. 
Note that everything still starts up and runs normally if I reboot into linux through grub/lilo. These changes didn't prevent KDE or X from starting up. 

The second batch file (multiwindow) is used for when you don't want a full KDE on windows, but just want the linux consoles (alt-f4 to get multiple consoles does work) and a couple graphical linux applications to run under Xming. The -ac flag disables access control (needed since we are not using XDMCP and otherwise you get errors involving mit cookies or access denied). To test this mode: 
run colinux.bat 
run runx_multiwindow.bat 
under linux: 
. /etc/colinuxdisplay (or source /etc/colinuxdisplay) 
try: ddd (assuming it's installed on your linux distro). 

That should be all there is to it to get codeblocks running under colinux (after compiling codeblocks under linux of course). 

===Compiling from source===

The reason to want to do this is if you want to use a different kernel than the one provided by the colinux installer (currently 2.6.11). If you want to compile your own modules or add something to the kernel then this might be the way to go. If you just try to compile a new kernel and then run it under the existing colinux binaries you will get an ABI mismatch unless you compiled with their version of gcc they used (3.3.x) to cross compile the colinux binaries, so it's probably best to just setup your own cross compiler under linux and recompile the source. Note that colinux runs in kernel mode, but does not allow linux to do direct hardware access. It writes a layer and then hands hardware requests to windows. So no sound output is supported (yet) and X doesn't run under linux (yet - but you can use xmingw as described above). It's best not to modify the kernel settings from what the colinux .config file provides too much. You will need a working linux installation and an internet connection to compile from source. 

- grab the source
[http://www.colinux.org/snapshots/stable-colinux-20050524.tar.gz]

- switch to linux
I actually recompiled everything from within colinux which works fine. You could also reboot into linux. 

- extract the source and compile
I used /usr/src as the base directory. You can use /home/username if desired. 
cd /usr/src; tar xfz stable-colinux-20050524.tar.gz
cd stable-colinux-20050524

Your linux distribution needs a couple of things to be able to setup the cross compiler and compile the daemons. I needed to grab and install: 
unix2dos-2.2.src.tar.gz

The configure script will let you know about any other missing dependencies (Everything else was present here: LFS & BLFS installation). Make sure you have wget installed since all needed mingw packages are fetched with it. 

Edit bin/build-common.sh 
GCC_VERSION="3.4.4"
GCC_RELEASE="$GCC_VERSION-20050522-1"
GCC_PATCH="gcc-core-$GCC_RELEASE-src-fix1.patch"
MXML_URL=http://ftp.easysw.com/pub/mxml/1.3

Needed patch: 
<nowiki>#########</nowiki>begin gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>##########</nowiki>
<pre>
diff -urN gcc-3.4.4-20050522-1.old/gcc/crtstuff.c gcc-3.4.4-20050522-1/gcc/crtstuff.c
--- gcc-3.4.4-20050522-1.old/gcc/crtstuff.c 2005-08-18 15:46:45.000000000 -0400
+++ gcc-3.4.4-20050522-1/gcc/crtstuff.c 2005-08-18 15:53:00.000000000 -0400
@@ -602,7 +602,8 @@
#if defined (USE_EH_FRAME_REGISTRY) \
&& !__USING_SJLJ_EXCEPTIONS__
static int __EH_FRAME_END__[]
- __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME),
+/* __attribute__ ((unused, mode(SI), section(EH_FRAME_SECTION_NAME), */
+ __attribute__ ((unused, section(EH_FRAME_SECTION_NAME),
aligned(4)))
= { 0 };
static void __reg_frame_ctor (void) __attribute__ ((constructor));
</pre>
<nowiki>#########</nowiki>end gcc-core-3.4.4-20050522-1-src-fix1.patch<nowiki>#########</nowiki> 
Save the above (between the <nowiki>###</nowiki> marks) to gcc-core-3.4.4-20050522-1-src-fix1.patch 
mkdir /usr/src/download (mkdir /home/username/download if using home directory)
mv gcc-core-3.4.4-20050522-1-src-fix1.patch /usr/src/download

The patch is needed for gcc 3.4.4 to compile as a cross compiler using sjlj exceptions (dwarf exceptions don't work well under windows it seems). Otherwise you get errors about the mode(SI) statement. 

Compile: 
./configure
make
make # I got md5sum creation errors, but things resumed ok -- just type make again...
make install

This will download and install a mingw cross compiler under linux. It will then proceed to compile the windows colinux daemons and finally the colinux kernel. The kernel source will be in a subdirectory of the directory you are compiling from (/usr/src/linux-2.6.11-co or something). You can later recompile the colinux kernel by switching to this directory and doing: 
make menuconfig # set kernel options...don't change too much or it may not work with colinux
make vmlinux
make modules modules_install # installed to /lib/linux-2.6.11-co i believe

Then just move the /usr/src/linux-2.6.11-co/vmlinux kernel image to c:\coLinux (backup the old one in case). Fyi, the kernel patch they are using is under stable-colinux-20050524/patch/linux and the kernel .config file is stable-colinux-20050524/config/linux-config 
(tar xfz linux-2.6.11-12.tar.gz; cd linux-2.6.11-12; patch -p1 -i stable-colinux-20050524/patch/linux; cp stable-colinux-20050524/config/linux-config .config) 
to start from fresh kernel.org sources. note that only up to 2.6.11-X is working. A patch is available on colinux.org for 2.6.12 but I haven't tried it. 

Btw the make install above just installs to a subdirectory (dist/). It won't touch /usr or /usr/local. Once everything completes you can just tar the dist directory and copy to your windows directory: 
tar cfz dist.tar.gz dist
mount /mnt/cofs
mv dist.tar.gz /mnt/cofs
Winrar supports extracting from .tar.gz and .tar.bz2 archives (7zip does too I believe).
That's all that should be required to build colinux from source and compile custom colinux kernels.
Make sure you use the same gcc major version (gcc 3.4.x here) to compile both the daemons and kernel (the automatic kernel build run by the colinux install scripts does this by default).

Tips'n'Tricks

2005-08-25T12:49:47Z

Grv:

====[[Personalities]]====
====[[Fixing Internal Errors]]====
====[[Setting the WX_VER variable]]====
====[[Running under colinux]]====

Various development tips

2005-08-24T10:15:34Z

Grv: /* JIT debugging */

This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

====Using Code::Blocks' global configuration====

There are many cases where you may need to have persistent configuration values. For example, you may be writing a new plugin (or extend an existing).
The global configuration object is a singleton, meaning that only one exists for the program's lifetime. It can be accessed like this:

<pre>#include <configmanager.h>
...
ConfigManager::Get()->Read(...); // "read" example
ConfigManager::Get()->Write(...); // "write" example</pre>

As you can see, all that's needed is to include the relevant header file. To access the configuration then, you use the static member function ConfigManager::Get() which returns a ConfigManager object (the only). ConfigManager descends from wxConfigBase and so it inherits all its public methods for working with configuration files.

Let's see a real world example. Suppose you 're writing a new plugin and it needs to keep a directory path in a configuration value.
To write the configuration value, possibly prior to exiting (or after its imaginary configuration window is closed), do this:
<pre>// somehow set pluginDir to the value you want
wxString pluginDir;
// write it in the global configuration
ConfigManager::Get()->Write("/new_plugin/directory", pluginDir);
</pre>
And to read the saved value, do this:
<pre>// write it in the global configuration
// if we never written the value before, "default" will be returned
wxString pluginDir = ConfigManager::Get()->Read("/new_plugin/directory", "default");
</pre>
In the above examples, the "/new_plugin" part of the string should be replaced with something unique for the plugin you 're writing. For example, the compiler plugin uses "/compiler_gcc", the internal editor class uses "/editor" and so on.
That's how simple is to use Code::Blocks' global configuration :)

One more thing: if you want your plugin's configuration to be included in the import/export list in "Settings->Import/export configuration", just add in your plugin's constructor(s) the following:
<pre>ConfigManager::AddConfiguration(m_PluginInfo.title, "/new_plugin");</pre>
This line will add your plugin in the import/export list. Neat huh?

====JIT debugging====

cd C:\mingw\bin
drmingw -i -v
this will install drmingw as the jit debugger (drmingw -u to later uninstall)
(windbg from the platform sdk can be installed as the jit debugger with windbg -I
but it doesn't support gcc debug symbols. it does support vc5/6/7 .pdb files
generated by vc++ toolkit, providing true source level debugging)

to test:
- create a win32 project using the gcc compiler as default
- place
__asm("int3");
somewhere in the code
- compile & run
gcc -g

- create a win32 project using vc++ toolkit compiler as default
- place
__asm{ int 3 };
somewhere in the code
- compile & run
cl /Zi
link /debug

Various development tips

2005-08-23T13:04:07Z

Grv: /* Using Code::Blocks' global configuration */

This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

====Using Code::Blocks' global configuration====

There are many cases where you may need to have persistent configuration values. For example, you may be writing a new plugin (or extend an existing).
The global configuration object is a singleton, meaning that only one exists for the program's lifetime. It can be accessed like this:

<pre>#include <configmanager.h>
...
ConfigManager::Get()->Read(...); // "read" example
ConfigManager::Get()->Write(...); // "write" example</pre>

As you can see, all that's needed is to include the relevant header file. To access the configuration then, you use the static member function ConfigManager::Get() which returns a ConfigManager object (the only). ConfigManager descends from wxConfigBase and so it inherits all its public methods for working with configuration files.

Let's see a real world example. Suppose you 're writing a new plugin and it needs to keep a directory path in a configuration value.
To write the configuration value, possibly prior to exiting (or after its imaginary configuration window is closed), do this:
<pre>// somehow set pluginDir to the value you want
wxString pluginDir;
// write it in the global configuration
ConfigManager::Get()->Write("/new_plugin/directory", pluginDir);
</pre>
And to read the saved value, do this:
<pre>// write it in the global configuration
// if we never written the value before, "default" will be returned
wxString pluginDir = ConfigManager::Get()->Read("/new_plugin/directory", "default");
</pre>
In the above examples, the "/new_plugin" part of the string should be replaced with something unique for the plugin you 're writing. For example, the compiler plugin uses "/compiler_gcc", the internal editor class uses "/editor" and so on.
That's how simple is to use Code::Blocks' global configuration :)

One more thing: if you want your plugin's configuration to be included in the import/export list in "Settings->Import/export configuration", just add in your plugin's constructor(s) the following:
<pre>ConfigManager::AddConfiguration(m_PluginInfo.title, "/new_plugin");</pre>
This line will add your plugin in the import/export list. Neat huh?

====JIT debugging====

cd C:\mingw\bin
drmingw -i -v
this will install drmingw as the jit debugger (drmingw -u to later uninstall)
(windbg from the platform sdk can be installed as the jit debugger with windbg -I
but it doesn't support gcc gcc debug symbols. it does support vc5/6/7 .pdb files
generated by vc++ toolkit, providing true source level debugging)

to test:
- create a win32 project using the gcc compiler as default
- place
__asm("int3");
somewhere in the code
- compile & run
gcc -g

- create a win32 project using vc++ toolkit compiler as default
- place
__asm{ int 3 };
somewhere in the code
- compile & run
cl /Zi
link /debug

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-23T05:49:15Z

Grv: /* Building codeblocks from source (using makefile) */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
update.bat
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-23T04:57:46Z

Grv: /* Building codeblocks from source (using makefile) */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6 clean
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
update.bat
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-23T04:54:22Z

Grv: /* Building codeblocks from source */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source (using makefile)====

Codeblocks can be used to build the source but here is how to build using just makefiles.

<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
update.bat
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-23T04:42:26Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 

====Building codeblocks from source====
<pre>
build wxWidgets-2.6.1 dll using mingw32
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb clean
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb
copy C:\wxWidgets-2.6.1\lib\gcc_dll to C:\wxWidgets-2.6.1\lib\gcc_dllUnicode (copy since wxDockIt expects gcc_dll to exists)
checkout CVS source codeblocks module (used VERSION_1_0 branch)
(beware path lengths - best to checkout to root directory - c:\)
download http://prdownloads.sourceforge.net/wxextended/wxDockIt_2.1.zip?download
extract wxDockIt to codeblocks\src\src
patch codeblocks\src\src\wxDockit\build\msw\makefile.gcc
change "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_adv -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX)_xml -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX)_core -lwxbase$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
to "$(CXX) -shared -fPIC -o $@ $(WXDOCKIT_DLL_OBJECTS) $(LDFLAGS) -mthreads -L$(WX_DIR)$(__WXLIBPATH_FILENAMES) -L..\..\$(__WXDOCKIT_OUTPUT_FOLDER_FILENAMES_1) $(__DEBUGINFO) -mthreads -Wl,--out-implib,..\..\lib\gcc_dll\libwxdockit$(WXLIBPOSTFIX).a -lwxmsw$(WX_VERSION)$(WXLIBPOSTFIX) -lwxtiff$(WX3RDPARTLIBPOSTFIX) -lwxjpeg$(WX3RDPARTLIBPOSTFIX) -lwxpng$(WX3RDPARTLIBPOSTFIX) -lwxzlib$(WX3RDPARTLIBPOSTFIX) -lwxregex$(WXLIBPOSTFIX) -lwxexpat$(WX3RDPARTLIBPOSTFIX) -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32 -lodbc32"
compile wxDockIt
cd codeblocks\src\src\wxDockit\build\msw
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26 clean
mingw32-make -f makefile.gcc WX_DIR=C:\wxWidgets-2.6.1 WX_SHARED=1 WX_DEBUG=0 WX_UNICODE=1 WX_VERSION=26
move codeblocks\src\src\wxDockit\build\msw\gcc_dll to codeblocks\src\src\wxDockit\build\msw\gcc_dllUnicode
edit codeblocks\src\src\Makefile.wx2.6
change WX_DIR=C:/Devel/wxWindows-2.6.1 to WX_DIR=C:/wxWidgets-2.6.1
change WX_CFG=NonUnicode to WX_CFG=Unicode
global search+replace: replace " -lwxmsw26" with " -lwxmsw26u"
global search+replace: replace "/msw" with "/mswu"
replace "-Lsrc/wxDockit/lib" with "-Lsrc/wxDockit/lib/gcc_dll$(WX_CFG)"
replace "..\wxDockit\lib\libwxdockit.a" with "src\wxDockit\lib\gcc_dll$(WX_CFG)\libwxdockitu.a"
edit C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\mswu\wx\setup.h
change "#define wxUSE_UNICODE 0" to "#define wxUSE_UNICODE 1"
start->run->cmd
cd codeblocks\src
mingw32-make -f Makefile.wx2.6
download ftp://ftp.info-zip.org/pub/infozip/MSDOS/zip231x.zip (infozip)
put zip.exe in some directory in your PATH (e.g. C:\MinGW\bin)
update.bat
copy C:\wxWidgets-2.6.1\lib\gcc_dllUnicode\wxmsw26u_gcc_cb.dll to codeblocks\src\output\wxmsw26u_gcc_cb.dll and codeblocks\src\devel\wxmsw26u_gcc_cb.dll
copy src\src\wxDockit\lib\gcc_dllUnicode\wxdockitu.dll to and codeblocks\src\output\wxdockitu.dll and codeblocks\src\devel\wxdockitu.dll
output\CodeBlocks.exe
</pre>

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-23T04:08:40Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 

cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 

 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


stc is no longer needed for latest codeblocks (cvs version) which uses wxscintilla: 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 


cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 

 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release

Installing Code::Blocks from source on Linux

2005-08-21T06:46:38Z

Grv: /* wxWidgets 2.6.1 build */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
su
make install
make -C contrib/src/stc install
exit

add /opt/wx/2.6 to /etc/ld.so.conf (nano /etc/ld.so.conf)
ldconfig

That's it. Now the linker will look in /opt/wx/2.6 for wx libraries and you will have a monolithic shared library unicode build.

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Installing Code::Blocks from source on Linux

2005-08-21T05:00:16Z

Grv: /* wxWidgets 2.6.1 build */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-xrc \
--enable-monolithic \
--enable-unicode
make
make -C contrib/src/stc
make -C contrib/src/xrc
su
make install
make -C contrib/src/stc install
make -C contrib/src/xrc install
exit

add /opt/wx/2.6 to /etc/ld.so.conf (nano /etc/ld.so.conf)
ldconfig

That's it. Now the linker will look in /opt/wx/2.6 for wx libraries and you will have a monolithic shared library unicode build.

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Installing Code::Blocks from source on Linux

2005-08-21T04:36:37Z

Grv: /* wxGTK-2.4.2 installation */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

====wxWidgets 2.6.1 build====

In case you want to use wxGTK 2.6.1 instead.
Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-monolithic \
--enable-unicode || exit 1
make || exit 1
make -C contrib/src/stc || exit 1
su
make install
make -C contrib/src/stc install
exit

add /opt/wx/2.6 to /etc/ld.so.conf (nano /etc/ld.so.conf)
ldconfig

That's it. Now the linker will look in /opt/wx/2.6 for wx libraries and you will have a monolithic shared library unicode build.

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Installing Code::Blocks from source on Linux

2005-08-21T04:35:04Z

Grv: /* wxWidgets 2.6.1 build */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

Installing Code::Blocks from source on Linux

2005-08-21T04:34:30Z

Grv: /* Building Code::Blocks */

These are instructions on how to build Code::Blocks under Linux. I 've ran and verified this procedure to work under SuSE 9.2 and Fedora Core 3. These instructions should work for all Linux distros, as we 'll be installing from sources.

===Prerequisites===

In order to sucesfully compile Code::Blocks, the wxWidgets (wxGTK-2.4.2) cross-platform UI library must be installed. In this document, it is not assumed that it is already installed in your system and instructions are given on how to download, build and install it.
What is '''not''' covered here, is the wxWidgets prerequisites. The most important being GTK2, of course!
Let me stress it here, while it's early: GTK2 is required, not GTK1, for Code::Blocks to be operational.

All the instructions below, assume an existing directory named <tt>~/devel</tt>. If you 'll be using a different one, adjust the path to match.
As a first step create this directory:

<pre>mkdir ~/devel</pre>

===wxGTK-2.4.2 installation===
====Getting wxGTK-2.4.2====

Visit the [http://www.wxwidgets.org wxWidgets] web site. Click on the "Download" button in the sidebar on the left side of the page. You want to download the file named wxGTK-2.4.2.tar.gz (or wxGTK-2.4.2.tar.bz2). Save the file in <tt>~/devel</tt>.

====Uncompressing the wxGTK sources====

After the download finishes, switch to <tt>~/devel</tt>:

<pre>cd ~/devel</pre>

Now, untar the wxGTK sources:

<pre>tar zxf wxGTK-2.4.2.tar.gz</pre>

or

<pre>tar jxf wxGTK-2.4.2.tar.bz2</pre>

depending on which file you downloaded.

=====Patching wxGTK=====

Most newer distros provide gtk2.4.x. Although wxGTK will compile using this gtk version, applications using this wxGTK will not compile succesfully. This happens because some internal function names were changed in later gtk versions and wxGTK-2.4.2, at the time of its release, did not account for these changes.
If your distro uses this gtk version, you will need to patch the wxGTK sources before the build process.
You can get the required patch from here (TODO: add link), or create a new file and put the following in it:

<pre>//sgl/devel/grimoire/x11-toolkits/wxGTK/gtk-2.4-fix.patch#1 - add change 30747 (text)
diff -Nur wxGTK-2.4.2/src/gtk/menu.cpp wxGTK-2.4.2-fix/src/gtk/menu.cpp
--- wxGTK-2.4.2/src/gtk/menu.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/menu.cpp 2004-03-29 14:53:34.000000000 +0200
@@ -30,13 +30,13 @@
#ifdef __WXGTK20__
#include <glib-object.h>

- #define gtk_accel_group_attach(g, o) _gtk_accel_group_attach((g), (o))
- #define gtk_accel_group_detach(g, o) _gtk_accel_group_detach((g), (o))
+ #define gtk_accel_group_attach(g, o) gtk_window_add_accel_group((o), (g))
+ #define gtk_accel_group_detach(g, o) gtk_window_remove_accel_group((o), (g))
#define gtk_menu_ensure_uline_accel_group(m) gtk_menu_get_accel_group(m)

- #define ACCEL_OBJECT GObject
+ #define ACCEL_OBJECT GtkWindow
#define ACCEL_OBJECTS(a) (a)->acceleratables
- #define ACCEL_OBJ_CAST(obj) G_OBJECT(obj)
+ #define ACCEL_OBJ_CAST(obj) GTK_WINDOW(obj)
#else // GTK+ 1.x
#define ACCEL_OBJECT GtkObject
#define ACCEL_OBJECTS(a) (a)->attach_objects
diff -Nur wxGTK-2.4.2/src/gtk/settings.cpp wxGTK-2.4.2-fix/src/gtk/settings.cpp
--- wxGTK-2.4.2/src/gtk/settings.cpp 2003-09-21 13:31:57.000000000 +0200
+++ wxGTK-2.4.2-fix/src/gtk/settings.cpp 2004-03-29 15:15:35.000000000 +0200
@@ -340,8 +340,8 @@
}
else
{
- const gchar *font_name =
- _gtk_rc_context_get_default_font_name(gtk_settings_get_default());
+ gchar *font_name;
+ g_object_get(gtk_settings_get_default(), "gtk-font-name", &font_name, NULL);
g_systemFont = new wxFont(wxString::FromAscii(font_name));
}
gtk_widget_destroy( widget );
</pre>
(''Patch copied from http://www.flamerobin.org/dokuwiki/doku.php?id=wiki:wxgtkpatch.'')

Save the file as <tt>~/devel/gtk-2.4-fix.patch</tt> and apply it by issuing:

<pre>cd ~/devel
patch -Np0 -i gtk-2.4-fix.patch</pre>

Now we can build wxGTK!

====Building wxGTK-2.4.2====

Issue the following commands to build wxGTK-2.4.2:

<pre>cd ~/devel/wxGTK-2.4.2
./configure --enable-gtk2
make
</pre>

If something fails when you run the configure command, some wxGTK prerequisite is probably missing. Read through the output and figure out what's missing.
If all's gone well, after 10 to 30 minutes (depending on your machine), the wxGTK library should be ready. Time to install it, system-wide:

<pre>su -c "make install"</pre>

The above command will ask you for the root's password (you are working as a regular user, aren't you?) and then it will install the library and the needed development files in your system.

The next step is to build STC: the wxWidgets wrapper for Scintilla (the editor). This is located in the contrib subdir hierarchy. To do this, issue the following commands:

<pre>cd contrib/src/stc
make
su -c "make install"</pre>

When you 're done, STC will have been installed too. All that's left, is the XRC library which is used to load XML resources. Type the following:

<pre>cd ../xrc
make
su -c "make install"</pre>

NOTE: ''The Fedora Core 3 installation I tested this procedure, did not have /usr/local/lib in the library search path. I had to manually add /usr/local/lib in /etc/ld.so.conf as root and then issue ldconfig, as root again.''

That's it! If you reached here, congratulations! You 've built and installed wxGTK in your system.
You 're now ready to download and build Code::Blocks - i.e. the easy part :)

===Code::Blocks installation===

====Downloading Code::Blocks====

You can get Code::Blocks source code in one of two ways:
* Download the latest source package, or
* Get the latest sources from the CVS repository.
Both methods, are described below.

=====Downloading the latest source package=====

Go to the Code::Blocks [https://www.codeblocks.org web site] and download the latest source package. This would be the " Code::Blocks IDE version 1.0-finalbeta source code (tarball)" codeblocks-1.0-finalbeta.tar.gz.
Save this file in <tt>~/devel</tt> and then untar it:
<pre>cd ~/devel
tar zxf codeblocks-1.0-finalbeta.tar.gz</pre>
This will create the directory <tt>~/devel/codeblocks-1.0-finalbeta</tt>.
Change to the source code directory, by issuing the following command:
<pre>cd codeblocks-1.0-finalbeta/src</pre>

=====Getting the latest sources from CVS=====

For the following to work, you need to have the <tt>cvs</tt> command line client installed on your system.
First you need to login to the CVS server:

<pre>cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks login</pre>

When asked for a password, press enter.
Now, just checkout (i.e. download) the sources from the repository:

<pre>cd ~/devel
cvs -d :pserver:anonymous@cvs.sourceforge.net:/cvsroot/codeblocks co codeblocks</pre>

This will create the directory <tt>codeblocks</tt>.
Change to the source code directory, by issuing the following command:

<pre>cd codeblocks/src</pre>

====Building Code::Blocks====

To build Code::Blocks all you have to do now is type:

<pre>make -f Makefile.unix</pre>

This will build everything: the application and the plugins. The final step is to update the working environment for your system:

<pre>make -f Makefile.unix update</pre>

The following notes about converting the line endings does '''not''' apply to the CVS Version! The "update" script included there works just fine.

'''Important note:''' Don't run that final make yet! The "update" script seems to be using Dos character encoding, which will result in its failure to run on Linux. To fix this, use dos2unix:

To install it in Gentoo, do:

# emerge -av dos2unix

In Debian and Ubuntu, do (as root, or using sudo etc.):

# apt-get install sysutils

This will install dos2unix. Now we are ready to convert the script.
# dos2unix -n update update.unix
# chmod +x update.unix
# ./update.unix
The first line converts the script character encoding, the second makes it executable and the third runs it. This trick is from a forum post by ilkapo.

OK. Now that the update script is converted to unix format, you can run the final make:

<pre>make -f Makefile.unix update</pre>

If everything's gone well, congratulations! You should be able to launch Code::Blocks by running the generated <tt>run.sh</tt> script in the <tt>output</tt> subdir:

<pre>output/run.sh</pre>

This script can be ran from anywhere in your system so, yes, you can make a shortcut to it on your desktop ;)

Enjoy!

====wxWidgets 2.6.1 build====

Here we will create a seperate build directory instead of building from the src directory, so that we can easily rebuild with different options (unicode / ansi, monolithic / many libs, etc).

The documentation says the default is for gtk2 to use unicode and wx > 2.5 to build as a monolithic library. This doesn't appear to be the case, so these flags are passed to configure.

mkdir build_gtk2_shared_monolithic_unicode
cd build_gtk2_shared_monolithic_unicode
../configure --prefix=/opt/wx/2.6 \
--enable-monolithic \
--enable-unicode || exit 1
make || exit 1
make -C contrib/src/stc || exit 1
su
make install
make -C contrib/src/stc install
exit

add /opt/wx/2.6 to /etc/ld.so.conf (nano /etc/ld.so.conf)
ldconfig

That's it. Now the linker will look in /opt/wx/2.6 for wx libraries and you will have a monolithic shared library unicode build.

FAQ

2005-08-16T16:36:33Z

Grv: /* I can't compile a multithreaded app with VC Toolkit! Where are the libraries? */

= General =

== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==

Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)

== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==

Since version 1.0-beta5, no it is not. Code::Blocks works with GNU "make" [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to "Project/Build options", switch to the "Other" tab and select the build method you prefer.

== What licence is Code::Blocks released under? ==

GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])

= Compiling =

== What compiler can I use with Code::Blocks? ==

Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.

As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.

== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==

A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==

''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''

You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under "Settings/Configure plugins/Compiler" in the "Programs" tab...
Second, you have to add two additional compiler (include) dirs. Go to "Settings/Configure plugins/Compiler" and in the "Compiler dirs" tab add "dev-cpp\include\c++" and "dev-cpp\include\c++\mingw32" (substituting "dev-cpp" with the actual dev-cpp installation folder).

== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==

BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.

== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==

Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a "Custom Makefile" checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.
Also make sure that "GNU make" is the selected build method for the specific compiler.

== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==

Click on "Project/Build options" and select the compiler you want for your project/target.

== When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ==

You need to add WXUSINGDLL in "Project->Build options->Compiler definitions" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==

sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download MinGW :)

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (VCT3)
LIBCPMTD.LIB Multithreaded, static link (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps.

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

== Where are the libraries for the OpenGL / SDL / etc. projects? ==

They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.
In common terms, "batteries not included" :)

== Is it possible to use Visual C++ 6.0 with Code::Blocks? ==

FAQ

2005-08-16T14:12:53Z

Grv: /* I can't compile a multithreaded app with VC Toolkit! Where are the libraries? */

= General =

== Is it possible to integrate the win32-help as in dev-cpp, to get help on the items under the caret? ==

Integration of the win32 API helpfile should be a no-brainer. Someone could just write a really simple plugin and, upon invocation (through a shortcut possibly), look at the word under the cursor and invoke windows help... If you think you 're up to the task, I can help you with all the info you need. If not, I could write it myself but no promises on a release date ;)

== Launching for the first time, Code::Blocks tells me I need to install GNU make. Is this necessary on a Windows system? ==

Since version 1.0-beta5, no it is not. Code::Blocks works with GNU "make" [http://www.mingw.org/download.shtml (here)] or without it (default). To choose the build method, go to "Project/Build options", switch to the "Other" tab and select the build method you prefer.

== What licence is Code::Blocks released under? ==

GNU General Public License 2 ([http://www.gnu.org/licenses/gpl.txt GPL])

= Compiling =

== What compiler can I use with Code::Blocks? ==

Code::Blocks philosophy is to be able to use any compiler on earth! Well, almost.

As a matter of fact it largely depends on the used compiler plugin. The one provided with the default Code::Blocks installation, supports GNU GCC (MinGW/Cygwin), MS Visual C++ Free Toolkit 2003, Borland's C++ Compiler 5.5 and DigitalMars Free Compiler.

== I imported a MSVCToolkit project/workspace, but Code::Blocks insists on trying to use GCC. What's wrong? ==

A little documentation problem ^^;. The "default compiler" is usually GCC, so when you imported it with "the default compiler", you told it to use GCC. To fix this situation, go to "Project", "Build Options" and select VC++ Toolkit as your compiler.

== I 'm using gcc compiler from an existing dev-cpp installation. How can I make it work? ==

''As of version 1.0-beta6, if a default MinGW installation is not detected, a Dev-C++ installation is checked for and is used if detected.''

You need to take two steps. First, set the compiler master path to the dev-cpp folder. It's under "Settings/Configure plugins/Compiler" in the "Programs" tab...
Second, you have to add two additional compiler (include) dirs. Go to "Settings/Configure plugins/Compiler" and in the "Compiler dirs" tab add "dev-cpp\include\c++" and "dev-cpp\include\c++\mingw32" (substituting "dev-cpp" with the actual dev-cpp installation folder).

== I just installed Code::Blocks Beta4 and I can't compile anything with BCC. ==

BCC is not supported 100% yet, unfortunately... The next release (namely 1.0-beta6) should address all BCC issues.

== My project should be compiled with a custom makefile. Is it possible with Code::Blocks? ==

Yes, as of version 1.0-beta4 it is supported. Go to project options and you 'll notice a "Custom Makefile" checkbox. If you check this, Code::Blocks will not create another Makefile for compiling but instead always use this Makefile. You have to understand, though, that it is your sole responsibility to keep this Makefile up to date.
Also make sure that "GNU make" is the selected build method for the specific compiler.

== I have downloaded MS VC++ Toolkit 2003 for a compiler. How do I tell Code::Blocks that it is my compiler? ==

Click on "Project/Build options" and select the compiler you want for your project/target.

== When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? ==

You need to add WXUSINGDLL in "Project->Build options->Compiler definitions" and rebuild your project (or create a new project and use the "Using wxWidgets DLL" project option which adds "-DWXUSINGDLL" to Project->Build options->Other options).
If you were using 1.0-finalbeta and were trying to build a statically linked wxWidgets project, the cause of the problem was some faulty templates. But that's fixed now.

== I can't compile a multithreaded app with VC Toolkit! Where are the libraries? ==

sorry, no fix for your problem...

Your problem doesn't come from CodeBlocks. It exists, because the free VC toolkit (VCTK) doesn't provide all the libraries and tools which are coming with Visual C++ (VC) which isn't free, unfortunately.

Try buying a full-fledged VC++, or even better, download MinGW :)

The libraries that can be obtained free of charge are:

Paths:
(VCT3) Visual C++ Toolkit 2003 - C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
(PSDK) Platform SDK - C:\Program Files\Microsoft Platform SDK\Lib
(NSDK) .NET 1.1 SDK - C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

C runtime libs:
LIBC.LIB Single-threaded, static link (VCT3, NSDK)
LIBCMT.LIB Multithreaded, static link (VCT3, NSDK)
MSVCRT.LIB Multithreaded, dynamic link (import library for MSVCR71.DLL) (NSDK)
LIBCD.LIB Single-threaded, static link (debug) (VCT3, NSDK)
LIBCMTD.LIB Multithreaded, static link (debug) (NSDK)
MSVCRTD.LIB Multithreaded, dynamic link (import library for MSVCR71D.DLL) (debug) (NSDK)

C++ libs:
LIBCP.LIB Single-threaded, static link (VCT3, PSDK)
LIBCPMT.LIB Multithreaded, static link (VCT3)
MSVCPRT.LIB Multithreaded, dynamic link (import library for MSVCP71.dll) (none)
LIBCPD.LIB Single-threaded, static link (VCT3)
LIBCPMTD.LIB Multithreaded, static link (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (none)

Try setting the library linker directories to:
C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib
C:\Program Files\Microsoft Platform SDK\Lib
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib
in that order.

The ones listed as (none) above are actually present in the IA64 and AMD64 subdirectories of the PSDK lib directory. Not sure if these would work on 32-bit windows, however, they may if they are
meant to work in 32-bit compatibility mode on the 64-bit processors. Worth a try. Otherwise, you
can link statically to the C++ library instead of using MSVCP71.dll. If you really want to link against MSVCP71.dll you can try to create MSVCP71.LIB from the dll using lib.exe and sed. Search google for "exports.sed" for detailed steps. You may also want to consider the Visual C++ Express Beta 2005 download @ http://msdn.microsoft.com/express instead of VCT3.

See also: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_c_run.2d.time_libraries.asp

== Where are the libraries for the OpenGL / SDL / etc. projects? ==

They're not bundled. The templates were provided for your convenience, but you need to download the libraries on your own.
In common terms, "batteries not included" :)

== Is it possible to use Visual C++ 6.0 with Code::Blocks? ==

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T20:05:02Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1: If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly make lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2: If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3: Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g.
release version = libc.lib
debug version = libcd.lib
multithreaded release version = libmt.lib
etc. (not sure about the 'i' or 'p' variants) 
The above link statically.
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T20:04:39Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1: If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly make lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2: If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3: Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g.
release version = libc.lib
debug version = libcd.lib
multithreaded release version = libmt.lib
etc. (not sure about the 'i' or 'p' variants)
The above link statically.
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T20:03:15Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1: If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly make lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2: If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3: Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g. 
release version = libc.lib 
debug version = libcd.lib 
multithreaded release version = libmt.lib 
etc. (not sure about the 'i' or 'p' variants) 
The above link statically. 
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T20:02:01Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1: If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly make lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2: If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3: Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g.
release version = libc.lib
debug version = libcd.lib
multithreaded release version = libmt.lib
etc. (not sure about the 'i' or 'p' variants)
The above link statically.
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T20:00:05Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1: If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly makes lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2: If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3: Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g.
release version = libc.lib
debug version = libcd.lib
multithreaded release version = libmt.lib
etc. (not sure about the 'i' or 'p' variants)
The above link statically.
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T19:59:40Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-H1- If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly makes lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-H2- If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-H3- Note that the VC++ Toolkit itself does not come with debugging versions of the .lib library files. For these you should also download the .NET 1.1 SDK and add the linker path as in H2 above.

The MS naming convention for some their libraries seems to be e.g.
release version = libc.lib
debug version = libcd.lib
multithreaded release version = libmt.lib
etc. (not sure about the 'i' or 'p' variants)
The above link statically.
dynamic multithreaded release version (uses a dll) = msvcrt.lib

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-09T04:32:44Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-- If the project cannot find "lib.exe" or "cvtres.exe" then use the ones in C:\Program Files\Microsoft Platform SDK\Bin\win64. They correctly makes lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-- If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-09T04:30:31Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 
cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 
 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 
 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-08T20:13:55Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

-- If the project cannot find "lib.exe" then use the one in C:\Program Files\Microsoft Platform SDK\Bin\win64. It correctly makes lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

-- If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

-- If the project you are compiling has a resource (.rc) file then you will need cvtres.exe when using the VC++ Toolkit 2003. Goto support.microsoft.com, and search the KB for "cvtres1.exe". Should come up with "FIX: Visual Studio 97 SP3 Installs Incorrect Cvtres.exe" (187280). Download cvtres1.exe, rename to cvtres.exe and place this in a directory in the path, e.g. C:\PlatformSDK\Bin.

Both the VC++ Toolkit 2003 and the platform SDK omit this utility.

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-08T20:11:09Z

Grv: /* Compiling Hints */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

If the project cannot find "lib.exe" then use the one in C:\Program Files\Microsoft Platform SDK\Bin\win64. It correctly makes lib files for 32-bit windows. So add to the END of Programs->Additional paths under "Compiler Settings":
C:\Program Files\Microsoft Platform SDK\Bin\win64

If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

If the project you are compiling has a resource (.rc) file then you will need cvtres.exe when using the VC++ Toolkit 2003. Goto support.microsoft.com, and search the KB for "cvtres1.exe". Should come up with "FIX: Visual Studio 97 SP3 Installs Incorrect Cvtres.exe" (187280). Download cvtres1.exe, rename to cvtres.exe and place this in a directory in the path, e.g. C:\PlatformSDK\Bin.

Both the VC++ Toolkit 2003 and the platform SDK omit this utility.

Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE

2005-08-08T20:07:56Z

Grv: /* Setting Platform SDK */

==Microsoft Visual C++ Toolkit 2003 - Overview==
'''Microsoft Visual C++ Toolkit 2003''' (or VCToolkit, MVCT) is freely available and free for commercial use minimalistic compiler suite released by Microsoft. It consists of high quality C/C++ optimizing compiler (VC 7.1, which is much better than old VC++ 6.0) and linker, but obviously comes without IDE, thus making management of medium and larger projects nearly impossible. Luckily, it's where Code::Blocks IDE with its multi-compiler integration feature comes in handy! This tutorial will cover process of integrating these two incredible pieces of software - VCToolkit and Code::Blocks IDE.

==What does VC Toolkit include, and what does it not?==

According to '''readme.txt''' shipped with package, Microsoft Visual C++ Toolkit 2003 '''does include''':

* Visual C/C++ compiler and linker, same as these shipped with Visual Studio .NET 2003 Professional!

* C Runtime Library and the C++ Standard Library, including the Standard Template Library. These are the same static-link libraries included with Visual Studio.

* Microsoft .NET Framework Common Language Runtime. Visual C++ can optionally build applications that run on the Common Language Runtime (CLR).

* Code samples. The toolkit includes four samples designed to showcase the powerful new features of the 2003 version, including new optimization capabilities, features to improve code-security and robustness, enhanced ISO C++ standards support, and the ability to use the .NET Framework library and target the CLR.

According the same source, MSVT '''does NOT include''':

* Various development tools shipped only with commercial Visual Studio IDE - like debugger, profiler, etc.

* Microsoft Foundation Class (MFC) and Active Template Libraries (ATL).

* Advanced developer tools, including compilers and tools for developing using other languages like Visual Basic and C#.

==Packages needed==
In order to set up '''Code::Blocks IDE''' with '''Microsoft Visual C++ Toolkit 2003''' you need following packages:

* '''Code::Blocks IDE''' itself.
: You can grab the latest version of '''Code::Blocks IDE''' in download section of [http://codeblocks.org/downloads.shtml Code::Blocks homepage] or at [http://sourceforge.net/project/showfiles.php?group_id=126998 project's site] at [http://sourceforge.net Source Forge]. (~3 MB)

* '''Microsoft Visual C++ Toolkit 2003''' compiler suite
: This package contains fully functional Visual C++ 7.1 compiler suite, which is '''free for commercial use'''. It contains minimalistic set of tools and C/C++ header and library files required for basic application development. You can download latest release of MVCT from [http://www.microsoft.com/downloads/details.aspx?FamilyId=272BE09D-40BB-49FD-9CB0-4BFA122FA91B&displaylang=en Microsoft's website]. (~31.4 MB)

* '''Platform SDK'''
: This package provides a whole bunch of useful stuff not only for Visual C++ compiler users, but generally, any Windows developer - it includes extensive headers and libraries, as well as tools (like resource compiler, '''not included''' in basic VCToolkit package), documentation and samples.

: There are three ways to obtain '''Platform SDK''':
<blockquote>
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=a55b6b43-e24f-4ea3-a93e-40c0ec4f68e5&DisplayLang=en Platform SDK Web Install]
: '''Platform SDK''' in its most compact shape - download tiny (~1.2 MB), compact installer, which will guide you through rest of the installation process (online). You will also decide yourself which components you want to install.

* [http://www.microsoft.com/downloads/details.aspx?FamilyID=eba0128f-a770-45f1-86f3-7ab010b398a3&DisplayLang=en Platform SDK Full Download] (beware, it's HUGE!)
: Complete '''Platform SDK''', with all things you will ever need or not. Huge, self-extracting *.cab installer.

* [http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92&displaylang=en Platform SDK ISO Install] (beware, it's HUGE!)
: Same as above, but you get it as *.img (CD image) file.
</blockquote>
: Choose the most convinient way for yourself.

==Okay, so let's proceed with installation:==

Basically, it doesn't really matter what you install first. The most convinient way, however, is to have compiler suite installed before running '''Code::Blocks IDE''' for the first time. In such case, C::B will likely autodetect available compilers during its startup, and set up everything correctly. If you have some of the components already installed, just skip that part.

===Installing Microsoft Visual C++ Toolkit 2003===
Simply run '''VCToolkitSetup.exe''' and installation process will start. Select a path you want to install MVCT to. This tutorial assumes you installed it to:
C:\VCToolkit2003\
When installation is done, navigate to the MSVT directory ("C:\VCToolkit2003\") and run vcvars32.bat. It will set up enviromental variables.

'''Note:''' Installing VCToolkit requires .NET Framework. Most likely you already have it. If not, setup will trigger .NET Framework installation and proceed it smoothly on older Windows NT systems (NT & 2000), newer ones (XP and above) already have it. This one will, however, fail if you have Windows 9x/Me. In order to install VCToolkit on these machines you need to install .NET Framework manually, preventing setup from triggering malfunctioning procedure. [TODO: it would be great if someone who actually tried it describe it somewhere here]

===Installing Platform SDK===
In this tutorial we will follow '''Platform SDK Web Install'''. Download (links above) and run '''PSDK-x86.exe''', '''PSDK-amd64.exe''' or '''PSDK-ia64.exe''' (according your PCs architecture). Select a path you want to install Platform SDK to. We will use
C:\PlatformSDK\
If you select '''custom installation''', you will have to select which components you want to install. I didn't dare to run '''typical installation''', because it presumably downloads & installs everything (= hundreds of megabytes). Selecting components may be a little tricky, most of them are related to various Microsoft technologies, and if you are using any of them in your applications, you should install these features here, otherwise your programs will likely fail to compile and/or link correctly. You can update your Platform SDK installation at any time.

When installation is finished, navigate to the Platform SDK directory ("C:\PlatformSDK\") and run '''SetEnv.Cmd'''.

===Installing Code::Blocks IDE===
Simply run setup file, and select a path where you want it to be installed.

'''Note:''' some of the plugins are '''MinGW''' specific (GDB plugin, DevPak plugin). If you are not sure whether you might need them some day (you may switch to '''MinGW''' or simply decide to use more than one compiler), better install them (they are just few kilobytes anyway) and eventually keep them disabled.

Now you can run the '''Code::Blocks IDE''' for the first time, and set up the compiler.

==Setting up the compiler==
===First run compiler auto-detection===
If you have already installed MVCT on your machine, Code::Blocks will autodetect it now ([http://img289.imageshack.us/img289/4028/compilerautodetecton8rb.png screen]), as well as all other supported compilers that are present. If more than one compiler is detected, you can set one of them as default one.

After this step, you should have Visual C++ compiler almost fully integrated with Code::Blocks.
You only need to inform compiler about your Platform SDK installation and goodies (like resource compiler) it should find there. Now, either go to "Settings->Compiler" (in your C::B IDE) and then jump quickly to [[#Setting Platform SDK]], or read further to know more details and verify your auto-detection results.

===Setting compiler from scratch (missed or failed first run auto-detection)===
In case you missed first run auto-detection (MVCT was not present at the time) or somehow it failed, you have to set up your compiler manually. Whole procedure is actually common for any supported compiler, and applies to Microsoft Visual C++ Toolkit 2003 perfectly:

'''''Golden Tip :''' "In order to integrate any supported compiler with Code::Blocks, all you need to do is to correctly specify location of compiler's executables, as well as compiler's (include) and linker's (lib) directories".''
====Specifying location of compiler's executables====
Go to "Settings->Compiler" and make sure that "Microsoft Visual C++ Toolkit 2003" is selected.

Open "Programs" tab - verify whether '''''Compiler's installation directory''''' (the same you installed VCToolkit to, ie: "C:\VCToolkit2003\" ) is set properly - if not - press "Autodetect". If correct path doesn't appear, simply paste the correct one there or navigate to it using dialog available under "..." button.

Note that all specified executables (compiler, linker, resource compiler) must exist either in the "bin" subdirectory of '''''Compiler's installation path''''' (ie: "C:\VCToolkit2003\bin\") or in any other path specified here as "Extra path". (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

====Specifying location of compiler's and linker's directories====
Open "Directories" tab and verify if following entries are present:

"Compiler" tab - entries should point to "include" directories:
C:\VCToolkit2003\include

"Linker" tab - entries should point to "lib" directories:
C:\VCToolkit2003\lib

If not, do not hestitate to add these ones.

'''Note:''' If you ever be using any library that is not included in MVCT (like FMOD, Allegro, or any of thousands open source libraries out there), you need either to add appropriate "include" and "libs" paths here too, or copy headers and libs to already specified paths.

===Setting Platform SDK===
Setting up Platform SDK looks the same as previous step, you just have to add appropriate entries that point to Platform SDK's "include" and "lib" subdirectories respectively.

Being in "Directories" tab just add following entries:

"Compiler" tab:
C:\PlatformSDK\Include

"Linker" tab:
C:\PlatformSDK\Lib

"Resource compiler" tab:
C:\PlatformSDK\Include

Do not forget to specify extra path for resource compiler executable (it's in Platform SDK's "bin" subdirectory, ie: "C:\PlatformSDK\Bin" ) - you can do this in "Programs" tab (see [http://img289.imageshack.us/img289/772/settingexepaths7yx.png screen])

That's all - you can compile your applications using free Microsoft Visual C++ Toolkit 2003 with Code::Blocks as your IDE.

Enjoy!

===Compiling Hints===

If the project cannot find lib.exe then use the one in C:\Program Files\Microsoft Platform SDK\Bin\win64. It correctly makes lib files for 32-bit windows. So add to the END of

If the project you are compiling complains that it cannot find "msvcrt.lib" then download the .NET 1.1 SDK and add to the END of the Directories->Linker tab:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib

Both the VC++ Toolkit 2003 and the platform SDK omit this library.

If the project you are compiling has a resource (.rc) file then you will need cvtres.exe when using the VC++ Toolkit 2003. Goto support.microsoft.com, and search the KB for "cvtres1.exe". Should come up with "FIX: Visual Studio 97 SP3 Installs Incorrect Cvtres.exe" (187280). Download cvtres1.exe, rename to cvtres.exe and place this in a directory in the path, e.g. C:\PlatformSDK\Bin.

Both the VC++ Toolkit 2003 and the platform SDK omit this utility.

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-08T04:52:31Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 
cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 
 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 
 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release 
 
--------------- 
Btw, if you need cvtres.exe to compile .rc resource files, grab it here: 
http://support.microsoft.com/default.aspx?scid=kb;en-us;q187280

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-08T04:49:36Z

Grv: /* Building wxWidgets 2.6.1 mingw32 & vc++ toolkit 2003 */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 
cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 
 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 
 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release

FAQ

2005-08-08T03:39:59Z

Grv: /* When compiling a wxWidgets project, I get several "variable 'vtable for xxxx' can't be auto-imported". What's wrong? */

Compiling wxWidgets 2.6.2 to develop Code::Blocks (MSW)

2005-08-07T06:22:50Z

Grv: /* Post compilation steps (before running C::B) */

These are the instructions to compile wxWidgets do you can compile Code::Blocks on your own.

'''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.

== Install MinGW ==
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 instroctions 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:''' The files are compressed in the tar.gz format. You need a third-party extraction utility to unzip them. (like 7-zip)

You need at least the following files:
* [http://prdownloads.sf.net/mingw/gcc-core-3.4.2-20040916-1.tar.gz?download gcc-core-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/gcc-g++-3.4.2-20040916-1.tar.gz?download gcc-g++-3.4.2-20040916-1.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-runtime-3.7.tar.gz?download mingw-runtime-3.7.tar.gz]
* [http://prdownloads.sf.net/mingw/mingw-utils-0.3.tar.gz?download mingw-utils-0.3.tar.gz]
* [http://prdownloads.sf.net/mingw/w32api-3.2.tar.gz?download w32api-3.2.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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
GDB is not really needed, but could be usefull for debugging.

After you install, make sure you have the following directories under your path:
* <MINGW>\bin;
* <MINGW>\mingw32\bin;

== Download and Install the wxWidgets source code ==
The wxWidgets 2.6.1 distribution can be found at the [http://www.wxwidgets.org/dl_msw2.htm#stable wxWidgets website]. (Note that ther e is also a winhelp file available.) You can get 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:''' 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.1")

'''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.

== Check 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:
<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.

== Building wxWidgets ==
Now it is time to compile wxWidgets, open the command promt and change to the wxWidgets directory:
<tt>cd <WXWIN>\build\msw</tt>
Now we are on the right place we are first going to clean up the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
'''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 USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
'''NOTE:''' these options are the official Code::Blocks options. When you want another version of wxWidgets (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.

== Build the STC library ==
If you closed the command promt, you have to open it again.
We are going to the STC directory
<tt>cd ..\..\contrib\build\stc</tt>
We clean the source:
<tt>mingw32-make -f makefile.gcc clean</tt>
And we going to compile it. Make sure you have the same build options as before.
<tt>mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb</tt>
So now everything is compiled for using codeblocks.

== Copy libraries ==
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 ==
Everything is done now, and we can start compiling Code::Blocks, couldn't we? No! First we have to setup the paths.
Open the codeblocks project (CodeBlocks-wx2.6.0.cbp) and go to the Build options.
From there you have to go to the tab Directories and Compiler. Here you have to add the following paths (Remember to replace <WXWIN>)
* <WXWIN>\lib\codeblocks\msw
* <WXWIN>\include
* <WXWIN>\contrib\include
The first path is used to find the right setup.h for the build you are using. The other two are for the normal include files.

Now go to the Linker tab and add the following path:
* <WXWIN>\lib\codeblocks
'''NOTE:''' You have to replace this with the directory of your own choice in the previous section!

Finally, go to the resource tab and add the following path (Remember to replace <WXWIN>)
* <WXWIN>\include

Now you are finished with the configuration and you can hit the compile button (CTRL-F9). Be aware that Code::Blocks is not officially support wxWidgets 2.6.1 so it is possible that new files are not yet in the project. You have to do this by your self.

== Post compilation steps (before running C::B) ==

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: 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].

----------

Edit: I didn't see any update.bat script but no matter. Two changes to this howto to get everything to work.
 
1. When creating a wx project in codeblocks, the link stage fails with cannot find -lwxmsw. I needed to: 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw.a 
copy C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw26_stc.a to C:\wxWidgets-2.6.1\lib\codeblocks\libwxmsw_stc.a 

or mess with the autogenerated makefile (they don't use WX_VER anymore it seems...) which is more of a hassle. 
 
2. You will still get --enable-auto-import errors. Looks like you just need to add a define: 
project->build options->compiler->#defines 
WXUSINGDLL 
 
Lastly it will look for wxmsw26_gcc_cb.dll and not find it. Either put 
C:\wxWidgets-2.6.1\lib\codeblocks in your PATH, put wxmsw26_gcc_cb.dll and wxmsw26_stc_gcc_cb.dll in C:\windows\system32, or add C:\wxWidgets-2.6.1\lib\codeblocks to compile->compiler options->programs->additional paths 
 
Rebuild and everything should run ok.
 
 
====Building wxWidgets 2.6.1 mingw32 & 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 changes to support wxWidgets on the vc++ toolkit seamlessly.
 
--------------------
for mingw32 compiler
--------------------
 
cd <WXWIN>\build\msw 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
mingw32-make -f makefile.gcc clean 
mingw32-make -f makefile.gcc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_gcc; cd ..\gcc_dll; move * ..\codeblocks_gcc; move msw ..\codeblocks_gcc 
 
codeblocks 
<pre>
project->build options
directories->compiler
<WXWIN>\lib\codeblocks_gcc\msw
<WXWIN>\include
<WXWIN>\contrib\include
directories->linker
<WXWIN>\lib\codeblocks_gcc
directories->resource compiler
<WXWIN>\include
compiler->#defines
WXUSINGDLL

compile->compiler options
programs->additional paths
C:\wxWidgets-2.6.1\lib\codeblocks_gcc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\wxmsw26_gcc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc (not recommended)

copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw.a
copy C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw26_stc.a
to C:\wxWidgets-2.6.1\lib\codeblocks_gcc\libwxmsw_stc.a

compile->rebuild
</pre>
------------------------------
for vc++ toolkit 2003 compiler
------------------------------
install VCToolkitSetup.exe 
install PlatformSDK 
install .NET Framework SDK Version 1.1 
run PlatformSDK->Set Windows XP 32-bit Build Environment (Retail) 
C:\Program Files\Microsoft Visual C++ Toolkit 2003\vcvars32.bat (not needed) 
 
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 clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd ..\..\contrib\build\stc 
nmake -f makefile.vc clean 
nmake -f makefile.vc USE_XRC=1 SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=0 VENDOR=cb 
cd <WXWIN>\lib; mkdir codeblocks_vc; cd ..\vc_dll; move * ..\codeblocks_vc; move msw ..\codeblocks_vc 
 
codeblocks 
<pre>
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.1\lib\codeblocks_vc
-OR- copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_vc_cb.dll
to application exe directory or c:\windows\system32
-OR- change project->properties->targets->execution working dir
to C:\wxWidgets-2.6.1\lib\codeblocks_vc (not recommended)

compile->compiler options
programs->additional paths
C:\Program Files\Microsoft Platform SDK\Bin
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\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.1\lib\codeblocks_vc\wxmsw26.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw.lib
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.exp
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.exp
copy C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw26_stc.lib
to C:\wxWidgets-2.6.1\lib\codeblocks_vc\wxmsw_stc.lib

compile->rebuild
</pre>
 
building from the commandline (wxwidgets demos) 
nmake -f makefile.vc SHARED=1 MONOLITHIC=1 BUILD=release