Compile Code::Blocks plugins based on a nightly - Revision history

LETARTARE: new svn

2013-09-05T14:18:22Z

new svn

LETARTARE: new svn

2013-09-05T14:14:09Z

new svn

MortenMacFly at 06:20, 23 August 2012

2012-08-23T06:20:40Z

MortenMacFly at 06:19, 23 August 2012

2012-08-23T06:19:19Z

MortenMacFly at 06:16, 23 August 2012

2012-08-23T06:16:56Z

MortenMacFly at 20:30, 22 August 2012

2012-08-22T20:30:06Z

MortenMacFly at 20:28, 22 August 2012

2012-08-22T20:28:33Z

MortenMacFly at 20:26, 22 August 2012

2012-08-22T20:26:58Z

MortenMacFly at 20:26, 22 August 2012

2012-08-22T20:26:34Z

MortenMacFly at 20:19, 22 August 2012

2012-08-22T20:19:19Z

@@ Line 6: / Line 6: @@
 * A nightly of your choice, download from [/index.php/board,20.0.html here].
 * The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. sjlj or dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
-* The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
+* The Code::Blocks sources in the revision the nightly is based on from [https://sourceforge.net/p/codeblocks/code/ here]. You usually get these, if you issue a:
    svn checkout svn://somepath@1234 working-directory
 ...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
-   svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk@8150
+   svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk@8150  working-directory
 * The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

@@ Line 9: / Line 9: @@
    svn checkout svn://somepath@1234 working-directory
 ...on the command line (having the [https://subversion.apache.org Subversion tools] installed properly). For example, to checkout trunk at revision 8150 into the folder you are currently in, issue:
-   svn checkout svn://svn.berlios.de/codeblocks/trunk@8150
+   svn checkout svn://svn.code.sf.net/p/codeblocks/code/trunk@8150
 * The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.

@@ Line 5: / Line 5: @@
 * The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
 * A nightly of your choice, download from [/index.php/board,20.0.html here].
-* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
+* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. sjlj or dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
 * The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
    svn checkout svn://somepath@1234 working-directory

@@ Line 5: / Line 5: @@
 * The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
 * A nightly of your choice, download from [/index.php/board,20.0.html here].
-* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2 ''and'' flavour (i.e. dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
+* The MinGW/GCC compiler used to build the nightly - as written in the nightly section and usually available from here [http://tdm-gcc.tdragon.net here]. Note that the version (i.e. v4.5.2) ''and'' flavour (i.e. dwarf) ''must'' match. Usually this information is available [/index.php/topic,3299.msg26011.html here].
 * The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
    svn checkout svn://somepath@1234 working-directory

@@ Line 5: / Line 5: @@
 * The wxWidgets ''sources'' (!) - no need to compile them, just download from [http://www.wxwidgets.org/downloads here] ''but exactly the version, the nightly is built on''.
 * A nightly of your choice, download from [/index.php/board,20.0.html here].
 * The Code::Blocks sources in the revision the nightly is based on from [http://developer.berlios.de/svn/?group_id=5358 here]. You usually get these, if you issue a:
    svn checkout svn://somepath@1234 working-directory
@@ Line 18: / Line 19: @@
 * Goto the plugin's build options
 * Goto linker settings
-** change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
+** Change the wxmsw28$(WX_SUFFIX) part to become "wxmsw28u_gcc_cb.dll" (the one shipped with the nightly)
-** change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly)
+** Change the codeblocks part to become "codeblocks.dll" (the one shipped with the nightly). Note that this change might actually not be needed as MinGW automatically looks for files with the extension *.dll, too...
 * Goto the "search directories" settings
-** change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
+** Change the compilers C::B related include directories (usually setup relative, like ..\..\..\include) to point to the equivalent path's where you checked out the C::B sources
-** change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
+** Change the compilers wxwidgets related include directories (usually setup like $(#WX.INCLUDE)) to point to the equivalent path's where you extracted the wxWidgets sources, or (in case of global variables like here), just adjust the global compiler variables (GCV's).
 ** Do the same with the linker and resource include path's of the plugin (note that i.e. "..\..\..\devel" should not point to the root of your nightly installation folder)
 * Note that you might need to do this at project and target level - depending on how the plugin is setup.

@@ Line 11: / Line 11: @@
 * The sources of the plugin / component you want to change should be included in this checkout, you can (however) update the specific folder to SVN HEAD, if you like.
-One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on.
+One note: This surely ''only'' works, if the SDK version is compatible to the plugin. What won't work is, if the plugin makes use of SDK methods not available in the SDK version the nightly is based on. Luckily, the SDK is quite stable and existing (stable) plugins rarely change to make use of new SDK methods.
 Now comes the "hard" part: You'll need to adjust the plugin's project file, so it links against the DLL's from the nightly (yes, MinGW can do so!) instead of the import libraries you usually compile.