Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10.7z
For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb_wx2.6.3p2.7z
The 15 December 2006 build is out.
- Windows : http://prdownload.berlios.de/codeblocks/CB_20061215_rev3385_win32.7z
- Linux :
http://prdownload.berlios.de/codeblocks/CB_20061215_rev3385_Ubuntu6.06.deb (not yet)
http://prdownload.berlios.de/codeblocks/CB_20061215_rev3385_suse100+101.rpm (not yet)
http://prdownload.berlios.de/codeblocks/CB_20061215_rev3385_fc4+5.rpm (not yet)
Resolved Fixed:
- applying patch 1715 (fixing bugs 009641 and 009247 and 006965)
- SDK version pumped to 1.11.5
- Added support for the Cygwin compiler
- Implemented wxCrc32::FromFile()
- Improved MenuItemsManager
- Major scripting update:
- startup.script does not need a main() function now.
- The recently added 'App' script object provides no functions now (those that it used to provide have been moved elsewhere).
- Script plugins support (yes, plugins that are actually scripts).
- Enabled "dangerous" script-bound functions in IO script namespace providing the following operations: copy, write, delete, rename and execute.
- Added security layer for the above "dangerous" IO functions.
- Provided sample script that adds "Settings->Edit startup script" menu.
- Provided sample (pointless) script plugin (disabled by default).
- Wiki documentation currently being updated for all of the above changes - Last commit message was missing some debugger updates: mainly GDB support for Cygwin-based executables and cpu registers reading improvements
- Respect OS theme's window background colour in the compiler's build log
- Script functions IO.CreateDir and IO.RemoveDir renamed to IO.CreateDirectory and IO.RemoveDirectory
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem/Win XP problem)
- menu items with icon not correctly aligned (since wx263)
there seems to be a side effect in this build, at each start up CB show the compiler list and which ones are detected.
[PERSONAL NOTE] : would be nice if that compiler selection list dialog would be resizable so i t can be enlarged that everything is nicely visible.
[EDIT] : on Suse 10.2 it is also ok.
To compile svn3385 on linux ubuntu edgy, I modify the following line:
gdb_commands.h (line 1148):
#ifdef __WXMSW__
if(m_disassemblyFlavor == _T("set disassembly-flavor or32"))
{
reDisassemblyInitFuncOR32.GetMatch(output, 1).ToLong(&active, 16);
}
else
#endif
gdb_driver.cpp (line 755):
#ifdef __WXMSW__
if(flavour == _T("set disassembly-flavor or32"))
{
HandleMainBreakPoint(reBreak_or32, lines);
}
else
#endif
gdb_driver.h (line 76):
void GDB_driver::HandleMainBreakPoint(const wxRegEx& reBreak, wxString line);
Best regards,
pasgui
Quote from: killerbot on December 15, 2006, 07:19:56 PM
there seems to be a side effect in this build, at each start up CB show the compiler list and which ones are detected.
[PERSONAL NOTE] : would be nice if that compiler selection list dialog would be resizable so i t can be enlarged that everything is nicely visible.
This side effect is not present on edgy.
how to compile the latest svn on my linux box
i get this messages
:: === Code::Blocks - Unix, Debugger ===
plugins/debuggergdb/gdb_commands.h:1148: error: `m_disassemblyFlavor' was not declared in this scope
plugins/debuggergdb/gdb_commands.h:1150: error: `reDisassemblyInitFuncOR32' was not declared in this scope
plugins/debuggergdb/gdb_commands.h:1150: warning: unused variable 'reDisassemblyInitFuncOR32'
plugins/debuggergdb/gdb_commands.h:1148: warning: unused variable 'm_disassemblyFlavor'
plugins/debuggergdb/gdb_driver.cpp:757: error: `reBreak_or32' was not declared in this scope
plugins/debuggergdb/gdb_driver.cpp:757: warning: unused variable 'reBreak_or32'
:: === Build finished: 3 errors, 3 warnings ===
Quote from: PsYhLo on December 15, 2006, 08:10:04 PM
how to compile the latest svn on my linux box
i get this messages
:: === Code::Blocks - Unix, Debugger ===
plugins/debuggergdb/gdb_commands.h:1148: error: `m_disassemblyFlavor' was not declared in this scope
plugins/debuggergdb/gdb_commands.h:1150: error: `reDisassemblyInitFuncOR32' was not declared in this scope
plugins/debuggergdb/gdb_commands.h:1150: warning: unused variable 'reDisassemblyInitFuncOR32'
plugins/debuggergdb/gdb_commands.h:1148: warning: unused variable 'm_disassemblyFlavor'
plugins/debuggergdb/gdb_driver.cpp:757: error: `reBreak_or32' was not declared in this scope
plugins/debuggergdb/gdb_driver.cpp:757: warning: unused variable 'reBreak_or32'
:: === Build finished: 3 errors, 3 warnings ===
use rev 3387
QuoteRespect OS theme's window background colour in the compiler's build log
this didn't work for me :(
the same thing like in this thread http://forums.next.codeblocks.org/index.php?topic=4696.0
Quote from: PsYhLo on December 15, 2006, 09:29:15 PM
QuoteRespect OS theme's window background colour in the compiler's build log
this didn't work for me :(
the same thing like in this thread http://forums.next.codeblocks.org/index.php?topic=4696.0
I just noticed you were talking about linux. Yes, I just checked it in linux and you 're right: it doesn't fix it.
So wait until (probably) tomorrow.
I do not know if this is the proper place to post but...
the code completion has a bug in it. When you have a space ( " " ) in your file, the code completion categorizes it as it as a separate suggestopns.
For example,
if the file is called "Test Hi.h"
you write #include "
then it gives the suggestions "Test" then "Hi.h"
When you save any file, all trailing spasec at the and of each line are removed.
May be, it is the same bug...
I've posted this bug (#9734):
https://developer.berlios.de/bugs/?func=detailbug&bug_id=9734&group_id=5358
Sorry, I've forgot to set "Category" to this bug, please, fix it.
Quote from: dkirienko on December 16, 2006, 11:24:56 AM
When you save any file, all trailing spasec at the and of each line are removed.
May be, it is the same bug...
I've posted this bug (#9734):
https://developer.berlios.de/bugs/?func=detailbug&bug_id=9734&group_id=5358
Sorry, I've forgot to set "Category" to this bug, please, fix it.
It's a feature, not a bug.
Settings -> Editor -> Skip trailing blanks
Joseph.
Yes, I see.
Probably, student, that show be this "bug" after updating C::B for new build has this option enabled.
Thank you.
Cygwin compiler ver very good ide , but cn i ask for freebasic too . if i cn ask :oops:
Quote from: jpaterso on December 16, 2006, 12:37:52 PM
It's a feature, not a bug.
Settings -> Editor -> Skip trailing blanks
Joseph.
Mine is not a problem with the saving trailing blanks. It is the auto complete.
Quote- Enabled "dangerous" script-bound functions in IO script namespace providing the following operations: copy, write, delete, rename and execute.
Great! Was hoping to see those. (Well, mainly execute)
I was wondering if there was a way to delete a file in the project instead of just removing it from view without going into explorer?
Quote from: slymr on December 16, 2006, 06:46:16 AM
I do not know if this is the proper place to post but...
the code completion has a bug in it. When you have a space ( " " ) in your file, the code completion categorizes it as it as a separate suggestopns.
For example,
if the file is called "Test Hi.h"
you write #include "
then it gives the suggestions "Test" then "Hi.h"
Another thing when using code completion after an #include.
The layout for my projects is quite often
src/ (.cpp files go here)
src/include/ (.h files go here)
Unfortunately, code completion does not parse the directories correctly. In any file in src, as soon as I type #include "include/" all the options disappear.
Joseph.
I am also getting the compiler tools selection window on each launch, no matter what I do.
This is Win XP Home.
I hope that the next nightly build will have it fixed.
No big deal, but it would be nice if C::B remembered it.
Quote from: jacmoe on December 17, 2006, 05:53:18 PM
I am also getting the compiler tools selection window on each launch, no matter what I do.
This is Win XP Home.
I hope that the next nightly build will have it fixed.
No big deal, but it would be nice if C::B remembered it.
I have the same problem on Win2kpro(sp4) !!! :shock: