Code::Blocks - User contributions [en]

Syntax highlighting custom colour themes

2013-12-04T13:21:21Z

Jens:

[[Category: User Documentation]]
This page lists syntax highlighting custom colour themes contributed by Code::Blocks users.

All screenshots were made with Code::Blocks 12.11 running on Windows XP, with the following settings:
* General settings/Editor settings/Font: '''Consolas 12''';
* General settings/Editor settings/Other options/Highlight line under caret: '''enabled''';
* Margins and caret/Caret/Style is '''Line''', Width is '''3''', and Colour is '''red''' (R: 255, G: 0, B: 0).

There are dark themes and light themes. Custom colours are configured on each theme on a per-language basis. The themes below have been configured for C/C++ only; other languages are unchanged from the default colour theme.

== Important note ==

Currently, these themes can only be used with the C/C++ lexer !

== Bright Yellow ==

[[File:BrightYellow.png]]

== Dark Gray ==

[[File:DarkGray.png]]

== Espresso Libre ==
You might want to set General settings/Editor settings/Other options/Highlight line under caret to '''disabled''' with this theme.

[[File:EspressoLibre.png]]

== Idel ==

[[File:Idel.png]]

== KFT2 ==
You might want to set General settings/Editor settings/Other options/Highlight line under caret to '''disabled''' with this theme.

[[File:KFT2.png]]

== Modnokai Coffee ==

[[File:ModnokaiCoffee.png]]

== Modnokai Night Shift ==

[[File:ModnokaiNightShift.png]]

== Modnokai Night Shift v2==

[[File:ModnokaiNightShift_v2.png]]

== Oblivion ==

[[File:Oblivion.png]]

== Slush n' Poppies ==

[[File:SlushNPoppies.png]]

== Solarized Dark ==

[[File:SolarizedDark.png]]

== Solarized Light ==

[[File:SolarizedLight.png]]

== Son of Obsidian ==

[[File:SonOfObsidian.png]]

== Sublime ==

[[File:Sublime.png]]

== Vim ==

[[File:Vim.png]]

== Installation ==

Follow the steps below to install the colour themes:

''Note: '''Always''' back up your current configuration file before importing a custom configuration file!''

Make sure Code::Blocks is '''NOT''' running. Import the colour set file '''colour_themes.conf''' below:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocksConfig version="1">
<editor>
<colour_sets>
<ACTIVE_COLOUR_SET>
<str>
<![CDATA[modnokai night shift v2]]>
</str>
</ACTIVE_COLOUR_SET>
<ACTIVE_LANG>
<str>
<![CDATA[C/C++]]>
</str>
</ACTIVE_LANG>
<bright_yellow>
<NAME>
<str>
<![CDATA[bright yellow]]>
</str>
</NAME>
<cc>
<style0>
<BACK>
<colour r="255" g="255" b="208" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<BACK>
<colour r="255" g="255" b="208" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="158" g="158" b="158" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="158" g="158" b="158" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="158" g="158" b="158" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="158" g="158" b="158" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="128" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="128" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="128" g="128" b="218" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="128" g="128" b="218" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style21>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style39>
<BACK>
<colour r="0" g="255" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</bright_yellow>
<dark_gray>
<NAME>
<str>
<![CDATA[dark gray]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="42" g="56" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="42" g="56" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style13>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style19>
<FORE>
<colour r="255" g="142" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="140" g="196" b="255" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="255" g="230" b="80" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="255" g="128" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="255" g="128" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style34>
<FORE>
<colour r="115" g="210" b="22" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="255" g="0" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="128" g="128" b="128" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="64" g="128" b="128" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</dark_gray>
<idel>
<NAME>
<str>
<![CDATA[idel]]>
</str>
</NAME>
<cc>
<style0>
<BACK>
<colour r="245" g="245" b="245" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<BACK>
<colour r="245" g="245" b="245" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="135" g="135" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style21>
<FORE>
<colour r="255" g="128" b="64" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="156" g="37" b="166" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="0" g="155" b="45" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="0" g="155" b="45" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style34>
<FORE>
<colour r="0" g="128" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style39>
<BACK>
<colour r="0" g="255" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</idel>
<oblivion>
<NAME>
<str>
<![CDATA[oblivion]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="238" g="238" b="236" />
</FORE>
<BACK>
<colour r="46" g="52" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="238" g="238" b="236" />
</FORE>
<BACK>
<colour r="46" g="52" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="136" g="138" b="133" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="136" g="138" b="133" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="136" g="138" b="133" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="136" g="138" b="133" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style11>
<FORE>
<colour r="52" g="101" b="164" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="52" g="101" b="164" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style17>
<FORE>
<colour r="164" g="0" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="164" g="0" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="173" g="127" b="168" />
</FORE>
<BACK>
<colour r="46" g="52" b="54" />
</BACK>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="233" g="185" b="110" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="78" g="154" b="6" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="185" g="49" b="0" />
</FORE>
<BACK>
<colour r="30" g="3" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="185" g="49" b="0" />
</FORE>
<BACK>
<colour r="30" g="3" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="245" g="121" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style33>
<FORE>
<colour r="211" g="215" b="207" />
</FORE>
<NAME>
<str>
<![CDATA[UUID]]>
</str>
</NAME>
</style33>
<style34>
<FORE>
<colour r="78" g="154" b="6" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="233" g="185" b="110" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="23" g="32" b="24" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="24" g="33" b="33" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<style40>
<BACK>
<colour r="114" g="159" b="207" />
</BACK>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Matching brace highlight]]>
</str>
</NAME>
</style40>
<style41>
<FORE>
<colour r="238" g="238" b="236" />
</FORE>
<BACK>
<colour r="164" g="0" b="0" />
</BACK>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[No matching brace highlight]]>
</str>
</NAME>
</style41>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</oblivion>
<son_of_obsidian>
<NAME>
<str>
<![CDATA[son of obsidian]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="241" g="242" b="243" />
</FORE>
<BACK>
<colour r="34" g="40" b="42" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="241" g="242" b="243" />
</FORE>
<BACK>
<colour r="34" g="40" b="42" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="102" g="116" b="123" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="102" g="116" b="123" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="102" g="116" b="123" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="102" g="116" b="123" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style11>
<FORE>
<colour r="153" g="163" b="138" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="153" g="163" b="138" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style17>
<FORE>
<colour r="0" g="0" b="164" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="0" g="0" b="164" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="255" g="205" b="34" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="147" g="199" b="99" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="103" g="140" b="177" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="236" g="118" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="236" g="118" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="239" g="194" b="16" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style33>
<FORE>
<colour r="207" g="215" b="211" />
</FORE>
<NAME>
<str>
<![CDATA[UUID]]>
</str>
</NAME>
</style33>
<style34>
<FORE>
<colour r="160" g="130" b="189" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="232" g="226" b="183" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="48" g="58" b="59" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<FORE>
<colour r="0" g="0" b="0" />
</FORE>
<BACK>
<colour r="47" g="57" b="60" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<style40>
<BACK>
<colour r="80" g="80" b="80" />
</BACK>
<NAME>
<str>
<![CDATA[Matching brace highlight]]>
</str>
</NAME>
</style40>
<style41>
<FORE>
<colour r="0" g="0" b="160" />
</FORE>
<BACK>
<colour r="80" g="80" b="80" />
</BACK>
<NAME>
<str>
<![CDATA[No matching brace highlight]]>
</str>
</NAME>
</style41>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</son_of_obsidian>
<solarized_light>
<NAME>
<str>
<![CDATA[solarized light]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="88" g="110" b="117" />
</FORE>
<BACK>
<colour r="253" g="246" b="227" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="88" g="110" b="117" />
</FORE>
<BACK>
<colour r="253" g="246" b="227" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="38" g="139" b="210" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="38" g="139" b="210" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style15>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style17>
<FORE>
<colour r="220" g="50" b="47" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="220" g="50" b="47" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="42" g="161" b="252" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="88" g="110" b="117" />
</FORE>
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style34>
<FORE>
<colour r="203" g="75" b="22" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="181" g="137" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</solarized_light>
<solarized_dark>
<NAME>
<str>
<![CDATA[solarized dark]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="147" g="161" b="161" />
</FORE>
<BACK>
<colour r="0" g="43" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="147" g="161" b="161" />
</FORE>
<BACK>
<colour r="0" g="43" b="54" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="38" g="139" b="210" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="38" g="139" b="210" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style15>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style17>
<FORE>
<colour r="220" g="50" b="47" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="220" g="50" b="47" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="42" g="161" b="252" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="133" g="153" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="88" g="110" b="117" />
</FORE>
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="42" g="161" b="152" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style34>
<FORE>
<colour r="203" g="75" b="22" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="181" g="137" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style39>
<BACK>
<colour r="7" g="54" b="66" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME bool="1">
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</solarized_dark>
<modnokai_coffee>
<NAME>
<str>
<![CDATA[modnokai coffee]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="39" g="40" b="34" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="39" g="40" b="34" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style15>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style17>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="38" g="249" b="173" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style34>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="166" g="226" b="46" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="73" g="72" b="62" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="62" g="61" b="50" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</modnokai_coffee>
<sublime>
<NAME>
<str>
<![CDATA[sublime]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="40" g="40" b="40" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="40" g="40" b="40" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="106" g="102" b="85" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="58" g="81" b="133" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="58" g="81" b="133" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style19>
<FORE>
<colour r="150" g="110" b="220" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="100" g="210" b="230" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="156" g="242" b="132" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="230" g="220" b="110" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="230" g="220" b="110" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style36>
<FORE>
<colour r="255" g="0" b="127" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="75" g="72" b="65" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="91" g="90" b="78" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
</cc>
</sublime>
<vim>
<NAME>
<str>
<![CDATA[vim]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="192" g="192" b="192" />
</FORE>
<BACK>
<colour r="0" g="0" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="192" g="192" b="192" />
</FORE>
<BACK>
<colour r="0" g="0" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="128" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="128" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="128" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="128" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="0" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="0" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style19>
<FORE>
<colour r="255" g="0" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="0" g="255" b="0" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="255" g="255" b="0" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="255" g="0" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="255" g="0" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="255" g="0" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style34>
<FORE>
<colour r="0" g="0" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="128" g="128" b="128" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="64" g="128" b="128" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
</cc>
</vim>
<slush_n_poppies>
<NAME>
<str>
<![CDATA[slush n poppies]]>
</str>
</NAME>
<cc>
<style0>
<BACK>
<colour r="241" g="241" b="241" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<BACK>
<colour r="241" g="241" b="241" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style11>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="64" g="96" b="64" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style19>
<FORE>
<colour r="0" g="128" b="160" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="32" g="96" b="160" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="32" g="96" b="160" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="192" g="48" b="48" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="192" g="48" b="48" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="128" g="0" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style36>
<FORE>
<colour r="97" g="97" b="97" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="176" g="176" b="255" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style40>
<BACK>
<colour r="140" g="140" b="255" />
</BACK>
<BOLD bool="0" />
<UNDERLINED bool="1" />
<NAME>
<str>
<![CDATA[Matching brace highlight]]>
</str>
</NAME>
</style40>
<style41>
<BACK>
<colour r="255" g="106" b="106" />
</BACK>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[No matching brace highlight]]>
</str>
</NAME>
</style41>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
</cc>
</slush_n_poppies>
<espresso_libre>
<NAME>
<str>
<![CDATA[espresso libre]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="132" g="112" b="89" />
</FORE>
<BACK>
<colour r="42" g="33" b="28" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="132" g="112" b="89" />
</FORE>
<BACK>
<colour r="42" g="33" b="28" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="0" g="102" b="255" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="0" g="102" b="255" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="0" g="102" b="255" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="0" g="102" b="255" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style19>
<FORE>
<colour r="68" g="170" b="67" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="67" g="168" b="237" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style27>
<FORE>
<colour r="4" g="155" b="10" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="4" g="155" b="10" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="47" g="228" b="32" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style34>
<FORE>
<colour r="154" g="255" b="135" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="109" g="121" b="222" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style40>
<FORE>
<colour r="192" g="192" b="192" />
</FORE>
<BACK>
<colour r="141" g="119" b="95" />
</BACK>
<BOLD bool="0" />
<UNDERLINED bool="1" />
<NAME>
<str>
<![CDATA[Matching brace highlight]]>
</str>
</NAME>
</style40>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</espresso_libre>
<modnokai_night_shift>
<NAME>
<str>
<![CDATA[modnokai night shift]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="34" g="40" b="42" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="34" g="40" b="42" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style15>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style17>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="38" g="249" b="173" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style34>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="166" g="226" b="46" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="17" g="64" b="76" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="47" g="57" b="60" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
<editor>
<keywords />
</editor>
</cc>
</modnokai_night_shift>
<default>
<NAME>
<str>
<![CDATA[default]]>
</str>
</NAME>
</default>
<kft2>
<NAME>
<str>
<![CDATA[kft2]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="93" g="255" b="105" />
</FORE>
<BACK>
<colour r="28" g="0" b="36" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="93" g="255" b="105" />
</FORE>
<BACK>
<colour r="28" g="0" b="36" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="0" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="0" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="0" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="0" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style11>
<FORE>
<colour r="100" g="211" b="222" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="100" g="211" b="222" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style15>
<FORE>
<colour r="10" g="187" b="187" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="10" g="187" b="187" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style19>
<FORE>
<colour r="255" g="241" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="63" g="118" b="255" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="0" g="222" b="0" />
</FORE>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="171" g="171" b="171" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="171" g="171" b="171" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style31>
<FORE>
<colour r="255" g="176" b="53" />
</FORE>
<NAME>
<str>
<![CDATA[Character]]>
</str>
</NAME>
</style31>
<style33>
<FORE>
<colour r="255" g="0" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[UUID]]>
</str>
</NAME>
</style33>
<style34>
<FORE>
<colour r="33" g="237" b="33" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="255" g="0" b="206" />
</FORE>
<BOLD bool="1" />
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<FORE>
<colour r="255" g="196" b="253" />
</FORE>
<BACK>
<colour r="78" g="0" b="86" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<FORE>
<colour r="0" g="255" b="14" />
</FORE>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<style40>
<FORE>
<colour r="255" g="0" b="0" />
</FORE>
<BACK>
<colour r="0" g="0" b="0" />
</BACK>
<BOLD bool="0" />
<NAME>
<str>
<![CDATA[Matching brace highlight]]>
</str>
</NAME>
</style40>
<editor>
<keywords>
<SET4>
<str>
<![CDATA[_DEBUG=1 __cplusplus __GNUC__ __GNUG__]]>
</str>
</SET4>
</keywords>
</editor>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
</cc>
</kft2>
<modnokai_night_shift_v2>
<NAME>
<str>
<![CDATA[modnokai night shift v2]]>
</str>
</NAME>
<cc>
<style0>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="0" g="0" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style0>
<style1>
<FORE>
<colour r="255" g="255" b="255" />
</FORE>
<BACK>
<colour r="0" g="0" b="0" />
</BACK>
<NAME>
<str>
<![CDATA[Default]]>
</str>
</NAME>
</style1>
<style5>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style5>
<style6>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style6>
<style7>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style7>
<style8>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (normal)]]>
</str>
</NAME>
</style8>
<style9>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style9>
<style10>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (normal)]]>
</str>
</NAME>
</style10>
<style11>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style11>
<style12>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment (documentation)]]>
</str>
</NAME>
</style12>
<style13>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style13>
<style14>
<FORE>
<colour r="117" g="113" b="94" />
</FORE>
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Comment line (documentation)]]>
</str>
</NAME>
</style14>
<style15>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style15>
<style16>
<FORE>
<colour r="128" g="255" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword (documentation)]]>
</str>
</NAME>
</style16>
<style17>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style17>
<style18>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Comment keyword error (documentation)]]>
</str>
</NAME>
</style18>
<style19>
<FORE>
<colour r="255" g="128" b="128" />
</FORE>
<NAME>
<str>
<![CDATA[Number]]>
</str>
</NAME>
</style19>
<style21>
<FORE>
<colour r="120" g="215" b="236" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[Keyword]]>
</str>
</NAME>
</style21>
<style23>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<BOLD bool="0" />
<ITALICS bool="1" />
<NAME>
<str>
<![CDATA[User keyword]]>
</str>
</NAME>
</style23>
<style27>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style27>
<style28>
<FORE>
<colour r="224" g="160" b="0" />
</FORE>
<NAME>
<str>
<![CDATA[String]]>
</str>
</NAME>
</style28>
<style34>
<FORE>
<colour r="249" g="38" b="114" />
</FORE>
<NAME>
<str>
<![CDATA[Preprocessor]]>
</str>
</NAME>
</style34>
<style36>
<FORE>
<colour r="166" g="226" b="46" />
</FORE>
<NAME>
<str>
<![CDATA[Operator]]>
</str>
</NAME>
</style36>
<style38>
<BACK>
<colour r="17" g="64" b="76" />
</BACK>
<NAME>
<str>
<![CDATA[Selection]]>
</str>
</NAME>
</style38>
<style39>
<BACK>
<colour r="34" g="40" b="42" />
</BACK>
<NAME>
<str>
<![CDATA[Active line]]>
</str>
</NAME>
</style39>
<editor>
<keywords>
<SET4>
<str>
<![CDATA[__cplusplus __GNUC__ __GNUG__]]>
</str>
</SET4>
</keywords>
</editor>
<NAME>
<str>
<![CDATA[C/C++]]>
</str>
</NAME>
</cc>
</modnokai_night_shift_v2>
</colour_sets>
</editor>
</CodeBlocksConfig>

into your configuration with CB Share Config. Run Code::Blocks, go to Settings, Editor..., Syntax highlighting, and pick the colour theme of your choice.

Installing Code::Blocks from source on RPM based distributions

2012-09-22T07:59:00Z

Jens: /* Build the RPM package */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]

== Install Requirements ==

Note: Code::Blocks requires GTK+ 2.x. Older distributions might only support GTK+ 1.x.

Upgrading GTK+ is beyond the scope of this document, easier to upgrade distribution ?

=== Install Development Tools ===

This has to be installed before starting:
* zip
* update-desktop-files (only on SUSE)
* make
* gettext
* autoconf >= 2.5
* automake >= 1.7
* libtool >= 1.4
* m4
* intltool
* gcc-c++
* libstdc++-devel

In Fedora/CentOS, this can be done with:
<pre>
su -c 'yum groupinstall "Development Tools"'
su -c 'yum install intltool'
</pre>

==== Install newer autotools versions (if needed) ====

If you have CentOS 3 or RHEL 3, you will need to rebuild "automake17" to use instead of automake-1.6:
* ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/os/i386/SRPMS/automake17-1.7.9-5.src.rpm
<pre>
rpmbuild --rebuild automake17-1.7.9-5.src.rpm
</pre>

Then you need to invoke bootstrap like this, both on the commandline and in codeblocks.spec:
<pre>
AUTOMAKE=automake-1.7 ACLOCAL=aclocal-1.7 ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
</pre>

=== Setup RPM environment ===

This has to be installed before starting:
* rpm-build

The top work directory for RPM varies between distributions and setups, but you can find your RPM top dir by setting a variable like:

<pre>
RPM_TOPDIR=`rpm --eval %{_topdir}`
echo $RPM_TOPDIR
</pre>

==== Non-root rpmbuild environment (recommended) ====

It is recommended that you don't use the root account to build packages, here is how you set up a minimal user build environment:

<pre>
cd
mkdir rpm
echo "%_topdir $HOME/rpm" >> .rpmmacros
mkdir /tmp/$USER/rpm
echo "%_tmppath /tmp/$USER/rpm" >> .rpmmacros
cd rpm
mkdir SPECS SOURCES BUILD RPMS SRPMS
RPM_TOPDIR=`rpm --eval %{_topdir}`
</pre>

You can now build packages without being root (assuming that the spec files are correct). You will still need root access to install.

=== Install wxWidgets 2.6.x ===

''Note: the following section on the required version is out of date; please ''do'' use from the 2.8 branch.''

The build requirements in the source RPM are set to a minimum. So it isn't checked whether wxGTK is installed or not. So you have to take a look at it yourself. Note that currently Code::Blocks requires wxWidgets '''2.6''', not 2.8! So if your distribution only provides packages for wxWidgets 2.8, you need to build wxWidgets 2.6 yourself.

This has to be installed:
# wxGTK >= 2.6.0 and its devel package (see [http://wxwidgets.org wxwidgets.org])
# wxGTK-xrc and its devel package (in some distributions included in the packages of point 1)

In later Fedora, this can be done with:
<pre>
su -c 'yum install wxGTK-devel'
</pre>

==== Build the wxGTK RPM from source (if needed) ====

TODO

* http://prdownloads.sourceforge.net/wxwindows/wxGTK-2.6.3.tar.gz
* ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.tar.gz
* http://www.algonet.se/~afb/wx/wxGTK.spec

RPMS

* wx-base-unicode-2.6.3.0.2-1.i386.rpm
* wx-base-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-gl-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-debuginfo-2.6.3.0.2-1.i386.rpm
* wx-i18n-2.6.3.0.2-1.i386.rpm

=== Install Subversion client ===

This has to be installed before starting:
* subversion >= 1.4.0, (see [http://subversion.tigris.org subversion.tigris.org])

Binary packages for Red Hat Linux 9, Fedora Core 1, CentOS 3, CentOS 4 at:

http://the.earth.li/pub/subversion/summersoft.fay.ar.us/pub/subversion/latest/

In later Fedora, this can be done with:
<pre>
su -c 'yum install subversion'
</pre>

==== Build Subversion RPM from source (if needed) ====

TODO

* http://subversion.tigris.org/downloads/subversion-1.4.2.tar.gz
* packages/rpm/rhel-3/subversion.spec (CentOS 3)
* packages/rpm/rhel-4/subversion.spec (CentOS 4)

RPMS

* subversion-1.4.2-1.i386.rpm
* subversion-devel-1.4.2-1.i386.rpm
* subversion-perl-1.4.2-1.i386.rpm
* subversion-python-1.4.2-1.i386.rpm
* subversion-tools-1.4.2-1.i386.rpm
* subversion-debuginfo-1.4.2-1.i386.rpm

== Install Code::Blocks ==

=== Download the Source RPM ===

1. Download the Source RPM from [https://www.codeblocks.org/downloads/source www.codeblocks.org/downloads/source]

''Note: SRPM's are for the last stable (10.05); the SVN branch includes the many improvements since then.''


==== Prepare SRPM package from SVN (if needed) ====

1. You need to get the latest sources from SVN [https://www.codeblocks.org/downloads/svn www.codeblocks.org/downloads/svn]

svn checkout svn://svn.berlios.de/codeblocks/trunk

2. go into ''trunk'', if you haven't already done it.

3. run these three commands in this order
./bootstrap
./configure
make dist
the last one will create a .tar.gz archive that contains the sources.

4. copy the archive to the directory $RPM_TOPDIR/SOURCES
sudo mv codeblocks-trunk-r*.tar.gz $RPM_TOPDIR/SOURCES

5. build the source RPM, or copy spec to $RPM_TOPDIR/SPECS
rpmbuild -bs codeblocks.spec

This will create a source package in the directory $RPM_TOPDIR/SRPMS/.

=== Build the RPM package ===

1. Build the binary package
rpmbuild --rebuild codeblocks*.src.rpm

This will create several packages in one of the architecture specific subdirectories (i386, x86_64, ppc, ...) of $RPM_TOPDIR/RPMS/.

These are:
* codeblocks: main package
* codeblocks-contrib: contrib plugins
* codeblocks-devel: SDK headers
* codeblocks-contrib-devel: headers for contrib-plugins (wxSmith etc.)
* codeblocks-debuginfo: stripped debug information

=== Install the RPM package ===

Install as root the packages you want (usually codeblocks and codeblocks-contrib) and enjoy Code::Blocks!
su -c 'rpm -Uvh codeblocks-1.0*.i386.rpm'

Installing Code::Blocks from source on RPM based distributions

2012-09-22T07:57:15Z

Jens: /* Build the RPM package */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]

== Install Requirements ==

Note: Code::Blocks requires GTK+ 2.x. Older distributions might only support GTK+ 1.x.

Upgrading GTK+ is beyond the scope of this document, easier to upgrade distribution ?

=== Install Development Tools ===

This has to be installed before starting:
* zip
* update-desktop-files (only on SUSE)
* make
* gettext
* autoconf >= 2.5
* automake >= 1.7
* libtool >= 1.4
* m4
* intltool
* gcc-c++
* libstdc++-devel

In Fedora/CentOS, this can be done with:
<pre>
su -c 'yum groupinstall "Development Tools"'
su -c 'yum install intltool'
</pre>

==== Install newer autotools versions (if needed) ====

If you have CentOS 3 or RHEL 3, you will need to rebuild "automake17" to use instead of automake-1.6:
* ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/os/i386/SRPMS/automake17-1.7.9-5.src.rpm
<pre>
rpmbuild --rebuild automake17-1.7.9-5.src.rpm
</pre>

Then you need to invoke bootstrap like this, both on the commandline and in codeblocks.spec:
<pre>
AUTOMAKE=automake-1.7 ACLOCAL=aclocal-1.7 ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
</pre>

=== Setup RPM environment ===

This has to be installed before starting:
* rpm-build

The top work directory for RPM varies between distributions and setups, but you can find your RPM top dir by setting a variable like:

<pre>
RPM_TOPDIR=`rpm --eval %{_topdir}`
echo $RPM_TOPDIR
</pre>

==== Non-root rpmbuild environment (recommended) ====

It is recommended that you don't use the root account to build packages, here is how you set up a minimal user build environment:

<pre>
cd
mkdir rpm
echo "%_topdir $HOME/rpm" >> .rpmmacros
mkdir /tmp/$USER/rpm
echo "%_tmppath /tmp/$USER/rpm" >> .rpmmacros
cd rpm
mkdir SPECS SOURCES BUILD RPMS SRPMS
RPM_TOPDIR=`rpm --eval %{_topdir}`
</pre>

You can now build packages without being root (assuming that the spec files are correct). You will still need root access to install.

=== Install wxWidgets 2.6.x ===

''Note: the following section on the required version is out of date; please ''do'' use from the 2.8 branch.''

The build requirements in the source RPM are set to a minimum. So it isn't checked whether wxGTK is installed or not. So you have to take a look at it yourself. Note that currently Code::Blocks requires wxWidgets '''2.6''', not 2.8! So if your distribution only provides packages for wxWidgets 2.8, you need to build wxWidgets 2.6 yourself.

This has to be installed:
# wxGTK >= 2.6.0 and its devel package (see [http://wxwidgets.org wxwidgets.org])
# wxGTK-xrc and its devel package (in some distributions included in the packages of point 1)

In later Fedora, this can be done with:
<pre>
su -c 'yum install wxGTK-devel'
</pre>

==== Build the wxGTK RPM from source (if needed) ====

TODO

* http://prdownloads.sourceforge.net/wxwindows/wxGTK-2.6.3.tar.gz
* ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.tar.gz
* http://www.algonet.se/~afb/wx/wxGTK.spec

RPMS

* wx-base-unicode-2.6.3.0.2-1.i386.rpm
* wx-base-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-gl-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-debuginfo-2.6.3.0.2-1.i386.rpm
* wx-i18n-2.6.3.0.2-1.i386.rpm

=== Install Subversion client ===

This has to be installed before starting:
* subversion >= 1.4.0, (see [http://subversion.tigris.org subversion.tigris.org])

Binary packages for Red Hat Linux 9, Fedora Core 1, CentOS 3, CentOS 4 at:

http://the.earth.li/pub/subversion/summersoft.fay.ar.us/pub/subversion/latest/

In later Fedora, this can be done with:
<pre>
su -c 'yum install subversion'
</pre>

==== Build Subversion RPM from source (if needed) ====

TODO

* http://subversion.tigris.org/downloads/subversion-1.4.2.tar.gz
* packages/rpm/rhel-3/subversion.spec (CentOS 3)
* packages/rpm/rhel-4/subversion.spec (CentOS 4)

RPMS

* subversion-1.4.2-1.i386.rpm
* subversion-devel-1.4.2-1.i386.rpm
* subversion-perl-1.4.2-1.i386.rpm
* subversion-python-1.4.2-1.i386.rpm
* subversion-tools-1.4.2-1.i386.rpm
* subversion-debuginfo-1.4.2-1.i386.rpm

== Install Code::Blocks ==

=== Download the Source RPM ===

1. Download the Source RPM from [https://www.codeblocks.org/downloads/source www.codeblocks.org/downloads/source]

''Note: SRPM's are for the last stable (10.05); the SVN branch includes the many improvements since then.''


==== Prepare SRPM package from SVN (if needed) ====

1. You need to get the latest sources from SVN [https://www.codeblocks.org/downloads/svn www.codeblocks.org/downloads/svn]

svn checkout svn://svn.berlios.de/codeblocks/trunk

2. go into ''trunk'', if you haven't already done it.

3. run these three commands in this order
./bootstrap
./configure
make dist
the last one will create a .tar.gz archive that contains the sources.

4. copy the archive to the directory $RPM_TOPDIR/SOURCES
sudo mv codeblocks-trunk-r*.tar.gz $RPM_TOPDIR/SOURCES

5. build the source RPM, or copy spec to $RPM_TOPDIR/SPECS
rpmbuild -bs codeblocks.spec

This will create a source package in the directory $RPM_TOPDIR/SRPMS/.

=== Build the RPM package ===

1. Build the binary package
rpmbuild --rebuild codeblocks*.src.rpm

This will create several packages in one of the architecture specific subdirectories (i386, x86_64, ppc, ...) of $RPM_TOPDIR/RPMS/.

These are:
* codeblocks: main package
* codeblocks-contrib: contrib plugins
* codeblocks-devel: SDK headers
* codeblocks-debuginfo: stripped debug information

=== Install the RPM package ===

Install as root the packages you want (usually codeblocks and codeblocks-contrib) and enjoy Code::Blocks!
su -c 'rpm -Uvh codeblocks-1.0*.i386.rpm'

Installing Code::Blocks from source on RPM based distributions

2012-09-22T07:56:52Z

Jens: /* Prepare SRPM package from SVN (if needed) */

[[Category:Installing Code::Blocks]]
[[Category:Installing Code::Blocks from source]]

== Install Requirements ==

Note: Code::Blocks requires GTK+ 2.x. Older distributions might only support GTK+ 1.x.

Upgrading GTK+ is beyond the scope of this document, easier to upgrade distribution ?

=== Install Development Tools ===

This has to be installed before starting:
* zip
* update-desktop-files (only on SUSE)
* make
* gettext
* autoconf >= 2.5
* automake >= 1.7
* libtool >= 1.4
* m4
* intltool
* gcc-c++
* libstdc++-devel

In Fedora/CentOS, this can be done with:
<pre>
su -c 'yum groupinstall "Development Tools"'
su -c 'yum install intltool'
</pre>

==== Install newer autotools versions (if needed) ====

If you have CentOS 3 or RHEL 3, you will need to rebuild "automake17" to use instead of automake-1.6:
* ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/os/i386/SRPMS/automake17-1.7.9-5.src.rpm
<pre>
rpmbuild --rebuild automake17-1.7.9-5.src.rpm
</pre>

Then you need to invoke bootstrap like this, both on the commandline and in codeblocks.spec:
<pre>
AUTOMAKE=automake-1.7 ACLOCAL=aclocal-1.7 ACLOCAL_FLAGS="-I /usr/share/aclocal" ./bootstrap
</pre>

=== Setup RPM environment ===

This has to be installed before starting:
* rpm-build

The top work directory for RPM varies between distributions and setups, but you can find your RPM top dir by setting a variable like:

<pre>
RPM_TOPDIR=`rpm --eval %{_topdir}`
echo $RPM_TOPDIR
</pre>

==== Non-root rpmbuild environment (recommended) ====

It is recommended that you don't use the root account to build packages, here is how you set up a minimal user build environment:

<pre>
cd
mkdir rpm
echo "%_topdir $HOME/rpm" >> .rpmmacros
mkdir /tmp/$USER/rpm
echo "%_tmppath /tmp/$USER/rpm" >> .rpmmacros
cd rpm
mkdir SPECS SOURCES BUILD RPMS SRPMS
RPM_TOPDIR=`rpm --eval %{_topdir}`
</pre>

You can now build packages without being root (assuming that the spec files are correct). You will still need root access to install.

=== Install wxWidgets 2.6.x ===

''Note: the following section on the required version is out of date; please ''do'' use from the 2.8 branch.''

The build requirements in the source RPM are set to a minimum. So it isn't checked whether wxGTK is installed or not. So you have to take a look at it yourself. Note that currently Code::Blocks requires wxWidgets '''2.6''', not 2.8! So if your distribution only provides packages for wxWidgets 2.8, you need to build wxWidgets 2.6 yourself.

This has to be installed:
# wxGTK >= 2.6.0 and its devel package (see [http://wxwidgets.org wxwidgets.org])
# wxGTK-xrc and its devel package (in some distributions included in the packages of point 1)

In later Fedora, this can be done with:
<pre>
su -c 'yum install wxGTK-devel'
</pre>

==== Build the wxGTK RPM from source (if needed) ====

TODO

* http://prdownloads.sourceforge.net/wxwindows/wxGTK-2.6.3.tar.gz
* ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.tar.gz
* http://www.algonet.se/~afb/wx/wxGTK.spec

RPMS

* wx-base-unicode-2.6.3.0.2-1.i386.rpm
* wx-base-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-gl-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-contrib-devel-2.6.3.0.2-1.i386.rpm
* wx-gtk2-unicode-debuginfo-2.6.3.0.2-1.i386.rpm
* wx-i18n-2.6.3.0.2-1.i386.rpm

=== Install Subversion client ===

This has to be installed before starting:
* subversion >= 1.4.0, (see [http://subversion.tigris.org subversion.tigris.org])

Binary packages for Red Hat Linux 9, Fedora Core 1, CentOS 3, CentOS 4 at:

http://the.earth.li/pub/subversion/summersoft.fay.ar.us/pub/subversion/latest/

In later Fedora, this can be done with:
<pre>
su -c 'yum install subversion'
</pre>

==== Build Subversion RPM from source (if needed) ====

TODO

* http://subversion.tigris.org/downloads/subversion-1.4.2.tar.gz
* packages/rpm/rhel-3/subversion.spec (CentOS 3)
* packages/rpm/rhel-4/subversion.spec (CentOS 4)

RPMS

* subversion-1.4.2-1.i386.rpm
* subversion-devel-1.4.2-1.i386.rpm
* subversion-perl-1.4.2-1.i386.rpm
* subversion-python-1.4.2-1.i386.rpm
* subversion-tools-1.4.2-1.i386.rpm
* subversion-debuginfo-1.4.2-1.i386.rpm

== Install Code::Blocks ==

=== Download the Source RPM ===

1. Download the Source RPM from [https://www.codeblocks.org/downloads/source www.codeblocks.org/downloads/source]

''Note: SRPM's are for the last stable (10.05); the SVN branch includes the many improvements since then.''


==== Prepare SRPM package from SVN (if needed) ====

1. You need to get the latest sources from SVN [https://www.codeblocks.org/downloads/svn www.codeblocks.org/downloads/svn]

svn checkout svn://svn.berlios.de/codeblocks/trunk

2. go into ''trunk'', if you haven't already done it.

3. run these three commands in this order
./bootstrap
./configure
make dist
the last one will create a .tar.gz archive that contains the sources.

4. copy the archive to the directory $RPM_TOPDIR/SOURCES
sudo mv codeblocks-trunk-r*.tar.gz $RPM_TOPDIR/SOURCES

5. build the source RPM, or copy spec to $RPM_TOPDIR/SPECS
rpmbuild -bs codeblocks.spec

This will create a source package in the directory $RPM_TOPDIR/SRPMS/.

=== Build the RPM package ===

1. Build the binary package
rpmbuild --rebuild codeblocks-1.0*.src.rpm

This will create several packages in one of the architecture specific subdirectories (i386, x86_64, ppc, ...) of $RPM_TOPDIR/RPMS/.

These are:
* codeblocks: main package
* codeblocks-contrib: contrib plugins
* codeblocks-devel: SDK headers
* codeblocks-debuginfo: stripped debug information

=== Install the RPM package ===

Install as root the packages you want (usually codeblocks and codeblocks-contrib) and enjoy Code::Blocks!
su -c 'rpm -Uvh codeblocks-1.0*.i386.rpm'

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

2012-09-22T07:56:06Z

Jens: /* Patching Code::Blocks to using 2.9 instead of 2.8 */

'''Note, the wxWidgets 2.9.0 release is a development release NOT intended for production use.'''

'''Note, compiling Code::Blocks linked against the wxWidgets 2.9.0 is NOT ready for stable use; it crashes and fails to compile from time to time.'''

These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.

Although these instructions are targeted at the Windows operating system, it should be possible to apply them with slight adjustments to other platforms, since we make use of MinGW.

== Installing MinGW ==
Directions to install MinGW for Code::Blocks can be found here.
[[MinGW installation]]

== Installing the wxWidgets Source Code ==
The wxWidgets 2.9.0 distribution can be found at the [http://www.wxwidgets.org/downloads/#previous_stable wxWidgets download site]. (Note that there is also a winhelp file available.) You can choose between an installer and a zip file. You can just get the zip file because the installer is also a zipped version.

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

'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.9.0\wxWidgets-2.9.0").

'''NOTE:''' You do not need MSYS. Furthermore, you cannot have MSYS in your path, or the wxWidgets compilation will fail. Thus, if you have MSYS installed, ensure that ''<MSYS>\bin'' '''is not''' in your path before compiling wxWidgets. wxWidgets must be compiled from a "regular" command line (like cmd.exe), not from a Unix-like shell. The same problem could arise if Cygwin is in the path.

'''NOTE:''' For the remainder of these instructions we call the MinGW directory ''<MINGW>''. You have to change it to your corresponding directory (e.g. "C:\MinGW").

== Checking make Version ==
If you didn't install MinGW yourself you have to ensure you are using a recent enough version of the make utility. Open a command prompt and type:
<tt>cd <MINGW>\bin
mingw32-make -v</tt>
The version should read 3.80 or higher.

== Building wxWidgets ==
=== Editing the values to be used in wx/setup.h ===
Note, changing the value of wxUSE_STC prevents error compiling Code::Blocks because it has its own custom version of STC.
===== Open the folder <WXWIN>\include\wx\msw\ =====
===== If the file setup.h does not exist copy the file setup0.h to setup.h =====
===== With an text editor open <WXWIN>\include\wx\msw\setup.h =====
===== Change "#define wxUSE_STC 1" to "#define wxUSE_STC 0" =====
===== Save the changes =====

=== Changing Directory and Setting Path ===
To compile wxWidgets, open the command prompt window and change to the wxWidgets directory:
<tt>cd /d <WXWIN>\build\msw</tt>

<tt>SET PATH=<MINGW>\bin</tt>
'''NOTE:''' This is normally SET PATH=C:\MingGW\bin

=== Cleaning wxWidgets Code ===
Now clean up the source:
<tt>mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 USE_STC=0 USE_PROPGRID=1 BUILD=release clean</tt>
'''NOTE:''' Make sure you use exactly the same options for this step and for the build step below. The clean target uses these variables and only cleans the specified version of the generated object and library files. (It will not clean the intended files if these variables are not identical.)

'''NOTE:''' If you still have problems with compiling after cleaning, you could try to manually remove the gcc_msw directory under the build\msw directory. This directory is the place where the object files are stored.

=== Building wxWidgets Code ===
When everything is clean you can start compiling wxWidgets:
<tt>mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 USE_STC=0 USE_PROPGRID=1 BUILD=release</tt>

'''NOTE:''' These options are not the officially-supported Code::Blocks options because there is no official options for wxWidgets 2.9. The option of "USE_STC=0" is needed because Code::Blocks has its own customized version of it; and, if both exists it will cause errors building Code::Blocks plugins. The option "USE_PROPGRID=1" is used to help building plugins that depend on wxPropertyGrid. If you want another version of wxWidgets (debug or non-Unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for linking Code::Blocks.

Patience. This step takes time. Make sure there was no compilation error before you continue.

== Compiling Code::Blocks ==
=== Patching Code::Blocks to using 2.9 instead of 2.8 ===
No patches are needed to compile Code::Blocks with wxWidgets 2.9, just use the project/workspace-files with the ''_wx29'' in the name and call ''update29,bat'' to update the resources.

That does not mean, that everything runs absolutely bug-free, but we are working on it.

As always patches are welcome.

=== Setting up paths ===
Before finally compiling Code::Blocks itself, you need to setup the paths:
*Open the Code::Blocks project (CodeBlocks.cbp).
*It will ask you to define a [[Global compiler variables|Global variable]]
*Set the path to where you have wxWidgets installed (e.g. "c:\wxMSW-2.9.0\wxWidgets-2.9.0").
*Compile Code::Blocks.

=== Post compilation steps ===
When the compilation process is finished, simply run the update.bat script. It will ensure that all resource files Code::Blocks uses are in the right place and up to date.

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

2012-09-22T07:54:27Z

Jens: /* Patching Code::Blocks to using 2.9 instead of 2.8 */

'''Note, the wxWidgets 2.9.0 release is a development release NOT intended for production use.'''

'''Note, compiling Code::Blocks linked against the wxWidgets 2.9.0 is NOT ready for stable use; it crashes and fails to compile from time to time.'''

These are the instructions for compiling wxWidgets for use with Code::Blocks. They are primarily intended in preparation for compiling Code::Blocks itself but (hopefully) may also help installing wxWidgets for general development using that framework.

Although these instructions are targeted at the Windows operating system, it should be possible to apply them with slight adjustments to other platforms, since we make use of MinGW.

== Installing MinGW ==
Directions to install MinGW for Code::Blocks can be found here.
[[MinGW installation]]

== Installing the wxWidgets Source Code ==
The wxWidgets 2.9.0 distribution can be found at the [http://www.wxwidgets.org/downloads/#previous_stable wxWidgets download site]. (Note that there is also a winhelp file available.) You can choose between an installer and a zip file. You can just get the zip file because the installer is also a zipped version.

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

'''NOTE:''' For the remainder of these instructions we call the wxWidgets directory ''<WXWIN>''. You have to change it to your corresponding directory (e.g. "c:\wxMSW-2.9.0\wxWidgets-2.9.0").

'''NOTE:''' You do not need MSYS. Furthermore, you cannot have MSYS in your path, or the wxWidgets compilation will fail. Thus, if you have MSYS installed, ensure that ''<MSYS>\bin'' '''is not''' in your path before compiling wxWidgets. wxWidgets must be compiled from a "regular" command line (like cmd.exe), not from a Unix-like shell. The same problem could arise if Cygwin is in the path.

'''NOTE:''' For the remainder of these instructions we call the MinGW directory ''<MINGW>''. You have to change it to your corresponding directory (e.g. "C:\MinGW").

== Checking make Version ==
If you didn't install MinGW yourself you have to ensure you are using a recent enough version of the make utility. Open a command prompt and type:
<tt>cd <MINGW>\bin
mingw32-make -v</tt>
The version should read 3.80 or higher.

== Building wxWidgets ==
=== Editing the values to be used in wx/setup.h ===
Note, changing the value of wxUSE_STC prevents error compiling Code::Blocks because it has its own custom version of STC.
===== Open the folder <WXWIN>\include\wx\msw\ =====
===== If the file setup.h does not exist copy the file setup0.h to setup.h =====
===== With an text editor open <WXWIN>\include\wx\msw\setup.h =====
===== Change "#define wxUSE_STC 1" to "#define wxUSE_STC 0" =====
===== Save the changes =====

=== Changing Directory and Setting Path ===
To compile wxWidgets, open the command prompt window and change to the wxWidgets directory:
<tt>cd /d <WXWIN>\build\msw</tt>

<tt>SET PATH=<MINGW>\bin</tt>
'''NOTE:''' This is normally SET PATH=C:\MingGW\bin

=== Cleaning wxWidgets Code ===
Now clean up the source:
<tt>mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 USE_STC=0 USE_PROPGRID=1 BUILD=release clean</tt>
'''NOTE:''' Make sure you use exactly the same options for this step and for the build step below. The clean target uses these variables and only cleans the specified version of the generated object and library files. (It will not clean the intended files if these variables are not identical.)

'''NOTE:''' If you still have problems with compiling after cleaning, you could try to manually remove the gcc_msw directory under the build\msw directory. This directory is the place where the object files are stored.

=== Building wxWidgets Code ===
When everything is clean you can start compiling wxWidgets:
<tt>mingw32-make -f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 USE_STC=0 USE_PROPGRID=1 BUILD=release</tt>

'''NOTE:''' These options are not the officially-supported Code::Blocks options because there is no official options for wxWidgets 2.9. The option of "USE_STC=0" is needed because Code::Blocks has its own customized version of it; and, if both exists it will cause errors building Code::Blocks plugins. The option "USE_PROPGRID=1" is used to help building plugins that depend on wxPropertyGrid. If you want another version of wxWidgets (debug or non-Unicode) you still have to make sure you build a MONOLITHIC version (one big DLL) for linking Code::Blocks.

Patience. This step takes time. Make sure there was no compilation error before you continue.

== Compiling Code::Blocks ==
=== Patching Code::Blocks to using 2.9 instead of 2.8 ===
No patches are needed to compile Code::Blocks with wxWidgets 2.9 .

That does not mean, that everything runs absolutely bug-free, but we are working on it.

As always patches are welcome.

=== Setting up paths ===
Before finally compiling Code::Blocks itself, you need to setup the paths:
*Open the Code::Blocks project (CodeBlocks.cbp).
*It will ask you to define a [[Global compiler variables|Global variable]]
*Set the path to where you have wxWidgets installed (e.g. "c:\wxMSW-2.9.0\wxWidgets-2.9.0").
*Compile Code::Blocks.

=== Post compilation steps ===
When the compilation process is finished, simply run the update.bat script. It will ensure that all resource files Code::Blocks uses are in the right place and up to date.

Cross Compiling wxWidgets Applications on Linux

2011-12-04T12:02:06Z

Jens: /* Code::Blocks */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries of Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum. 
For debian you find packages on [http://apt.jenslody.de/ my server].

==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources change directory to the root of the sources and configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows with wxWidgets dll's compiled on MS Windows, so I prefer using the static libraries.

* The line in '''Compiler Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' for statically linked executables or you have to make sure the appropriate dll's exist on the target system. 
In any case the needed dll's have to be in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's. 
I wasn't able to use dll's build on windows together with a cross-compiled executable. Because of that I prefer a statically linked program that only needs '''mingwm10.dll'''. By doing so I avoid runtime errors.

'''mingwm10.dll''' is part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2011-12-04T11:58:49Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources change directory to the root of the sources and configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows with wxWidgets dll's compiled on MS Windows, so I prefer using the static libraries.

* The line in '''Compiler Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' for statically linked executables or you have to make sure the appropriate dll's exist on the target system. 
In any case the needed dll's have to be in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's. 
I wasn't able to use dll's build on windows together with a cross-compiled executable. Because of that I prefer a statically linked program that only needs '''mingwm10.dll'''. By doing so I avoid runtime errors.

'''mingwm10.dll''' is part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

User:Jens

2011-09-28T07:02:21Z

Jens:

*Real Name: Jens Lody
*Location: Germany
*Nightly (and Release) Builds for debian '''i386''' and '''amd64''', wxWidgets cross-build libraries for [http://www.debian.org/ debian]
*Homepage: [http://apt.jenslody.de/ Jens' (un-)official debian-repository for Code::Blocks]

Version control

2011-08-15T17:06:30Z

Jens: /* Merging from trunk to a branch */

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]

==== Merging from trunk to a branch ====

Merging from trunk to a branch is done with the following commands:

cd [path/to/my/branch/copy]
make sure it is clean and up to date
run: svn merge -r [first revision to be merged]:[last revision to be merged] svn+ssh://yourlogin@svn.berlios.de/svnroot/repos/codeblocks/trunk . (note the trailing dot [with a blank before it])
commit changes with comment "* my_branch: merged with trunk (trunk to my_branch)"

The first revision to be merged is normally the revision of the last merge, the last revision to be merged is normally HEAD, the url has to be fixed to fit your needs.
Instead of the url you can use the root-folder of your working-copy of trunk.
Instead of the trailing dot you can use the path to your working copy of the my-branch (if you are not inside its root-folder).
To see what will be merged (instead of really doing it), you can use "--dry-run" as for many other svn commands.

'''Important note:'''

Never mix changes from a merge with pending changes from the branch. This will result in an immediate loss of the ability to do a SVN re-integrate merge as SVN will never be able to resolve the changes.

Version control

2011-08-15T13:40:18Z

Jens: /* Merging from trunk to a branch */

WxWindowsQuickRef

2010-08-26T05:24:53Z

Jens:

[[Category:User Documentation]]
'''''A beginner's quick reference for setting up wxWidgets with Code::Blocks in Windows''''' 
Supported compilers: MinGW or MSVC

[http://shiningray.cn/windows-shang-pei-zhi-codeblocks-wxwidgets.html Chinese Translation]

'''Important Requirements:'''
* '''Recent version of Code::Blocks''' - You need to have successfully installed and run a recent version of Code::Blocks -- either [https://www.codeblocks.org/downloads/26 the 10.05 release] or [/index.php/board,20.0.html a recent nightly build].


* '''Windows compiler''' - You need to have correctly installed one of three options
**[http://www.mingw.org/ MinGW/GCC] free compiler, gcc-core, gcc-g++, binutils, w32api, and mingw32-make packages are required, or
**[http://msdn.microsoft.com/vstudio/ Microsoft's compilers] (the [http://msdn.microsoft.com/vstudio/express/ Express editions] are free, but you must also install the [http://www.microsoft.com/downloads/details.aspx?familyid=0baf2b35-c656-4969-ace8-e4c0c0716adb Platform SDK]), or
**[https://www.codeblocks.org/downloads/5#windows latest stable release of Code::Blocks] includes a MinGW-bundled compiler which includes all necessary packages

* '''Path properly defined.'''
** Ensure that the folder containing the compiler executables (typically C:\Program Files\CodeBlocks\bin) is in your [http://vlaurie.com/computers2/Articles/environment.htm#editing Windows PATH environment variable]. The path environment variable is changed by
***right-clicking on 'my computer',
***selecting properties,
***click the advanced tab,
***click the 'Environment Variables' button at the bottom.

To verify the path is set correctly, open a DOS prompt and enter the command: mingw32-gcc, a reply of 'Not recognized' indicates a problem. 'no input files' means that the program was found and that the path environment variable is correct. For example...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>mingw32-gcc
mingw32-gcc: no input files
C:\>

== Download wxWidgets ==
You can choose to download the wxWidgets source code and compile it yourself, or download the "wxPack", a precompiled version.
* '''The wxWidgets sources''' are a much smaller download, but you must also spend some time compiling them.
* '''wxPack''' is a much larger download, but you don't have to spend time compiling it or worry about build options.

=== wxWidgets Sources ===
The current recommended version of wxWidgets to use is '''2.8.10'''. [http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.8.10-Setup.exe Click here to download the wxWidgets 2.8.10 sources for Windows] (wxMSW-2.8.10-Setup.exe; 12.2 MB). You can check [http://www.wxwidgets.org/downloads/ the wxWidgets download page] to see if a newer stable version is available. '''It is highly recommended that you install the sources to a path without spaces.''' You should choose a volume with at least 300 MB of free space.

=== wxPack ===
wxPack makes the next step of building wxWidgets unnecessary. The current stable release of wxPack is '''v2.8.8.04''', based on wxWidgets 2.8.8. [http://downloads.sourceforge.net/wxpack/wxPack_v2.8.8.04.exe?download Click here to download wxPack v2.8.8.04] (wxPack_v2.8.8.04.exe, 315.9 MB). You can check [http://wxpack.sourceforge.net/Main/Downloads the wxPack download page] to see if a newer stable version is available. '''It is highly recommended that you install wxPack in a path without spaces.''' You should choose a volume with at least 700 MB of free space for MSVC, or 2.2 GB of free space for MinGW/GCC.

== Build wxWidgets ==
''This step is unnecessary if you are using '''wxPack''' ''

* Open up a command prompt for building. If you are using MinGW/GCC, simply use the standard Windows command shell (open the Start menu, click "Run...", enter "cmd" and hit OK). If you are using MSVC, you should use the special command shell which sets up the correct environment variables for you. If you use a version of MSVC which required you to download the Platform SDK separately, ensure that whichever command environment you use includes the Platform SDK tools and paths as well as the standard compiler tools and paths.
* Change to the wxWidgets build directory (where <wxWidgets> is the path you extracted the sources to; typically C:\wxWidgets-2.8.9):
cd <wxWidgets>\build\msw
* Execute the build command. The recommended command to use for '''MinGW/GCC''' is:
mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1
* The recommended command to use for '''MSVC''' is:
nmake -f makefile.vc BUILD=release SHARED=1 MONOLITHIC=1 UNICODE=1
* This step will generally take a long time; faster PCs may expect 30-minute build times, and slower PCs can take as much as several hours.
* If using more recent versions of GCC, many warnings will occur during the build. This can slow the build process noticeably; you may want to redirect the warnings to a text file by appending "2>errlog.txt" to the build command, or supress them entirely by appending "2>nul".

See the section below titled "wxWidgets build options explained" for details on the meaning of the BUILD, SHARED, MONOLITHIC, and UNICODE options. These options are critically important, because they define the basic wxWidgets development environment you will be using. You must duplicate them exactly when running Code::Blocks' wxWidgets project wizard.

== Create a wxWidgets project in Code::Blocks ==
* On the Code::Blocks Start Page, select "Create a new project"; alternatively, open the File menu, highlight "New" and select "Project..."
* Select "wxWidgets project"
# The first page is an introduction, which you can choose to skip in the future.
# Select which version of wxWidgets you will be using. If you followed the instructions above, you should select "wxWidgets 2.8.x".
# Set your project title and location.
# Enter author details if you wish (not required).
# Select options for automatic code and file generation.
# Select wxWidgets' location. It's highly recommended that you use a global variable for this: enter "$(#wx)" (without quotes). If you haven't already defined this global variable, the global variables dialog will appear; for the base path, select your wxWidgets installation location. You don't need to fill in the other paths.
# Select debug and/or release configurations for your project. The debug configuration at least is recommended.
# Choose your wxWidgets build options. '''These must match the options used when you built wxWidgets!''' If you followed the directions above, select all three of the options under "wxWidgets Library Settings". '''If you are using wxPack:''' wxPack includes each version, so you may select whichever options you prefer. The other settings on this page are not related to the wxWidgets build options; you may use them or not as you prefer. In order to avoid using a debug wxWidgets build (as recommended), you must select "Configure Advanced options" and then leave "Use __WXDEBUG__ and Debug wxWidgets lib" unchecked on the next page.
# Select additional libraries if required. You should not need to select any of these for normal usage.

== Build and Run ==
Select "Build and run" (F9) to, well, build and run. If all goes well, your wxWidgets basic program should appear.

== wxWidgets Build Options Explained ==
''What do the BUILD, SHARED, MONOLITHIC, and UNICODE options mean?''

=== BUILD ===
BUILD controls whether a debug version (BUILD=debug) or release version (BUILD=release) of wxWidgets itself is built. In the vast majority of cases you will only need a release version of wxWidgets, since you won't be interesting in debugging wxWidgets itself. You can still create debug builds of your own programs that link to a release build of wxWidgets.
* A '''debug''' build of wxWidgets creates libraries with a "d" suffix -- for example, "libwxmsw28d.a"/"wxmsw28d_gcc_custom.dll".
* A '''debug''' build of wxWidgets creates the folder "mswd" or "mswud" in the wxWidgets library output folder.
* A '''release''' build of wxWidgets creates libraries ''without'' the "d" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll".
* A '''release''' build of wxWidgets creates the folder "msw" or "mswu" in the wxWidgets library output folder.

=== SHARED ===
SHARED controls whether a DLL (SHARED=1) or static (SHARED=0) version of wxWidgets is built. With a DLL build, compile times are faster and the executable size is smaller. The total size of a single executable plus the wxWidgets DLL is greater, but multiple executables can use the same DLL.
* A '''DLL''' build of wxWidgets creates import libraries (such as libwxmsw28.a) and DLLs (such as wxmsw28_gcc_custom.dll). You must include the DLL when you distribute your program.
* A '''static''' build of wxWidgets creates static libraries only (such as libwxmsw28.a), and you do not need to distribute a wxWidgets DLL.

=== MONOLITHIC ===
MONOLITHIC controls whether a single library (MONOLITHIC=1) or multiple component libraries (MONOLITHIC=0) are built. With a monolithic build, project setup and development are much easier, and you only have one DLL to distribute if you're using a DLL build. With a non-monolithic (multilib) build, several different libraries are built and you can avoid linking with the entire wxWidgets codebase for programs that don't need it. You do have to ensure that you choose the correct component libraries.
* A '''monolithic''' build of wxWidgets creates a single wxWidgets import library (such as libwxmsw28.a) and a single DLL (such as wxmsw28_gcc_custom.dll).
* A '''multilib''' build of wxWidgets creates multiple import libraries (libwx28_base.a, etc.) and multiple DLLs.
* Additional '''static''' libraries are always created with any wxWidgets build (libwxexpat.a, libwxjpeg.a, etc.). These libraries do not normally need to be used with DLL builds of wxWidgets, but they are required when using static builds.

=== UNICODE ===
UNICODE controls whether wxWidgets and your program use wide-character strings with Unicode support. Most programs for Windows 2000 and later should do so. Earlier versions of Windows don't have the necessary Unicode support. You should always use wxWidget's _("string") and _T("string") macros to ensure that your hardcoded strings are the correct type.
* A '''Unicode''' (UNICODE=1) build of wxWidgets creates libraries with a "u" suffix -- for example, "libwxmsw28u.a"/"wxmsw28u_gcc_custom.dll".
* A '''Unicode''' build of wxWidgets creates the folder "mswu" or "mswud" in the wxWidgets library output folder.
* An '''ANSI''' (UNICODE=0) build of wxWidgets creates libraries ''without'' the "u" suffix -- for example, "libwxmsw28.a"/"wxmsw28_gcc_custom.dll".
* An '''ANSI''' build of wxWidgets creates the folder "msw" or "mswd" in the wxWidgets library output folder.

== Frequently Asked Questions ==

'''I get errors like "wx/setup.h: No such file or directory"'''

You're missing an important compiler search path in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, then open your project's build options and add "$(#wx.lib)\gcc_dll\mswu" (assuming a monolithic Unicode DLL build) to the compiler search paths.

'''I get errors like "cannot find -lwxmsw28u"'''

You have an incorrect link library in your build options. Make sure you choose the correct wxWidgets build configuration when running the wxWidgets project wizard. If re-running the wizard isn't an option, determine which version of the library is built and adjust the library name in your build options accordingly.

Compiled packages of Code::Blocks

2010-05-02T22:36:38Z

Jens: /* SVN */

== Stable Releases ==

=== 8.02 ===

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Operating_System|OS]]
! Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 2000/XP/Vista
| x86
| Binary
| With contrib plugins
| [http://downloads.sourceforge.net/codeblocks/codeblocks-8.02-setup.exe Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 2000/XP/Vista
| x86
| Binary Ansi
| With contrib plugins - With MinGW bundled
| [http://downloads.sourceforge.net/codeblocks/codeblocks-8.02mingw-setup.exe Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
|
| i386
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02debian-i386.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
|
| AMD64
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02debian-amd64.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 7.10 Gutsy
| x86
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks_8.02-0ubuntu1.deb.tar.gz Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 7.10 Gutsy
| AMD64
| Binary
|
| [http://prdownload.berlios.de/codeblocks/codeblocks-8.02-amd64.tar.gz Download]
|
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

=== 1.0 RC2 ===

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Operating_System|OS]]
! Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 98/NT/Me/2000/XP
| x86
| Binary Ansi
| With contrib plugins
| [http://prdownloads.sourceforge.net/codeblocks/codeblocks-1.0rc2.exe?download Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 98/NT/Me/2000/XP
| x86
| Binary Ansi
| With contrib plugins - With MinGW bundled
| [http://prdownloads.sourceforge.net/codeblocks/codeblocks-1.0rc2_mingw.exe?download Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
| Sid
| i386
| Binary
| No longer supported by the previous package author.
|
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 5.10 Breezy
| x86
| Binary
| No longer supported by the previous package author.
|
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| 2005.1
| x86/AMD64
| Ebuild
| {{dunno}}
| [http://bugs.gentoo.org/attachment.cgi?id=72819 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| 2005.1
| x86/AMD64
| Patch
| {{dunno}}
| [http://bugs.gentoo.org/attachment.cgi?id=72820 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Fedora]]
| Fedora Core 3
| i386
| Binary
| SRPMS compatible with wxGTK-2.4 is also [http://timeoff.wsisiz.edu.pl/zrzut/codeblocks-1.0-0.2.rc2.src.rpm available].
| [http://timeoff.wsisiz.edu.pl/zrzut/codeblocks-1.0-0.2.rc2.fc3.i386.rpm Download]
| Requires wxGTK-2.4 ([http://dag.wieers.com/packages/wxGTK/ Dag repository])
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Fedora]]
| Fedora Core 4
| i386
| Binary
| not available any more
| [http://www.neoinvent.com/cb/codeblocks-1.0-rc2.i386.rpm Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:FreeBSD-logo_32.png]] [[wikipedia:FreeBSD|FreeBSD]]
| 6.1
| x86
| Binary
| {{dunno}}
| [/index.php?topic=1407.0 Download]
|
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

== Development Releases ==

=== SVN ===

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec; border: solid 1px gray;"
! style="width:12em" | [[wikipedia:Operating_System|OS]]
! Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Microsoft_Windows-logo-alt2_32.png]] [[wikipedia:Microsoft_Windows|Windows]]
| 98/NT/Me/2000/XP
| x86
| Binary
| With contrib plugins
| [/index.php?board=20.0 Download]
| [/index.php/topic,3232.0.html How night build version works]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Debian-logo_32.png]] [[wikipedia:Debian|Debian]]
| stable,testing, unstable
| i386 and amd64
| Binary and sources
| With contrib plugins and doc-packages; APT-repository
| [http://apt.jenslody.de/pool/main/c/codeblocks/ Download]
| http://apt.jenslody.de/
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Ubuntu-logo_32.png]] [[wikipedia:Ubuntu_Linux|Ubuntu]]
| 5.10 Breezy
| x86
| Binary
| {{dunno}}
| [/index.php?board=20.0 Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:SuSE-logo-alt_32.png]] [[wikipedia:SUSE_Linux|openSUSE]]
|
| i586 & x86_64
| Binary
| With contrib plugins
| [http://download.opensuse.org/repositories/devel:/tools:/ide/ Download]
| http://en.opensuse.org/Build_Service/User
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Slackware-logo_32.png]] [[wikipedia:Slackware|Slackware]]
| 10.2
| i686
| Binary
| {{dunno}}
| [http://www.icpnet.pl/~groman/cb-slack/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Slackware-logo_32.png]] [[wikipedia:Slackware|Slackware]]
| 10.2
| athlon-xp
| Binary
| {{dunno}}
| [http://www.icpnet.pl/~groman/cb-slack/ Download]
|
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Mac-logo-alt.png]] [[wikipedia:Mac_OS_X|Mac OS X]]
| 10.3 Panther
| PPC
| Binary
| ?
| [http://developer.berlios.de/project/showfiles.php?group_id=5358 Download]
| Bundled with wxMac 2.6 inside the app bundle
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Mac-logo-alt.png]] [[wikipedia:Mac_OS_X|Mac OS X]]
| 10.4 Tiger
| PPC/X86
| Binary
| ?
| [http://developer.berlios.de/project/showfiles.php?group_id=5358 Download]
| Bundled with wxMac 2.6 inside the app bundle
|- style="border: solid 1px gray;"
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Mac-logo-alt.png]] [http://www.macports.org/ MacPorts]
| Darwin
| PPC/X86
| Source
| ?
|
| [[Installing Code::Blocks from source on Mac OS X]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Fedora-logo_32.png]] [[wikipedia:Fedora_Core|Fedora]]
|
| i386 & x86_64
| Binary
| With contrib plugins
| [http://download.opensuse.org/repositories/devel:/tools:/ide/ Download]
| http://en.opensuse.org/Build_Service/User
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[wikipedia:Mandriva_Linux|Mandriva]]
|
| i586 & x86_64
| Binary
| With contrib plugins
| [http://download.opensuse.org/repositories/devel:/tools:/ide/ Download]
| http://en.opensuse.org/Build_Service/User
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:CentOS-logo_32.png]] [[wikipedia:CentOS|CentOS]]
| CentOS 3/4
| i686
| Source
| ?
|
| [[Installing_Code::Blocks_from_source_on_RPM_based_distributions]]
|- style="border: solid 1px gray;"
! style="text-align: left; background: #ececec;" | [[Image:Gentoo-logo_32.png]] [[wikipedia:Gentoo_Linux|Gentoo]]
| Gentoo
| x86/AMD64
| Portage Overlay
| With contrib plugins by "contrib" useflag
| [http://www.savefile.com/projects/808517256 Download]
| [http://forums.gentoo.org/viewtopic-t-588089-highlight-codeblocks+svn.html Forum Guide New]
: [http://forums.gentoo.org/viewtopic-t-440412.html Forum Guide by retired Gentoo developer] [[Compiling_Code::Blocks_in_Gentoo]]
|- style="border: solid 1px gray;"
|- style="background: #ececec; border: solid 1px gray;"
! [[wikipedia:Operating_System|OS]]
! OS Version
! Architecture
! Package Type
! Remarks
! Download
! Installation Guide
|-
|}

Cross Compiling wxWidgets Applications on Linux

2010-02-19T16:26:46Z

Jens: /* Fixing build options */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows with wxWidgets dll's compiled on MS Windows, so I prefer using the static libraries.

* The line in '''Compiler Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' for statically linked executables or you have to make sure the appropriate dll's exist on the target system. 
In any case the needed dll's have to be in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's. 
I wasn't able to use dll's build on windows together with a cross-compiled executable. Because of that I prefer a statically linked program that only needs '''mingwm10.dll'''. By doing so I avoid runtime errors.

'''mingwm10.dll''' is part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Installing Code::Blocks

2009-06-07T12:50:38Z

Jens: /* Debian */

[[Category:Installing Code::Blocks]]

[[Compiled packages of Code::Blocks]]

== MS Windows ==

* [[Installing the latest official version of Code::Blocks on Windows]]
* [[Installing Code::Blocks nightly build on Windows]]
* [[Installing Code::Blocks from source on Windows]]

== Linux ==

* [[Installing Code::Blocks from source on Linux]] (applies to all distros)
* [[Installing Code::Blocks before SVN 3893 from source on Linux]] (applies to all distros)

=== Ubuntu ===

:* [[Installing Code::Blocks nightly build on Ubuntu]]

=== Debian ===

:* [http://apt.jenslody.de/ Installing Code::Blocks nightly build on Debian]

=== Fedora ===

:* [[Installing Code::Blocks nightly build on Fedora]]

=== Blag ===

:* [[Installing Code::Blocks nightly build on Blag]]

=== Gentoo ===

:* [[Installing Code::Blocks from source on Gentoo]]

=== RPM based distributions ===

Such as: Red Hat Linux, Yellow Dog Linux, Fedora Core, CentOS, etc. etc.

:* [[Installing Code::Blocks nightly build on RPM based distributions]]
:* [[Installing Code::Blocks from source on RPM based distributions]]

== BSD ==

=== FreeBSD ===

:* [[Installing Code::Blocks from source on FreeBSD]]

== Solaris ==

* [[Installing Code::Blocks from source on Solaris]]

== Mac OS X ==

* [[Installing Code::Blocks nightly build on Mac OS X]]

* [[Installing Code::Blocks from source on Mac OS X]]

==Working on Code::Blocks sources from within Code::Blocks!==

The following applies for all platforms where you have Code::Blocks installed and working.

After correct install of Code::Blocks you will find two folders under .../trunc/scr , a directory named "devel" and another one named "output".
These two folders will contain the same files and directory structure and you can use the IDE from either of these two directories. This structure has been created so that you can work in Code::Blocks while editing Code::Blocks' sources ;).
Basically, you 'll be using the "output/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel". So you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you 're using (under "output"). When your changes satisfy you and all works well, quit Code::Blocks, run "make update" from command line and re-launch "output/CodeBlocks.exe". You 'll be working on your brand new IDE!

Scripting commands

2009-02-22T14:45:04Z

Jens: /* CompileOptionsBase */

[[Category:Scripting Code::Blocks]]
Scripting is no good if all you can do is use the scripting language's built-in commands only. The host application (Code::Blocks) needs to expose parts of its internals to scripts, so scripts can use and control the host.

Code::Blocks has exposed a very large chunk of its SDK to scripts. This makes scripting in Code::Blocks nearly as powerful as native code (C++).

In this page all the exported constants, functions and classes are documented as a quick reference. For detailed documentation on each function/class, refer to the Code::Blocks SDK documentation.

''NOTE: Please remember that [http://www.squirrel-lang.org Squirrel] is typeless. Data types mentioned below are only used for documentation purposes.''

''NOTE: Please keep in mind that if a function has default parameters in C++ (which can be ommitted), you still have to type them for scripts (for e.g. exposed wxWidgets functionality). This means you *have* to use e.g. wxFileName.GetFullPath(wxPATH_NATIVE) instead of e.g only wxFileName.GetFullPath().

== Application object ==
The application object is accessed through the variable named '''<tt>App</tt>'''. Currently it has no bound functions...

== Global functions ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Log || wxString || logs to the application log
|-

|-
| void || LogDebug || wxString || logs to the debug log
|-

|-
| void || LogWarning || wxString || logs a warning
|-

|-
| void || LogError || wxString || logs an error
|-

|-
| int || Message || wxString,wxString,int || arg1=msg, arg2=caption, arg3=buttons; see API docs for cbMessageBox()
|-

|-
| void || ShowMessage || wxString ||
|-

|-
| void || ShowWarning || wxString ||
|-

|-
| void || ShowError || wxString ||
|-

|-
| void || ShowInfo || wxString ||
|-

|-
| wxString || ReplaceMacros || wxString,bool ||
|-

|-
| ScriptingManager* || GetScriptingManager || ||
|-

|-
| ProjectManager* || GetProjectManager || ||
|-

|-
| EditorManager* || GetEditorManager || ||
|-

|-
| ConfigManager* || GetConfigManager || ||
|-

|-
| UserVariableManager* || GetUserVariableManager || ||
|-

|-
| CompilerFactory* || GetCompilerFactory || ||
|-

|-
| wxArrayString || GetArrayFromString || wxString,wxString,bool ||
|-

|-
| wxString || GetStringFromArray || wxArrayString,wxString,bool ||
|-

|-
| wxString || EscapeSpaces || wxString ||
|-

|-
| wxString || UnixFilename || wxString ||
|-

|-
| FileType || FileTypeOf || wxString ||
|-

|-
| wxString || URLEncode || wxString ||
|-

|-
| void || NotifyMissingFile || wxString ||
|-

|-
| int || GetPlatformsFromString || wxString ||
|-

|-
| wxString || GetStringFromPlatforms || int,bool||
|-

|-
| void|| Display || wxString,wxString,int,int ||
|-

|-
| wxString || GetFolder || int || see API docs for ConfigManager::GetFolder()
|-

|-
| wxString || LocateDataFile|| wxString, int || see API docs for ConfigManager::LocateDataFile()
|-

|-
| bool || InstallPlugin || wxString,bool, bool || Install a binary plugin
|-

|-
| void || Include || wxString || similar to C/C++ ''<tt>#include "name"</tt>''
|-

|-
| bool || IsNull || void* ||
|-

|-
| wxString || _T || const char* || basically this is the wxString constructor
|-

|-
| bool || wxLaunchDefaultBrowser || wxString ||
|-

|-
| wxColour || wxGetColourFromUser || [wxColour] ||
|-

|-
| long || wxGetNumberFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetPasswordFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetTextFromUser || wxString,wxString,wxString ||
|-

|}

== ScriptingManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || RegisterScriptMenu || wxString, wxString || registers the script file (arg1) under a menu item (arg2).
e.g. <tt>GetScriptingManager().RegisterScriptMenu(_T("sample.script"), _T("Scripts/Sample script"))</tt>;
|-

|}

Notes about the <tt>RegisterScriptMenu</tt> function: 
* The second argument (menu item) is a string containing the full menu path to create the menu item. The path separator is a slash (/). For example, the string "Settings/Sample menu/Sample item" would create the menu path "Settings->Sample menu->Sample item".
* When each part of the path is evaluated, it is checked whether it starts with a number followed by a colon (:). If so then this is considered to be a menu index in the parent menu and the menu is inserted at that index instead of being appended to the menu. The number and colon are removed from the string.
* If the menu item starts with a dash (-), then a separator line is prepended in the menu before the menu item (e.g. "Scripts/'''-'''Sample script").
* For your convenience, all menu items created using this function have one extra functionality: if you keep the SHIFT key pressed while clicking on any of these "script menu items", instead of running the attached script, Code::Blocks will open it in the editor for you to view/edit :).
* Have a look at the [[Startup script#Example|startup script example]].

== ConfigManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| int || Read || int,int ||
|-

|-
| bool || Read || bool,bool ||
|-

|-
| float || Read || float,float ||
|-

|-
| wxString || Read || wxString,wxString ||
|-

|-
| void || Write || int,int ||
|-

|-
| void || Write || bool,bool ||
|-

|-
| void || Write || float,float ||
|-

|-
| void || Write || wxString,wxString[,bool] ||
|-

|}

== ProjectManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| wxString || GetDefaultPath || ( ) ||
|-

|-
| void || SetDefaultPath || (const wxString& path) ||
|-

|-
| cbProject* || GetActiveProject || ( ) ||
|-

|-
| void || SetProject || (cbProject* project, bool refresh = true) ||
|-

|-
| bool || LoadWorkspace || (const wxString& filename = DEFAULT_WORKSPACE)||
|-

|-
| bool || SaveWorkspace || ( ) ||
|-

|-
| bool || SaveWorkspaceAs || (const wxString& filename) ||
|-

|-
| bool || CloseWorkspace || ( ) ||
|-

|-
| cbProject* || IsOpen || (const wxString& filename) ||
|-

|-
| cbProject* || LoadProject || (const wxString& filename, bool activateIt = true) ||
|-

|-
| bool || SaveProject || (cbProject* project) ||
|-

|-
| bool || SaveProjectAs || (cbProject* project) ||
|-

|-
| bool || SaveActiveProject || ( ) ||
|-

|-
| bool || SaveActiveProjectAs || ( ) ||
|-

|-
| bool || SaveAllProjects || ( ) ||
|-

|-
| bool || CloseProject || (cbProject* project, bool dontsave = false, bool refresh = true) ||
|-

|-
| bool || CloseActiveProject || (bool dontsave = false) ||
|-

|-
| bool || CloseAllProjects || (bool dontsave = false) ||
|-

|-
| cbProject* || NewProject || (const wxString& filename = wxEmptyString) ||
|-

|-
| int || AddFileToProject || (const wxString& filename, cbProject* project = 0L, int target = -1) ||
|-

|-
| int || AskForBuildTargetIndex || (cbProject* project = 0L) ||

|-
| void || RebuildTree || ( ) ||
|-

|-
| bool || AddProjectDependency || (cbProject* base, cbProject* dependsOn) ||
|-

|-
| void || RemoveProjectDependency || (cbProject* base, cbProject* doesNotDependOn) ||
|-

|-
| void || ClearProjectDependencies || (cbProject* base) ||
|-

|-
| void || RemoveProjectFromAllDependencies || (cbProject* base) ||
|-

|-
| ProjectsArray* || GetDependenciesForProject || (cbProject* base) ||
|-

|-
| void || ConfigureProjectDependencies || (cbProject* base = 0) ||
|-
|}

== EditorManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || Configure || ( ) ||
|-

|-
| cbEditor* || New || (const wxString& newFileName = wxEmptyString) ||
|-

|-
| cbEditor* || Open || (const wxString& filename) ||
|-

|-
| cbEditor* || IsBuiltinOpen || (const wxString& filename) ||
|-

|-
| cbEditor* || GetBuiltinEditor || (const wxString& filename)|(int index) ||
|-

|-
| cbEditor* || GetBuiltinActiveEditor || ( ) ||
|-

|-
| EditorBase* || GetActiveEditor || ( ) ||
|-

|-
| void || ActivateNext || ( ) ||
|-

|-
| void || ActivatePrevious || ( ) ||
|-

|-
| bool || SwapActiveHeaderSource || ( ) ||
|-

|-
| bool || CloseActive || (bool dontsave = false) ||
|-

|-
| bool || Close || (const wxString& filename,bool dontsave = false)|(int index,bool dontsave = false),(EditorBase* editor,bool dontsave = false) ||
|-

|-
| bool || CloseAll || (bool dontsave=false) ||
|-

|-
| bool || Save || (const wxString& filename)|(int index)||
|-

|-
| bool || SaveActive || ( ) ||
|-

|-
| bool || SaveAs || (int index) ||
|-

|-
| bool || SaveActiveAs || ( ) ||
|-

|-
| bool || SaveAll || ( ) ||
|-

|-
| int || ShowFindDialog || (bool replace, bool explicitly_find_in_files = false),bool ||
|-

|}

== UserVariableManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || Exists || (const wxString& variable) ||
|-

|}

== IO namespace ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || DirectoryExists || (const wxString& dir) ||
|-

|-
| wxString || SelectDirectory || (const wxString& message, const wxString& initialPath, bool showCreateDirButton) ||
|-

|-
| bool || '''CreateDirectory''' || (const wxString& full_path, int perms) || arg1=dir, arg2=permissions
|-

|-
| bool || '''RemoveDirectory''' || (const wxString& src) ||
|-

|-
| bool || '''CopyFile''' ||(const wxString& src, const wxString& dst, bool overwrite) || src,dest,overwrite
|-

|-
| bool || '''RenameFile''' || (const wxString& src, const wxString& dst) || old,new
|-

|-
| bool || '''RemoveFile''' || (const wxString& src) ||
|-

|-
| bool || FileExists || (const wxString& file) ||
|-

|-
| wxString || SelectFile || (const wxString& title, const wxString& defaultFile, const wxString& filter) ||
|-

|-
| bool || ReadFileContents || (const wxString& filename) ||
|-

|-
| bool || '''WriteFileContents''' || (const wxString& filename, const wxString& contents) || filename,contents
|-

|-
| int || '''Execute''' || (const wxString& command) ||
|-

|-
| wxString || '''ExecuteAndGetOutput''' || (const wxString& command) ||
|-

|-
| wxString || GetCwd || ( ) ||
|-

|-
| void || SetCwd || (const wxString& dir) || directory (currently working directory)
|-

|}

'''Notes:'''
The namespaces are accesses by prepending it's name (e.g. "IO.") to the scripting function, e.g. "IO.DirectoryExists(...)". "::" is only used when declaring the members of the namespace.
The functions in bold are going through the scripts security layer so there is no guarantee calling them will succeed. You should always examine the return value...
There exists one constant too, named ''allowInsecureScripts'', which allow you to test whether Code::Blocks was compiled with the functions going through the security layer.

== CompilerFactory ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || IsValidCompilerID || (const wxString& id) ||
|-

|-
| int || GetCompilerIndex || (const wxString& id) ||
|-

|-
| wxString || GetDefaultCompilerID || ( ) ||
|-

|-
| wxString || GetCompilerVersionString || (const wxString& Id) ||
|-

|-
| bool || CompilerInheritsFrom || ( ) ||
|-

|}

== wxString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || operator+ || ||
|-

|-
| bool || operator< || ||
|-

|-
| bool || operator<= || ||
|-

|-
| bool || operator>= || ||
|-

|-
| bool || operator> || ||
|-

|-
| int || Find || wxString ||
|-

|-
| bool || Matches || wxString ||
|-

|-
| void || AddChar || char ||
|-

|-
| char || GetChar || int ||
|-

|-
| bool || IsEmpty || ||
|-

|-
| int || Length || ||
|-

|-
| int || length || || same as Length()
|-

|-
| int || len || || same as Length()
|-

|-
| int || size || || same as Length()
|-

|-
| wxString || Lower || ||
|-

|-
| wxString || LowerCase || || same as Lower()
|-

|-
| void || MakeLower || ||
|-

|-
| wxString || Upper || ||
|-

|-
| wxString || UpperCase || || same as Upper()
|-

|-
| void || MakeUpper || ||
|-

|-
| wxString || Mid || int,int ||
|-

|-
| void || Remove || int,int ||
|-

|-
| void || RemoveLast || ||
|-

|-
| int || Replace || wxString,wxString[,bool] ||
|-

|-
| wxString || Right || int ||
|-

|-
| wxString || AfterFirst || char ||
|-

|-
| wxString || AfterLast || char ||
|-

|-
| wxString || BeforeFirst || char ||
|-

|-
| wxString || BeforeLast || char ||
|-
|}
''NOTE: Is instantiated in a script using: local my_wxstring = ::wxString();

== wxArrayString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Add || wxString, size_t || arg1=string, arg2=number of copies to add
|-

|-
| void || Clear || ||
|-

|-
| int || GetCount || ||
|-

|-
| wxString || Item || int ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxarraystring = ::wxArrayString();

== wxColour ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| byte || Red || ||
|-

|-
| byte || Green || ||
|-

|-
| byte || Blue || ||
|-

|-
| void || Set || byte,byte,byte ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxcolour = ::wxColour();

== ProjectFile ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddBuildTarget || (const wxString& targetName)||
|-

|-
| void || RenameBuildTarget || (const wxString& oldTargetName, const wxString& newTargetName) ||
|-

|-
| void || RemoveBuildTarget || (const wxString& targetName)||
|-

|-
| wxString || GetBaseName || ( ) ||
|-

|-
| wxString || GetObjName || ( ) ||
|-

|-
| void || SetObjName || (const wxString& targetName) ||
|-

|-
| cbProject* || GetParentProject || ( ) ||
|-

|-
| wxString|| GetCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetCustomBuildCommand || (const wxString& compilerId, const wxString& newBuildCommand) ||
|-

|-
| bool || GetUseCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetUseCustomBuildCommand || (const wxString& compilerId, bool useCustomBuildCommand) ||
|-

|-
| wxFileName || file || || (variable)
|-

|-
| wxString || relativeFilename || || (variable)
|-

|-
| wxString || relativeToCommonTopLevelPath || || (variable)
|-

|-
| bool || compile || || (variable)
|-

|-
| bool || link || || (variable)
|-

|-
| int || weight || || (variable)
|-

|-
| wxString || compilerVar || || (variable)
|-

|}

== CompileOptionsBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddPlatform || (int platform) || windows,unix,mac
|-

|-
| void || RemovePlatform || (int platform) ||
|-

|-
| void || SetPlatforms || (int platform) ||
|-

|-
| int || GetPlatforms || ||
|-

|-
| bool || SupportsCurrentPlatform || ||
|-

|-
| void || SetLinkerOptions || (const wxArrayString& linkerOpts) ||
|-

|-
| void || SetLinkLibs || (const wxArrayString& linkLibs) ||
|-

|-
| void || SetCompilerOptions || (const wxArrayString& compilerOpts) ||
|-

|-
| void || SetIncludeDirs || (const wxArrayString& includeDirs) ||
|-

|-
| void || SetResourceIncludeDirs || (const wxString& option) ||
|-

|-
| void || SetLibDirs || (const wxArrayString& libDirs) ||
|-

|-
| void || SetCommandsBeforeBuild || (const wxArrayString& commands) ||
|-

|-
| void || SetCommandsAfterBuild || (const wxArrayString& commands) ||
|-

|-
| wxArrayString || GetLinkerOptions || ||
|-

|-
| wxArrayString || GetLinkLibs || ||
|-

|-
| wxArrayString || GetCompilerOptions || ||
|-

|-
| wxArrayString || GetIncludeDirs || ||
|-

|-
| wxArrayString || GetResourceIncludeDirs || ||
|-

|-
| wxArrayString || GetLibDirs || ||
|-

|-
| wxArrayString || GetCommandsBeforeBuild || ||
|-

|-
| wxArrayString || GetCommandsAfterBuild || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || (bool modified) ||
|-

|-
| void || AddLinkerOption || (const wxString& option) ||
|-

|-
| void || AddLinkLib || (const wxString& lib) ||
|-

|-
| void || AddCompilerOption || (const wxString& option)||
|-

|-
| void || AddIncludeDir || (const wxString& option) ||
|-

|-
| void || AddResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || AddLibDir || (const wxString& option) ||
|-

|-
| void || AddCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || AddCommandsAfterBuild || (const wxString& command) ||
|-

|-
| void || RemoveLinkerOption || (const wxString& option) ||
|-

|-
| void || RemoveLinkLib || (const wxString& lib) ||
|-

|-
| void || RemoveCompilerOption || (const wxString& option) ||
|-

|-
| void || RemoveIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveLibDir || (const wxString& option) ||
|-

|-
| void || RemoveCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || RemoveCommandsAfterBuild || (const wxString& command) ||
|-

|-
| bool || GetAlwaysRunPostBuildSteps || ||
|-

|-
| void || SetAlwaysRunPostBuildSteps || (bool always) ||
|-

|-
| void || SetBuildScripts || (const wxArrayString& scripts) ||
|-

|-
| wxArrayString || GetBuildScripts || ||
|-

|-
| void || AddBuildScript || (const wxString& script) ||
|-

|-
| void || RemoveBuildScript || (const wxString& script) ||
|-

|-
| bool || SetVar || (const wxString& key, const wxString& value, bool onlyIfExists = false) ||
|-

|-
| wxString || GetVar || (const wxString& key) ||
|-

|-
| bool || UnsetVar || (const wxString& key) ||
|-

|-
| void || UnsetAllVars || ( ) ||
|-

|}

== CompileTargetBase ==
Extends CompileOptionsBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetTargetFilenameGenerationPolicy || enum, enum ||
|-

|-
| wxString || GetFilename || ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || SetOutputFilename || wxString ||
|-

|-
| void || SetWorkingDir || wxString ||
|-

|-
| void || SetObjectOutput || wxString ||
|-

|-
| void || SetDepsOutput || wxString ||
|-

|-
| OptionsRelation || GetOptionRelation || OptionsRelationType ||
|-

|-
| void || SetOptionRelation || OptionsRelationType,OptionsRelation ||
|-

|-
| wxString || GetWorkingDir || ||
|-

|-
| wxString || GetObjectOutput || ||
|-

|-
| wxString || GetDepsOutput || ||
|-

|-
| wxString || GetOutputFilename || ||
|-

|-
| wxString || SuggestOutputFilename || ||
|-

|-
| wxString || GetExecutableFilename || ||
|-

|-
| wxString || GetDynamicLibFilename || ||
|-

|-
| wxString || GetDynamicLibDefFilename || ||
|-

|-
| wxString || GetStaticLibFilename || ||
|-

|-
| wxString || GetBasePath || ||
|-

|-
| void || SetTargetType || TargetType ||
|-

|-
| TargetType || GetTargetType || ||
|-

|-
| wxString || GetExecutionParameters || ||
|-

|-
| void || SetExecutionParameters || wxString ||
|-

|-
| wxString || GetHostApplication || ||
|-

|-
| void || SetHostApplication || wxString ||
|-

|-
| void || SetCompilerID || wxString ||
|-

|-
| wxString || GetCompilerID || ||
|-

|-
| wxString || GetMakeCommandFor || enum ||
|-

|-
| void || SetMakeCommandFor || enum,wxString ||
|-

|-
| bool || MakeCommandsModified || ||
|-

|}

== ProjectBuildTarget ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| cbProject* || GetParentProject || ||
|-

|-
| wxString || GetFullTitle || ||
|-

|-
| wxString || GetExternalDeps || ||
|-

|-
| void || SetExternalDeps || wxString ||
|-

|-
| void || SetAdditionalOutputFiles || wxString ||
|-

|-
| wxString || GetAdditionalOutputFiles || ||
|-

|-
| bool || GetIncludeInTargetAll || ||
|-

|-
| void || SetIncludeInTargetAll || bool ||
|-

|-
| bool || GetCreateDefFile || ||
|-

|-
| void || SetCreateDefFile || bool ||
|-

|-
| bool || GetCreateStaticLib || ||
|-

|-
| void || SetCreateStaticLib || bool ||
|-

|-
| bool || GetUseConsoleRunner || ||
|-

|-
| void || SetUseConsoleRunner || bool ||
|-

|}

== cbProject ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetMakefile || ||
|-

|-
| void || SetMakefile || wxString ||
|-

|-
| bool || IsMakefileCustom || ||
|-

|-
| void || SetMakefileCustom || bool ||
|-

|-
| bool || CloseAllFiles || bool ||
|-

|-
| bool || SaveAllFiles || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveLayout || ||
|-

|-
| bool || LoadLayout || ||
|-

|-
| bool || ShowOptions || || Display the project options dialog
|-

|-
| wxString || GetCommonTopLevelPath || ||
|-

|-
| int || GetFilesCount || || Returns number of files in the project
|-

|-
| ProjectFile* || GetFile || int ||
|-

|-
| ProjectFile* || GetFileByFilename || wxString,bool,bool || See API docs for cbProject::GetFileByName
|-

|-
| bool || RemoveFile || int ||
|-

|-
| ProjectFile* || AddFile || wxString|int,wxString,bool,bool,int || See API docs for cbProject::AddFile
|-

|-
| int || GetBuildTargetsCount || ||
|-

|-
| ProjectBuildTarget* || GetBuildTarget || wxString|int ||
|-

|-
| ProjectBuildTarget* || AddBuildTarget || wxString ||
|-

|-
| bool || RenameBuildTarget || wxString|int,wxString ||
|-

|-
| ProjectBuildTarget* || DuplicateBuildTarget || wxString|int,wxString ||
|-

|-
| bool || RemoveBuildTarget || wxString|int ||
|-

|-
| bool || ExportTargetAsProject || wxString|int ||
|-

|-
| bool || BuildTargetValid || wxString|bool ||
|-

|-
| wxString || GetFirstValidBuildTargetName || bool ||
|-

|-
| void || SetDefaultExecuteTarget || wxString ||
|-

|-
| wxString || GetDefaultExecuteTarget || wxString ||
|-

|-
| bool || SetActiveBuildTarget || wxString ||
|-

|-
| wxString || GetActiveBuildTarget || ||
|-

|-
| int || SelectTarget || int,bool ||
|-

|-
| ProjectBuildTarget* || GetCurrentlyCompilingTarget || ||
|-

|-
| void || SetCurrentlyCompilingTarget || ProjectBuildTarget* ||
|-

|-
| PCHMode || GetModeForPCH || ||
|-

|-
| void || SetModeForPCH || PCHMode ||
|-

|-
| void || SetExtendedObjectNamesGeneration || bool ||
|-

|-
| bool || GetExtendedObjectNamesGeneration || ||
|-

|-
| void || SetNotes || wxString ||
|-

|-
| wxString || GetNotes || ||
|-

|-
| void || SetShowNotesOnLoad || bool ||
|-

|-
| bool || GetShowNotesOnLoad || ||
|-

|-
| void || ShowNotes || bool,bool ||
|-

|-
| void || AddToExtensions || wxString ||
|-

|-
| bool || DefineVirtualBuildTarget || wxString,wxArrayString ||
|-

|-
| bool || HasVirtualBuildTarget|| wxSring ||
|-

|-
| bool || RemoveVirtualBuildTarget|| wxString ||
|-

|-
| wxArrayString || GetVirtualBuildTargets|| ||
|-

|-
| wxArrayString || GetVirtualBuildTargetGroup || wxString ||
|-

|-
| wxArrayString || GetExpandedVirtualBuildTargetGroup|| wxString ||
|-

|-
| bool || CanAddToVirtualBuildTarget || wxSring,wxString ||
|-

|-
| void || SetTitle || wxSring ||
|-
|}

== EditorBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| wxString || GetFilename || ||
|-

|-
| void || SetFilename || wxString ||
|-

|-
| wxString || GetShortName || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || Activate || ||
|-

|-
| bool || Close || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || IsBuiltinEditor || ||
|-

|-
| bool || ThereAreOthers || ||
|-

|-
| void || GotoLine || int,bool ||
|-

|-
| void || ToggleBreakpoint || int,bool ||
|-

|-
| bool || HasBreakpoint || int ||
|-

|-
| void || GotoNextBreakpoint || ||
|-

|-
| void || GotoPreviousBreakpoint || ||
|-

|-
| void || ToggleBookmark || int,bool ||
|-

|-
| bool || HasBookmark || int ||
|-

|-
| void || GotoNextBookmark || ||
|-

|-
| void || GotoPreviousBookmark || ||
|-

|-
| void || Undo || ||
|-

|-
| void || Redo || ||
|-

|-
| void || Cut || ||
|-

|-
| void || Copy || ||
|-

|-
| void || Paste || ||
|-

|-
| bool || CanUndo || ||
|-

|-
| bool || CanRedo || ||
|-

|-
| bool || CanPaste || ||
|-

|-
| bool || HasSelection || ||
|-

|}

== cbEditor ==
Extends EditorBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetEditorTitle || wxString ||
|-

|-
| ProjectFile* || GetProjectFile || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveAs || ||
|-

|-
| void || FoldAll || ||
|-

|-
| void || UnfoldAll || ||
|-

|-
| void || ToggleAllFolds || ||
|-

|-
| void || FoldBlockFromLine || int ||
|-

|-
| void || UnfoldBlockFromLine || int ||
|-

|-
| void || ToggleFoldBlockFromLine || int ||
|-

|-
| int || GetLineIndentInSpaces || int ||
|-

|-
| wxString || GetLineIndentString || int ||
|-

|-
| void || Touch || ||
|-

|-
| bool || Reload || bool ||
|-

|-
| void || Print || bool,PrintColourMode,bool ||
|-

|-
| void || AutoComplete || ||
|-

|-
| bool || AddBreakpoint || int,bool ||
|-

|-
| bool || RemoveBreakpoint || int,bool ||
|-

|-
| void || SetText || wxString || this is not present in cbEditor; included to help scripts edit text
|-

|-
| wxString || GetText || || this is not present in cbEditor; included to help scripts edit text
|-

|}

== Constants ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 0px solid gray"
!Constant
!Type
!Remarks
|-

|-
| PLATFORM || int || this defines the platform Code::Blocks is currently running on. It is equal to only one of the following PLATFORM_* constants
|-

|-
| PLATFORM_MSW || int || All Windows platforms
|-

|-
| PLATFORM_GTK || int || All GTK platforms (Linux, BSD, Solaris, Darwin, etc.)
|-

|-
| PLATFORM_MAC || int || All Mac platforms
|-

|-
| PLATFORM_OS2 || int || OS/2 platform
|-

|-
| PLATFORM_X11 || int || All X11 platforms
|-

|-
| PLATFORM_UNKNOWN || int || Unknown platform. Please inform us if PLATFORM == PLATFORM_UNKNOWN so we can make this platform known too ;)
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog flags'''
|-

|-
| wxOK || int || Flag for Message() 's third argument (flags).
|-

|-
| wxYES_NO || int || -"-
|-

|-
| wxCANCEL || int || -"-
|-

|-
| wxICON_QUESTION || int || -"-
|-

|-
| wxICON_INFORMATION || int || -"-
|-

|-
| wxICON_WARNING || int || -"-
|-

|-
| wxICON_ERROR || int || -"-
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog return values'''
|-

|-
| wxID_OK || int ||
|-

|-
| wxID_YES || int ||
|-

|-
| wxID_NO || int ||
|-

|-
| wxID_CANCEL || int ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelationType'''
|-

|-
| ortCompilerOptions || enum ||
|-

|-
| ortLinkerOptions || enum ||
|-

|-
| ortIncludeDirs || enum ||
|-

|-
| ortLibDirs || enum ||
|-

|-
| ortResDirs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelation'''
|-

|-
| orUseParentOptionsOnly || enum ||
|-

|-
| orUseTargetOptionsOnly || enum ||
|-

|-
| orPrependToParentOptions || enum ||
|-

|-
| orAppendToParentOptions || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TargetType'''
|-

|-
| ttExecutable || enum ||
|-

|-
| ttConsoleOnly || enum ||
|-

|-
| ttStaticLib || enum ||
|-

|-
| ttDynamicLib || enum ||
|-

|-
| ttCommandsOnly || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum MakeCommand'''
|-

|-
| mcClean || enum ||
|-

|-
| mcDistClean || enum ||
|-

|-
| mcBuild || enum ||
|-

|-
| mcCompileFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PCHMode'''
|-

|-
| pchSourceDir || enum ||
|-

|-
| pchObjectDir || enum ||
|-

|-
| pchSourceFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintScope'''
|-

|-
| psSelection || enum ||
|-

|-
| psActiveEditor || enum ||
|-

|-
| psAllOpenEditors || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintColourMode'''
|-

|-
| pcmBlackAndWhite || enum ||
|-

|-
| pcmColourOnWhite || enum ||
|-

|-
| pcmInvertColours || enum ||
|-

|-
| pcmAsIs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TemplateOutputType'''
|-

|-
| wizProject || enum || TemplateOutputType::totProject
|-

|-
| wizTarget || enum || TemplateOutputType::totTarget
|-

|-
| wizFiles || enum || TemplateOutputType::totFiles
|-

|-
| wizCustom || enum || TemplateOutputType::totCustom
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Other constants'''
|-

|-
| wxFILE_SEP_PATH || wxString || Path separator. "\" for windows, "/" for all other platforms
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions (e.g. "cbp")'''
|-

|-
| EXT_WORKSPACE || wxString ||
|-

|-
| EXT_CODEBLOCKS || wxString ||
|-

|-
| EXT_DEVCPP || wxString ||
|-

|-
| EXT_MSVC6 || wxString ||
|-

|-
| EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| EXT_MSVC7 || wxString ||
|-

|-
| EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| EXT_D || wxString ||
|-

|-
| EXT_F || wxString ||
|-

|-
| EXT_F77 || wxString ||
|-

|-
| EXT_F95 || wxString ||
|-

|-
| EXT_CPP || wxString ||
|-

|-
| EXT_C || wxString ||
|-

|-
| EXT_CC || wxString ||
|-

|-
| EXT_CXX || wxString ||
|-

|-
| EXT_HPP || wxString ||
|-

|-
| EXT_H || wxString ||
|-

|-
| EXT_HH || wxString ||
|-

|-
| EXT_HXX || wxString ||
|-

|-
| EXT_OBJECT || wxString ||
|-

|-
| EXT_XRCRESOURCE || wxString ||
|-

|-
| EXT_STATICLIB || wxString ||
|-

|-
| EXT_DYNAMICLIB || wxString ||
|-

|-
| EXT_EXECUTABLE || wxString ||
|-

|-
| EXT_RESOURCE || wxString ||
|-

|-
| EXT_RESOURCEBIN || wxString ||
|-

|-
| EXT_XML || wxString ||
|-

|-
| EXT_SCRIPT || wxString ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions with leading dot (e.g. ".cbp")'''
|-

|-
| DOT_EXT_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_CODEBLOCKS || wxString ||
|-

|-
| DOT_EXT_DEVCPP || wxString ||
|-

|-
| DOT_EXT_MSVC6 || wxString ||
|-

|-
| DOT_EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_MSVC7 || wxString ||
|-

|-
| DOT_EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_D || wxString ||
|-

|-
| DOT_EXT_F || wxString ||
|-

|-
| DOT_EXT_F77 || wxString ||
|-

|-
| DOT_EXT_F95 || wxString ||
|-

|-
| DOT_EXT_CPP || wxString ||
|-

|-
| DOT_EXT_C || wxString ||
|-

|-
| DOT_EXT_CC || wxString ||
|-

|-
| DOT_EXT_CXX || wxString ||
|-

|-
| DOT_EXT_HPP || wxString ||
|-

|-
| DOT_EXT_H || wxString ||
|-

|-
| DOT_EXT_HH || wxString ||
|-

|-
| DOT_EXT_HXX || wxString ||
|-

|-
| DOT_EXT_OBJECT || wxString ||
|-

|-
| DOT_EXT_XRCRESOURCE || wxString ||
|-

|-
| DOT_EXT_STATICLIB || wxString ||
|-

|-
| DOT_EXT_DYNAMICLIB || wxString ||
|-

|-
| DOT_EXT_EXECUTABLE || wxString ||
|-

|-
| DOT_EXT_RESOURCE || wxString ||
|-

|-
| DOT_EXT_RESOURCEBIN || wxString ||
|-

|-
| DOT_EXT_XML || wxString ||
|-

|-
| DOT_EXT_SCRIPT || wxString ||
|-

|}

== See also ==

* [[Scripting Code::Blocks|Scripting index]]

User documentation

2009-01-14T11:37:46Z

Jens: /* Compilers */

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

'''[[wxSmith tutorials]]'''
:Information about how to use wxSmith RAD editor

'''[[Building an Non-Unicode Win32 Code::Blocks]]'''
:Information about how to modify the Code::Blocks project files for an Non-Unicode build of Code::Blocks.

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

== Application development ==

* [[Builtin variables]]
* [[Recommended global variables]]
* [[Code::Blocks variable types synthesis]]
* [[Debugging with Code::Blocks]]
* [[Adding support for non C/C++ files to the build system]]

== 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]]
* [[Cross_Compiling_wxWidgets_Applications_on_Linux|Cross compiling wxWidgets applications on Linux]]
* [[Integrating Microsoft Visual Toolkit 2003 with Code::Blocks IDE]]
* [[Integrating Microsoft Visual C 6 with Code::Blocks IDE]]
* [[64Bit Windows|Setting up for 64-bit windows development with Mirosoft compilers]]
* [[Using the Code::Blocks IDE with SDCC on PIC MCUs]]
* [[Using Code::Blocks with Open Watcom]]

== Third-party libraries ==

* [[BoostWindowsQuickRef|Using Boost with Code::Blocks (Windows)]]
* [[WxWindowsQuickRef|Using wxWidgets with Code::Blocks (Windows)]]
* [[Using SDL with Code::Blocks]]
* [[Using GLFW with Code::Blocks]]

== User interface development ==

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

Cross Compiling wxWidgets Applications on Linux

2008-08-24T19:38:36Z

Jens: /* Fixing build options */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows with wxWidgets dll's compiled on MS Windows, so I prefer using the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' for statically linked executables or you have to make sure the appropriate dll's exist on the target system. 
In any case the needed dll's have to be in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's. 
I wasn't able to use dll's build on windows together with a cross-compiled executable. Because of that I prefer a statically linked program that only needs '''mingwm10.dll'''. By doing so I avoid runtime errors.

'''mingwm10.dll''' is part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T19:23:08Z

Jens: /* Compile */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' for statically linked executables or you have to make sure the appropriate dll's exist on the target system. 
In any case the needed dll's have to be in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's. 
I wasn't able to use dll's build on windows together with a cross-compiled executable. Because of that I prefer a statically linked program that only needs '''mingwm10.dll'''. By doing so I avoid runtime errors.

'''mingwm10.dll''' is part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T16:28:56Z

Jens: /* Compile */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' if you linked the wxWidgets dll's statically or you have to make sure the appropriate dll's exist on the target system in the same directory or at any other place in the search path. 
I think the most secure way is to ditribute them in the executables directory to make sure they don't interfere with existing wxWidgets dll's.

It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T16:24:26Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T16:05:10Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shared version of wxWidgets and to run it on MS WIndows with the native dll's. It only works if it is statically linked or you distribute the needed dll's that can be found in '''/usr/i586-mingw32msvc/lib/''' and put them into the executables directory. Putting them into the search path might interfere with existing wxWidgets dll's on windows.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T16:02:18Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shared version of wxWidgets and to run it on MS WIndows with the native dll's. It only works if it is statically linked or you distribute the needed dll's that can be found in /usr/i586-mingw32msvc/lib/.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-24T15:59:30Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shared version of wxWidgets and to run it on MS WIndows with the native dll's. It only works with statically linked dll's .

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-16T13:16:21Z

Jens: /* Fixing build options */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other linker options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

* The line in '''Linker Settings -> Other options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --cflags`
[[Image:CompilerSettings.png|thumb|none|Compiler settings]]

* The line in '''Linker Settings -> Other linker options''' should look like that:
`wx-config --host=i586-mingw32msvc --static --libs`
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-08-10T15:47:28Z

Jens: /* wxWidgets cross-build */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.8 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.

=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-03-27T21:32:05Z

Jens:

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:32, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-03-27T21:31:24Z

Jens: /* Setup the debugger */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:15, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setting up the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-03-27T21:30:50Z

Jens: /* Debugging */

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:15, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
===Known limitations===
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''. 
Therefore there are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. 
It does not know anything about special instructions for '''MS WIndows''' to use while debugging.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and that its api is not 100% compatible with the original '''MS Windows'''-api. 
It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works (better) in all cases.

===Setup the debugger===
Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

The debugger can be used as the native '''gdb''' for '''Linux''' from within '''Code::Blocks'''.

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-03-27T21:15:39Z

Jens:

[[Category:User Documentation]]

If this document is helpful for you, or if you have questions or suggestions feel free to send me a mail or Personal Message. 

If there are errors or you miss something feel free to edit the document to make it better.

[[User:Jens|Jens]]

22:15, 27 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''.
There are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. It does not know anything about special instructions to use while debugging, of course.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and the its api is not 100% compatible with the original '''MS Windows'''-api. It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works better.

Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

Happy debugging.

=(External) Links=

Here are some links that contain interesting articles and/or discussions about cross-compiling.

They are surely not complete and they are not in any special order.

[http://en.wikipedia.org/wiki/Cross_compiler http://en.wikipedia.org/wiki/Cross_compiler] 
[http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux http://www.wxwidgets.org/wiki/index.php/Cross-Compiling_Under_Linux] 
[https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers https://wiki.codeblocks.org/index.php?title=Code::Blocks_and_Cross_Compilers] 
[http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc http://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc] 
[/index.php/topic,7978.0.html /index.php/topic,7978.0.html] 
[/index.php/topic,3343.0.html /index.php/topic,3343.0.html] 
[/index.php/topic,6876.0.html /index.php/topic,6876.0.html] 
[/index.php/topic,7454.0.html /index.php/topic,7454.0.html]

Cross Compiling wxWidgets Applications on Linux

2008-03-27T20:56:34Z

Jens:

[[Category:User Documentation]]
This document is still under construction by [[User:Jens|Jens]], but I'm working on it. Please be patient.

01:00, 20 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
Debugging MS Windows apps with Code::Blocks works, but it does not work reliable.

I think one problem is that '''gdb''' has a slightly different syntax on '''Linux''' and '''MS Windows'''. '''Code::Blocks''' is aware of this and therefore uses different instructions when running '''gdb''' on '''Linux''' and on '''MS Windows'''.
There are some <code>#ifdef</code>'s in source code.

The problem is that '''Code::Blocks''' on '''Linux''' is compiled for ... right '''Linux'''. It does not know anything about special instructions to use while debugging, of course.

Annother problem might be the fact that [http://www.winehq.org/ wine] normally uses it own dll's and the its api is not 100% compatible with the original '''MS Windows'''-api. It might be possible to do some tweaking, or to use real '''MS Windows''' dll's, but that can lead to licensing problems and there is of course no guarantee that it works better.

Nevertheless it is possible to debug '''MS Windows''' applications from within '''Code::Blocks''':

Download a recent '''gdb'''-package (for '''MS Windows''' of course) from [http://www.mingw.org/ www.mingw.org/] and unzip to any directory you want. 
I put it into:
~/.wine/drive_c/MinGW/
There should be at least a <code>bin</code>-subdirectory now that contains '''gdb.exe'''. 
Typing
~/.wine/drive_c/MinGW/bin/gdb.exe -v
at the console should lead to something like this:
GNU gdb 6.7.50.20071127
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
Wine exited with a successful status

The easiest way to use '''gdb.exe''' from within Code::Blocks is to create a simple shell-script (I called it '''i586-mingw32msvc-gdb''') :
#!/bin/sh

wine /home/jens/.wine/drive_c/MinGW/bin/gdb.exe "$@"

You have to fix the path inside the script to point to your '''gdb.exe'''.

Make the script executable and place it in <code>/usr/bin</code>.
chmod 755 i586-mingw32msvc-gdb
sudo chown root.root i586-mingw32msvc-gdb
sudo mv i586-mingw32msvc-gdb /usr/bin

If you now run:
i586-mingw32msvc-gdb -v
from the console you should get the same output as above when calling '''gdb.exe''' directly.

You now have to put the name of the script in the appropriate text-box in '''Toolchain executables''' as described [[#Fix_Toolchain_Executables|above]].

Cross Compiling wxWidgets Applications on Linux

2008-03-20T00:00:02Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-19T23:59:15Z

Jens:

[[Category:User Documentation]]
This document is still under construction by [[User:Jens|Jens]], but I'm working on it. Please be patient.

For the moment you can also look [/index.php/topic,7978.0.html here]

00:59, 20 March 2008 (CET)

--------------------

This document describes how to setup Code::Blocks to compile applications that use the wxWidgets toolkit for MS Windows from within Linux. 
I tested it on [http://www.debian.org/ debian] sid, but it should also work on other distributions.

=Needed software=
==Code::Blocks==
You can download prebuild binaries Code::Blocks from the [https://www.codeblocks.org/downloads/binaries download page].

If you prefer to compile Code::Blocks yourself, you have the choice between downloading the sourcecode of the actual release as tarball from the official [https://www.codeblocks.org/downloads/6 download page] or to download the newest version via [https://www.codeblocks.org/downloads/7 svn]. A guide to build Code::Blocks from svn can be found in the [[Nightly Cookbook]].

The newest svn-versions are also available as prebuild binaries made available by users. 
You can find links to the downloadpages in the actual posts in the [/index.php/board,20.0.html Nightly Builds] forum.
==MinGW32==
MingW32 is the cross-build version of the [http://www.mingw.org/ '''Min'''imalistic '''G'''nu for '''W'''indows] compiler suite (a port of the Gnu Compiler Suite for the MS Windows platform). 
It is part of many linux distributions.

On debian the basepackage is called ''mingw32'' and can be installed by typing
sudo apt-get install mingw32
at the command-line. 
It's up to you to find out the name of the package and install it using your preferred package-manager or either compile it by hand.
==wxWidgets cross-build==
For debian-users I have made prebuild binary packages available on my [http://apt.jenslody.de/ server]. I guess they are also usable on Ubuntu, but you have to try it yourself.

I don't know if there are downloadable packages available in/for other distros, but you can build it on your own.

You can download the source-code either from my [http://apt.jenslody.de/pool/ server's software pool] or from the [http://www.wxwidgets.org/ wxWidgets] download page.

Unpack the sources and type configure it with
./configure prefix=/usr/i586-mingw32msvc --host=i586-mingw32msvc --enable-unicode --build=`./config.guess` --disable-shared
The prefix depends on your MinGW32 installation, either does the host. The other switches can be changed as you prefer it, with oine exception (at the moment): 
I wasn't able to build any application with the shred version of wxWidgets and to run it on MS WIndows. It only works with statically linked dll's.

You can see the available switches with
./configure --help

If everything wents right you get a message like this:

Configured wxWidgets 2.8.7 for `i586-pc-mingw32msvc'

Which GUI toolkit should wxWidgets use? msw
Should wxWidgets be compiled into single library? yes
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? no
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg builtin
png builtin
regex builtin
tiff builtin
zlib builtin
odbc no
expat builtin
libmspack no
sdl no

Now you can build the libraries with
make
make install

If you use my binaries you should be able to call <code>wx-config</code> directly. 
As test you can run <pre>wx-config --list</pre>.
The ouput should look like
Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
base-unicode-release-2.8

Also available in /usr:
i586-mingw32msvc-msw-unicode-debug-2.8
i586-mingw32msvc-msw-unicode-release-2.8
i586-mingw32msvc-msw-unicode-release-static-2.8

You can see the cross-compile configurations starting with ''i586-mingw32msvc-msw''.

If you don't see any cross-compile configurations you have to use the appropriate wx-config directly:
/usr/i586-mingw32msvc/lib/wx/config/i586-mingw32msvc-msw-unicode-release-static-2.8 --list
(The instruction may differ according to your configuration.) 
If the output shows your cross-build targets, everything is okay. If not something went wrong with compiling your wxWidgets cross-libraries.

In the further part of this document I'll use the paths I used in the example configure-line.
=Preparing Code::Blocks=
If everything is installed you have to prepare Code::Blocks for cross-compiling.

Therefore you need a special compiler based on '''''GNU GCC compiler'''''
==''Create'' Compiler==

*Open '''''Settings -> Compiler and Debugger ... -> Global compiler settings'''''.
*Chose '''''GNU GCC compiler'''''.
*Click Copy.
*Give your new Compiler a meaningful name.
[[Image:DuplicateCompiler.png|thumb|none|Duplicate Compiler]]

*Chose the cross-compiler.
==Fix Search directories==
*Open the Search directories notebook.
*Change the search directory for the Compiler to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsCompiler.png|thumb|none|Search Directories -> Compiler]]

*for the Linker to
/usr/i586-mingw32msvc/lib/
[[Image:SearchDirsLinker.png|thumb|none|Search Directories -> Linker]]

*and the Resource Compiler also to
/usr/i586-mingw32msvc/include/
[[Image:SearchDirsResources.png|thumb|none|Search Directories -> Resource Compiler]]
==Fix Toolchain Executables==
*Open the Toolchain executables notebook.
*Change the Program Files as follows:
:*'''C Compiler''' to:
:<pre>i586-mingw32msvc-gcc</pre>
:*'''C++ Compiler''' and '''Linker for dynamic libs''' to:
:<pre>i586-mingw32msvc-g++</pre>
:*'''Linker for static libs''' to:
:<pre>i586-mingw32msvc-ar</pre>
:*'''Debugger''' to:
:<pre>i586-mingw32msvc-gdb</pre>
:*'''Resource compiler''' to:
:<pre>`wx-config --host=i586-mingw32msvc --rescomp`</pre>
:*Leave '''Make''' unchanged
[[Image:ToolchainExecutables.png|thumb|none|Toolchain executables]]

One word to the debugger executable: there is no cross-debugger available in the MinGW-suite ! 
But for rudimentary debugging we can use the MS Windows version of the ''gdb''-debugger avaible on the [http://www.mingw.org/ MinGW] download site.

But debugging works not reliable, I think it's because there are some ''ifdef'''s in the Code::Blocks sources for the debugger-plugin dealing with differences between the linux and the MS Windows versions of ''gdb'' and the different application structure. Even if we use a MS WIndows executable as debugger, Code::Blocks believes it works on linux (and that's of course right) and is therefore compiled for the linux ''gdb.''

There is also a real cross-debugger for MS WIndows applications available, that belongs to [http://www.winehq.org/ wine], but the syntax is not compatible with the one of ''gdb,'' even if it is possible to use ''gdb'' as backend for ''winedbg''.

I will come back to the debugger and how it can be called (a shell-script) later in this document.
=Setting up your project=
You can of course use a working wxWidgets-project, but for testing I think the best way is to use the wizard and create a brand-new project.

==Creating a new build target==
If you have opened your project in Code::Blocks, go to the '''Projects''' tab in the '''Manager''' and right-click it to prepare it for cross-compiling.

Chose '''Properties..'''. from the context menu and switch to the Build targets-tab.

Select one of the build targets (I used '''Release''' for this example), click the Duplicate-button and give it a new name (WinRelease in my case).
[[Image:PropertiesDuplicate.png|thumb|none|Duplicate build target]]

Change the '''Output filename''' from '''bin/Release/<filename>''' to '''bin/WinRelease/<filename>.exe''', and uncheck at least '''Auto-generate filename extension'''.
[[Image:BuildTargets.png|thumb|none|Adapt settings of build target]]
==Fixing build options==
*In the '''Build options''' of the project you have to move <code>`wx-config --cflags`</code> from the global '''Compiler settings -> Other options''' to the one for the standard build targets ('''Debug''' and '''Release'''). 
:Do the same for '''Linker Settings -> Other options'''.

*To make it clear the '''Other options'''-tabs of the '''Compiler settings''' and '''Linker settings''' belonging to the whole project have to be empty (or only include settings that are valid for the Linux '''and''' the MS Windows targets).

*Change the compiler for '''WinRelease''' from '''GNU GCC compiler''' to '''Mingw GNU GCC Cross-Compiler for Windows''' or however you called the cross-compiler.

*The appropriate calls to '''wx-config''' for the '''WinRelease''' must have the parameter: '''--host=i586-mingw32msvc''' included and should have the parameter '''--static''' set also. 
:Until now I haven't been able to make a cross-compiled program run on MS Windows if I did not use the static libraries.

[[Image:CompilerSettings.png|thumb|none|Compiler settings]]
[[Image:LinkerSettings.png|thumb|none|Linker settings]]

If the wx-config-command does not find the correct wxWidgets configuration, you can also add a '''--prefix=/usr/i586-mingw32msvc''' or maybe another prefix if you use self-compiled libraries (it should be the same you used for '''./configure''').

==Compile==
Not much to say here.

If everything went right, you should have a real MS Windows-application in your output directory:
file bin/WinRelease/test.exe
bin/WinRelease/test.exe: MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit
If you want to run it on MS Windows you need '''mingwm10.dll''' in the same directory or at any other place in the search path. 
It's part of the '''mingw32-runtime'''-package and can be found (gzipped) in '''/usr/share/doc/mingw32-runtime/''' (at least on debian systems).

You can create console-projects in a similar way without using '''wx-config''' of course.

=Running on Linux=
==Normal run==
To run your application on Linux you will need the [http://www.winehq.org/ wine]-package.

To start a MS WIndows executable from the console (or from within Code::Blocks) you need the '''binfmt-support'''-package or however it is called in your distro.

If you run your test application it should look like this one:
[[Image:AboutBox.png|thumb|none|Dialog based example]]
==Debugging==
Coming soon...

File:AboutBox.png

2008-03-19T23:56:10Z

Jens:

File:LinkerSettings.png

2008-03-19T23:29:42Z

Jens:

File:CompilerSettings.png

2008-03-19T23:29:14Z

Jens:

File:BuildTargets.png

2008-03-19T22:51:47Z

Jens:

File:PropertiesDuplicate.png

2008-03-19T22:51:18Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T22:42:11Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T22:13:52Z

Jens:

File:ToolchainExecutables.png

2008-03-16T21:54:12Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T21:13:53Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T21:04:46Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T21:03:10Z

Jens:

File:SearchDirsResources.png

2008-03-16T20:43:11Z

Jens:

File:SearchDirsLinker.png

2008-03-16T20:43:00Z

Jens:

File:SearchDirsCompiler.png

2008-03-16T20:42:52Z

Jens:

File:DuplicateCompiler.png

2008-03-16T20:29:59Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T20:08:14Z

Jens:

Cross Compiling wxWidgets Applications on Linux

2008-03-16T18:40:13Z

Jens: