Code::Blocks - User contributions [en]

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

2005-09-16T09:46:10Z

Mispunt: /* 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 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) ==
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-09-15T13:21:23Z

Mispunt: /* What compiler can I use with Code::Blocks? */

= 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, DigitalMars Free Compiler., OpenWatcom and Small Device C Compiler (SDCC).

== 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 (debug) (VCT3)
LIBCPMTD.LIB Multithreaded, static link (debug) (none)
MSVCPRTD.LIB Multithreaded, dynamic link (import library for MSVCP71D.DLL) (debug) (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? ==

As they say in ##C++ on FreeNode: 
cylon> msvc++6 is not a C++ compiler. It was made before the C++ standard, so it compiles some language that isn't C++. Upgrade.

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

2005-06-09T09:50:50Z

Mispunt:

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

2005-06-09T08:41:46Z

Mispunt:

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

2005-06-09T07:34:39Z

Mispunt:

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

2005-05-26T08:10:50Z

Mispunt: /* Set up MSYS */

These are the instructions to Install and compile wxWidgets 2.4.2 so you can later compile Code::Blocks on your own.

NOTE: The instructions are MS Windows (TM) specific, but some could be applied to other platforms as well

NOTE: This article is under construction. More info can be found [https://www.codeblocks.org/index.php?name=PNphpBB2&file=viewtopic&t=211&highlight=tutorial in the forums].

== Install MinGW ==

If you don't have the Code::Blocks+MinGW bundle, grab the latest MINGW stuff (including MSYS) from the
[http://www.mingw.org/download.shtml#hdr2 MINGW site] and install it under a directory you like. In this tutorial we're assumming you're installing MINGW under C:\MINGW.

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

The files I (Rick) have installed are:

* [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/MSYS-1.0.10.exe?download MSYS-1.0.10.exe]
* [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/gdb-5.2.1-1.exe?download gdb-5.2.1-1.exe]
* [http://prdownloads.sf.net/mingw/mingw32-make-3.80.0-3.exe?download mingw32-make-3.80.0-3.exe]

After you install, make sure you have the following directories under your path:
* C:\MINGW\bin;
* C:\MINGW\mingw32\bin;
(I'm assumming you installed under C:\MINGW)

== Set up MSYS ==

''NOTE: MSYS '''is not actually required''' for the following procedure to work. Just replace /c/ with c: and it works without MSYS ;) and make sure you have the [ftp://biolpc22.york.ac.uk/pub/ports/mingw32/extra.zip extra.zip]''

The [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download MSYS package] ('''NOT included in the Code::Blocks+MinGW bundle''') allows you to run unix scripts with Mingw. Think of it as a "mini-linux emulator". When you run the executable installer, it will provide a link to msys.bat. If it doesn't appear in your desktop, search for it in your programs menu.

The wxWidgets 2.4.2 compilation must be run from inside MSYS. Drive C is found under /c/, drive D under /d/ and so on.

== Download and Install the wxWidgets source code ==

The wxWidgets 2.4.2 distribution can be found at the [http://www.wxwindows.org/dl_msw2.htm#stable242 wxWidgets site]. (Note that there's also a [http://prdownloads.sourceforge.net/wxwindows/wxWindows-2.4.2-WinHelp.zip winhelp file] available). You can choose to install either the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2-setup.zip setup version] or the [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.4.2.zip plain zip version] (which I find ridiculous, because the setup version is zipped too!).

If you use the plain zip version, make sure to unzip using the full path. Otherwise the directories won't be created correctly.
On a second thought, you might like to use the setup version :P

I have my wxWidgets installed in '''C:\wxWindows-2.4.2''' . Under MSYS, that should be '''/c/wxWindows-2.4.2''' .

And now that you have all the ingredients, it's time to compile :)

== Build wxWidgets ==

NOTE: We're assumming you installed under C:\wxWindows-2.4.2 .

Before anything, let me warn you: wxWidgets compilation is SLOW. And by SLOW I mean the time equivalent to one or two evolution cycles, like from Triasic to Jurasic, but doubled. So make sure there's a nice show on the TV, or you could invite a friend to play cards. OR you could start preparing the coffee :)

Now, open up your MSYS prompt, and change to the wxWidgets src/msw directory:

: <tt>cd /c/wxWindows-2.4.2/src/msw</tt>

Then proceed to the build. But first, an important warning that will save you many headaches.
----

:'''WARNING!'''
:If due to a misconfiguration (like changing the version of your MINGW), your compilation fails, '''MAKE SURE''' you clean out the outputs directory with the following command:

:: <tt>mingw32-make -f makefile.g95 clean</tt>

:(do it for wxwidgets, stc and xrc. I had weird linker errors and crashes because I didn't clean up the partial compilations).
----

And now that everything's clean, proceed to the build:

: <tt>mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1</tt>

If no "mingw32-make" is found, try this:

: <tt>make -f makefile.g95 FINAL=1 UNICODE=0 WXMAKINGDLL=1</tt>

Is it compiling OK? Good! You can now enjoy your coffee :-)

== Build the STC library ==

Still inside MSYS, type:

:<tt>cd ../../contrib/src/stc</tt>

That should change the directory to /c/wxWindows-2.4.2/contrib/src/stc.
Now type:

:<tt>mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1</tt>

(NOTE: There are NO line breaks in the command, if you see them, they're shown for readability)

== Build the XRC library ==

Still inside MSYS, type:

:<tt>cd ../xrc</tt>

That should change the directory to /c/wxWindows-2.4.2/contrib/src/xrc.
Now type:

:<tt>mingw32-make -f makefile.g95 FINAL=1 UNICODE=0 WXUSINGDLL=1</tt>

And that's it! Now you only have to copy the lib and include directories so your MINGW installation can find them.

== Copy the files to your mingw directory or set up the paths ==

This section provides you with two alternatives: The easy one, and the hard one.
The easy one consists of just copying the files to your MINGW directory. The hard one consists of setting up the paths in codeblocks.

=== Option 1: Copying the wxWidgets files over your MINGW installation ===

NOTE: The following instructions will overwrite part of your MINGW installation. If you're planning to build unicode applications, or use another version of wxWidgets, DO NOT, repeat, '''DO NOT''' follow these! Instead you'll have to set up the paths manually.

So, here's how to copy the files. I (Rick) guarantee this option works, since it's the one I used.

Close your MSYS window, and now open your windows explorer ('''NOT''' internet explorer, but Windows explorer. To open it, just press "(Windows key)+E"

It's recommended to open TWO explorer windows: One for your wxWidgets directory (which we'll change to copy different files), and another to
==== Copying the header files ====
In the location bar, select the following path:
:<tt>C:\wxWindows-2.4.2\include</tt>

Select all the files AND DIRECTORIES and copy.
Change to the directory "include" under your MINGW main directory, and paste.

Now change again the directory to:
:<<tt>C:\wxWindows-2.4.2\contrib\include</tt>

Copy all files and directories, and paste them to your MINGW include directory.

==== Copying the library files ====

Change the explorer directory to:

:<tt>C:\wxWindows-2.4.2\lib</tt>

And select all the files. Copy and Paste under your MINGW "lib" directory.

==== Copying the setup.h file ====

This one's very important! Normally people know to copy the headers and libs, but miss this step. If you miss it, you'll get LOTS of compilation errors.

Change the explorer directory to:

:<tt>C:\wxWindows-2.4.2\lib</tt>

There is a "mswdll" directory there. Under it, there's a "wx" subdirectory, too. Inside it there's a "setup.h".

Copy it, and paste under your MINGW include/wx directory.

(END of option 1)

=== Option 2: Setting up the paths manually ===

These instructions are to be followed by those who plan to use the 2.6 version of wxWidgets, or want to build their own version (i.e. with unicode support). Since you can't use both 2.4.2 and 2.6 libraries at the same time, you have to keep them in separate directories.

(Under construction - Somebody who has done this step, please edit)

----

And that's it. Now you're ready to compile Code::Blocks!