Code::Blocks Forums
User forums => Nightly builds => Topic started by: killerbot on March 07, 2006, 10:28:28 pm
-
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://download.berlios.de/codeblocks/wxmsw26u_gcc_cb.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://download.berlios.de/codeblocks/mingwm10.7z
For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://download.berlios.de/codeblocks/wxmsw26_gcc_cb.7z
The 07 March 2006 build is out.
- Windows : http://download.berlios.de/codeblocks/CB_20060307_rev2156_win32.7z
- Linux : not supported yet
Resolved Fixed:
- fixed crash on search/replace nothing (path 900 : bug 6665)
- Removed obsolete file src/sdk/wxscintilla/build/wxscintilla.cbp
- Added -r switch in OpenWatcom's compile resource command macro
- When launching a tool, its details are logged (command line and working dir) for easier user troubleshooting
- Updated Python lexer (patch #891)
- Updated CSS lexer (patch #884)
- Fixed DDE bug in windows (patch #902)
- Various little code cleanups (patches # 901, 897, 892)
- wxWidgets project templates updates (patch #862)
- Added a couple of missing #includes for non-PCH builds (patch #899)
- Ctrl-C (copy), Ctrl-V (paste), Ctrl-X (cut), Ctrl-Z (undo) and Ctrl-Shift-Z (redo) now work for logs too. The editor doesn't "steal" them anymore. Patch #890
- Renamed debugger's window "Examine memory" to "Memory dump"
- Improved debugger's "Memory dump" window. It now contains a field to enter an address and a combobox to select the bytes count to dump. It is also updated automatically
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem)
- there are several issues with Code Completion (is being redesigned : work in progress)
-
No more DDE bug club :(
-
No more DDE bug club :(
I don't get it.... :? Why does that make you put a (:()
-
No more DDE bug club :(
I don't get it.... :? Why does that make you put a (:()
Our old friend has gone away.
-
I've got an unhandled exception when i try to rebuild all targets...
I've got four target:
Release DigitalMars
Release Mingw
Release Vc++
Release OpenWatcom
It rebuilds the first one then after linking on the log appears:
------ Build: Release Mingw ...
And codeblocks crash with an unhandled exception
OpenWatcom resource compiler return error compiling a .rc file... (if it is wx.rc it complains about a missing wx.exe file...)
-
I've got an unhandled exception when i try to rebuild all targets
Post your .rpt file (crash file generated where codeblocks.exe is).
OpenWatcom resource compiler return error compiling a .rc file
Go to OpenWatcom's options and press "Reset defaults".
-
I've got an unhandled exception when i try to rebuild all targets
Post your .rpt file (crash file generated where codeblocks.exe is).
OpenWatcom resource compiler return error compiling a .rc file
Go to OpenWatcom's options and press "Reset defaults".
It doesn't add info on that file. (There was only old reports... i deleted it but nothing appens...)
By the way pressing the right button on the unhandled exception messagebox it show me another messagebox with these info:
An exception has been raised!
The application encountered an error at sdk\compiler.cpp on line 160.
The error message is:
Compiler::Init() not called or generator invalid!
Code::Blocks Version revision 2156 (...)
-
About openwatcom: it works after resetting but i can't understand why it builds a console based application instead of a gui one...
-
The fix for the "crash" (exception) has been committed already.
About compilers:
You all have to understand that I cannot possibly know all compilers and their switches to their full extent. So, if someone notices errors in a compiler's macros, and knows how to fix them, please post a patch in the patch tracker.
-
The fix for the "crash" (exception) has been committed already.
Thanks!
About compilers:
You all have to understand that I cannot possibly know all compilers and their switches to their full extent
I know! I just report a problem...
So, if someone notices errors in a compiler's macros, and knows how to fix them...
I don't know... I'm just testing compilers, i never compiled with ow before :D
-
Hello,
I submitted a bug about C::B and ResEd (a wonderful Ressource Editor)
https://developer.berlios.de/bugs/?func=detailbug&bug_id=6625&group_id=5358
I have discussed the problem with the author of ResEd.
He made a new version which correct the crash of Code::Blocks
For information, RedEd did not return exit code to 1.
It seems that Code::Blocks need that information.
Is somebody can close that bug?
Thanks and have a nice day.
-
About openwatcom... it seems that to build an app without console you need to add:
-"system nt_win"
as linker param.... I found it on wxWidgets minimal makefile, but i can't find out anything else about this param...
I think it should be setted automagically when you select the right type of project... (only on NT/2000/XP?)
-
Hello,
I have found this manual (http://www.openwatcom.org/ftp/manuals/tools.pdf) here (http://www.openwatcom.org/index.php/Manuals). At page 4 you can find "Open Watcom Compile and Link Options Summary". Anyway, the manual is a bit old :roll:.
Best wishes,
Michael
-
Another problem. Now i save my multicompiler project as template on shared/template ecc...
When i create a new project using this template, selected compiler for each target is wrong.
I'll try to explain better.
I created a project with 4 target:
-Release DMars <- Selected compiler in build option "Digital Mars" (for this target)
-Release Mingw <- Selected compiler in build option "Gnu gcc..." (for this target)
-Release VC++ <- Selected compiler in build option "VC++" (for this target)
-Release OpenWatcom <- Selected compiler in build option "Open watcom" (for this target)
That's work correctly. The compiler selected for project is digital mars. When i save and load project all works as expected. But when i save as template if i create a new project all target has "Digital Mars" as selected compiler... (why don't you add "none" to compiler lists?)
-
Hello,
I submitted a bug about C::B and ResEd (a wonderful Ressource Editor)
https://developer.berlios.de/bugs/?func=detailbug&bug_id=6625&group_id=5358
I have discussed the problem with the author of ResEd.
He made a new version which correct the crash of Code::Blocks
For information, RedEd did not return exit code to 1.
It seems that Code::Blocks need that information.
Is somebody can close that bug?
Thanks and have a nice day.
Yes. A project admin, or the submitter of a bug (you) can close a bug :D
-
Yes. A project admin, or the submitter of a bug (you) can close a bug :D
Sorry, I have searched on the web page how to close my bug but I did not find the way.
-
No problem. Thomas did it for you. :D Generally there is a drop-down box at the top of the page that you can change to closed...... SF.net does it this way, and since I have not submitted a bug yet I would assume that it (BerliOS) is the same or similar. :)
-
- When launching a tool, its details are logged (command line and working dir) for easier user troubleshooting
8)
My request added with only one day of delay....
I love this forum.
Maybe this weekend I can write a HOWTO to use NSIS under CB
Un saludo
Carlos Garces