User forums > Announcements
Preparing Code::Blocks Release
MortenMacFly:
--- Quote from: code robot on March 12, 2010, 11:40:40 am ---For example: Is this the kind of thing you are looking for?
--- End quote ---
Ok - the definition shall be:
"Design a startup/splash screen for Code::Blocks which contains the logo (the cube) and the writing "Code::Blocks", including the "::". Keep the cube basically as it is, but you can do position/resize it as you like (not too small, of course) and add some fancy surroundings as seen e.g. in the splash screen of 08/02."
I didn't expect the explanation needed to be that precise. Sorry, folks.
MortenMacFly:
A short note concerning the logo contest:
Please post in a new thread in this forum, I'll set them sticky until we start a poll to find out the "winner". Notice that actually ANY contribution is welcome. We will keep all logos and designers in a record.
fantasticfears:
shall we contain the language files? and launchpad is obsolete
ptDev:
One simple question regarding the release:
Are you going to supply developers a "standard compiler bundle" and release at least one specific SDK for the same Code::Blocks build, wxWidgets and compiler versions? The wide diversity in compilers (MinGW official/TDM, MSVC, etc.) that users build their libraries with makes binary compatibility between an official C::B release and third-party plugin releases very difficult.
One example I can think of: the DoxyBlocks plugin is great, and the author released it as a binary (.cbplugin format) in sourceforge, but he compiled it against C::B svn 6182. I'm using Code::Blocks revision 6188. Thus, there is no practical way for me to get it running, unless I build both C::B and the plugin from source, everytime there is an update of either... And I'm not even going into the pain it is running the same plugin under Linux.
A definite choice of standard binary compatibility would encourage a lot more people to make their own plugins and share them as binaries.
MortenMacFly:
--- Quote from: ptDev on March 18, 2010, 12:03:25 pm ---A definite choice of standard binary compatibility would encourage a lot more people to make their own plugins and share them as binaries.
--- End quote ---
As with all other releases we will provide a SDK here, too. Plugin-Devs linking against that SDK will automatically be "compatible" with the release. However, if (for good reasons) we change the ABI for the nightlies you cannot use plugins compiled against the nightlies version in the release version, obviously. To overcome, ask the devs to compile/link against the (fixed) release SDK.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version