Code::Blocks - User contributions [en]

Developer documentation

2007-11-04T22:04:49Z

Jmccay:

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
Articles for Code::Blocks developers.

* '''[http://launchpad.net/products/codeblocks/ Translation]'''
:Code::Blocks uses Launchpad to coordinate translation efforts.

* '''[[Coding style]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

* '''[[Scripting Code::Blocks]]'''
:Information about scripting Code::Blocks with [http://www.squirrel-lang.org/ Squirrel].

* '''[[A short overview about Code::Blocks architecture]]'''
:Information about the architecture of Code::Blocks.

* '''[[Code::Blocks SDK events]]'''
:Information about the Code::Blocks SDK events and how to work with them.

* '''[[File formats description]]'''
:Description of the format of each file Code::Blocks produces.

* '''SDK Documentation'''
:See the project page for this at http://developer.berlios.de/projects/codeblocks/ (under the downloads).

== Plug-In development ==

* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]
* [[Creating a plugin that actually does something]]
* [[Managing Plug-in Resources]]

* [[Research on doing a Plug-in for embedded help in CB]]

* [[wxSmith extensions]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

User documentation

2007-03-05T00:17:46Z

Jmccay:

[[Category:Code::Blocks Documentation]]
[[Category:User Documentation]]
__TOC__
Articles for Code::Blocks users.

'''[[Installing Code::Blocks]]'''

:How to install Code::Blocks (from binary or source)

'''[[Keyboard Shortcuts]]'''

:List of keyboard shortcuts that can be used in Code::Blocks

'''[[Command line arguments]]'''

:List of command-line arguments that can be used with Code::Blocks.

'''[[Personalities]]'''

:Customize the Code::Blocks user interface for different workflows.

'''[[Code::Blocks Plugins]]'''

:List of plugins that come with Code::Blocks.

'''[[The build process of Code::Blocks]]'''

:Information about how Code::Blocks actually builds your source code.

'''[[Scripting Code::Blocks]]'''
:Information about scripting Code::Blocks with [http://www.squirrel-lang.org/ Squirrel].

'''[[Miscellaneous]]'''
:Miscellaneous things related to the user development experience. This is a catch all place.

== Application development ==

* [[Builtin variables]]
* [[Recommended global variables]]
* [[Debugging with Code::Blocks]]

== Compilers ==

* [[Global compiler variables]]
* [[Precompiled headers]]
* [[Installing a supported compiler]]
* [[Installing Cygwin Compiler]]
* [[Installing Fortran Compiler]]
* [[Installing Uniwin remote compiler]]
* [[Code::Blocks_and_Cross_Compilers|Using cross compilers]]
* [[Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE]]
* [[Integrating Microsoft Visual C 6 with Code::Blocks IDE]]

== Third-party libraries ==

* [[Using SDL with Code::Blocks]]
* [[Using GLFW with Code::Blocks]]

== User interface development ==

* [[WxSmith Tutorial & Pointers|Creating a dialog for wxWidgets with wxSmith]]

Miscellaneous

2007-03-05T00:16:56Z

Jmccay:

[[Category:Miscellaneous]]

'''Editor Related Items'''

Scintilla (CodeBlocks editing component) offers users an easy way for inserting fold points in the code using the following symbols:
://{ -- as a block starter
://} -- as a block ender

Talk:Personalities

2007-02-23T18:13:14Z

Jmccay:

There is a bug in Personalities. Currently, the ask option doesn't produce a list of the personalities.

WxSmith Tutorial & Pointers

2005-10-28T01:51:11Z

Jmccay:

=== Tutorial ===

<<need to create this here>>

=== Pointers ===

When using an XRC file, do not forget to initialize the wxXMLResouce Handlers & XRC File. For example in your App::OnInit:

// Loading XRC resource file (not in a zip file).
wxXmlResource::Get()->InitAllHandlers();
wxXmlResource::Get()->Load("<your XRC File name>.xrc");

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

2005-10-22T18:58:56Z

Jmccay: /* 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 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:''' 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) ==
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. 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 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>

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

2005-10-01T23:16:19Z

Jmccay: /* 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> 
'''NOTE: The following directions do not work with msys, or other forms of Unix on windows.''' 
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->'''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>

Unicode Standards

2005-09-05T20:14:24Z

Jmccay: Place for the Unicode information

This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program. I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author. Sorry Feel free to edit this to improve it, or keep it up to date. I am new to using wiki, so please exscuse the bad designs. This is a a '''VERY''' rough draft with no clear organizational pattern. 
<nowiki> -- Joe M.</nowiki>

reference: [http://www.wxwidgets.org/manuals/2.4.2/wx458.htm#unicode]

== Macros ==
{NOTE: bullet list would look better here, but bold is used for now} 
'''__TFILE__''' = wxWidgets provide equivilant to __FILE__ 
'''__TDATE__''' = wxWidgets provide equivilant to __DATE__ 
'''__TTIME__''' = wxWidgets provide equivilant to __TIME__ 
'''_U()''' = Use it to convert non-literal char* strings to wxString. Use it for reading attributes from TiXmlNode's. If you deal with functions that return strings, you must use our _U macro. 

Code:
#ifdef wxUSE_UNICODE
#define _U(x) wxString((x),wxConvUTF8)
#define _UU(x,y) wxString((x),y)
#else
#define _U(x) (x)
#define _UU(x,y) (x)
#endif

i.e.:
Code:
const char* incompatible = "This is an incompatible string";
wxString compatible = _U(incompatible);

// wxString conftype = conf->Attribute("ConfigurationType"); // before
wxString conftype = _U(conf->Attribute("ConfigurationType")); // after :)

'''_C()''' = multibyte C string see wxhelp (wxMBConv classes overview) 
Is defined in code as:
#if wxUSE_UNICODE
#define _UU(x,y) wxString((x),(y))
#define _CC(x,y) (x).mb_str((y))
#else
#define _UU(x,y) (x)
#define _CC(x,y) (x)
#endif

#define _U(x) _UU((x),wxConvUTF8)
#define _C(x) _CC((x),wxConvUTF8)

'''_wxT()''' = fixed text's - like XRC resources object names (only adds an L before the string (ONLY if you're in a unicode build).) 
wxT() is a macro which can be used with character and string literals (in other words, 'x' or "foo") to automatically convert them to Unicode in Unicode build configuration. Please see the Unicode overview for more information.

This macro is simply returns the value passed to it without changes in ASCII build. In fact, its definition is:

#ifdef UNICODE
#define wxT(x) L ## x
#else // !Unicode
#define wxT(x) x
#endif 

'''_T()''' = fixed text's - like XRC resources object names (only adds an L before the string (ONLY if you're in a unicode build).). 
This macro is exactly the same as wxT and is defined in wxWidgets simply because it may be more intuitive for Windows programmers as the standard Win32 headers also define it (as well as yet another name for the same macro which is _TEXT()).

Don't confuse this macro with _()! 
wxChar _T(char ch)

const wxChar * _T(const wxChar ch) 

'''_()''' = text's which might be translated to other user-languages 
This macro expands into a call to wxGetTranslation function, so it marks the message for the extraction by xgettext just as wxTRANSLATE does, but also returns the translation of the string for the current locale during execution.

Don't confuse this macro with _T()! 

'''wxPLURAL''' = This macro is identical to _() but for the plural variant of wxGetTranslation. 
const wxChar * wxPLURAL(const char *sing, const char *plur, size_tn) 

== Guidlines ==
'''char & wxChar:''' 
Do not use wxChar when is not a text character, because a wxChar in unicode is an int of 16 bits (not 8 bits):

Example for text:
wxChar im_a_character = _T('f');

Example for not text (not character):
char im_a_byte = 254;
but perhaps better would be to use:
byte im_a_byte = 254;
so it's clear that it's a byte and not a character.

'''Other:''' 
Problem code:
// indent code accordingly
wxString code = it->second;
code.Replace("\n", '\n' + lineIndent);

Solution:
<nowiki> If the input is a const char*, use "normal strings". If the input is a wxChar or wxString, use the _T("macros"). For example:</nowiki>

// indent code accordingly
wxString code = it->second;
code.Replace(_T("\n"), _T('\n') + lineIndent);

Some of the strings already converted in C::B, use _( when they should be _T(.

Example:

WRONG: wxXmlResource::Get()->LoadDialog(this, parent, _("dlgGenericMultiSelect"));

dlgGenericMultiSelect is a reference to a resource. Therefore it must use _T instead.

RIGHT: wxXmlResource::Get()->LoadDialog(this, parent, _T("dlgGenericMultiSelect"));

And don't forget to test for single characters, too!

All operations with wxStrings (not char*'s) should have _("string") for strings to be displayed to the user, and _T("string") for strings used internally.

Printf-like functions is - use c_str() (in examples in wxwidgets.org there are used different arguments for unicode and non-unicode versions where formating string was both "%s"). For example:

tmpkey.Printf(_T("%s/editor/keywords/%d"), key.c_str(), i);

'''XRCID and XRCCTRL macros:''' 
XRCID and XRCCTRL macros must _NOT_ be converted! They're pre-converted already!

WRONG: XRCCTRL(*this, _T("lblLabel"), wxStaticText)->SetLabel(label);

RIGHT: XRCCTRL(*this, "lblLabel", wxStaticText)->SetLabel(label);

'''concatenated strings:''' 
_() is macro which calls one of wxWidget's internal function so concatenating should look like this:

_("string 1" "string2" ... )

_T() macro simply adds 'L' before string given as a param (in Unicode of course, in normal mode it do nothing with the string) so concatenation should be:

_T("string1") _T("string2") ...

This need to be rewritten. If nobody else improves on this, I will try and rewrite this once I have used these macros more. Joe M.