I dunno where to post this since i dont see any suggestion post, so i will put it here.
I think Codeblocks SDK should be included as an integral part of codeblocks. If you need to compile some plugin or you feel like making your own, you need to download full codeblocks source and compile it entirely(or almost) just to get the sdk. This includes having to download wxwidgets sdk or even (due to posible versions mitchmatch(sp?) ) having to download wxwidget sources an compile them. Actually if you want to add a new widget you will need to get wxwidget compiled.
I would actually deploy Code::Blocks+C::BSDK+wxSDK+Doc toguether (as long as wxWidgets allow it of course). So people could just install and start developing. Maybe someone would want to use some different widget toolkit but since C::B includes a good RAD plugin (wxSmith), focusing people to use wxWidgets could be fine.
I would actually go beyond:
* Choosing a common set of crossplatform libraries (community)
(i mean choosing from the big variety that actually exists not creating them)
- this would include in example wxWidgets for widgets, SDL for graphics, OGL for 3D, etc. whatever the community thinks is right. Covering the most common actual hardware in use.
- conditions: libraries with the right license, libraries ported to the most of platforms.
* Creating Groups:
+ Code::Blocks group (IDE)
+ cross Toolchains groups responsible of providing:
-the basic precompiled toolchain for all platforms platform (gcc)
(i.e. win group provides whatever is necesary to comiple in windows, only toolchain, never libraries)
+ cross SDK groups for each platform (win, mac, linux, etc.) rsponsible of providing:
-precompile library set for that platform providing a common base SDK
-source toolchain for that platform, ready for batch C::B compilation
+ Help documentation group
-since SDK contents are common documentation only needs to be done one for all platforms.
* Deploying(what user gets)
+ Code::Blocks IDE for your WORKING platform
+ Toolchain for your WORKING platform
+ one or more SDK (includes TARGET toolchain sources compilables to your WORKING platform at SDK installation time[since you should have previously installed C::B + WORKING Toolchain])
(note: in the most common case TARGET platform will be the same as WORKING platform)
In Example:
-SDK for target platform A
-SDK for target platform B
- .......
+ Common Help set
Some efforts should be done in Code::Block:
-integrate differents SDK (you wont have now different target for proyects but different target platforms too to compile against)
-better integrated help system
...
I promise im not gonna drunk anymore ... hehehe.
