Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
Before you use a nightly make sure you understand how it works (http://forums.next.codeblocks.org/index.php/topic,3232.0.html).
A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx289.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc421.7z
The 14 February 2009 build is out.
- Windows :
http://prdownload.berlios.de/codeblocks/CB_20090214_rev5456_win32.7z
- Linux :
none
Resolved Fixed:
- wxSmith: Fixed event names for wxListbook and wxChoicebook (thanks goes for kencamargo for finding this)
- Fixed: File can't be opened if "As Default encoding ..." option is selected
- encoding detector: using system locale as backup-solution has returned
- HexEdit: Added support for files up to 2GB (unchanged data is read directly from the file)
- HexEdit: Resolved problems related to 32-bit resolution of scrollbar, HexEdit can now support files with size up to about 10^19
- Fixed: [Bug #15121] PlatMacOSX.cxx:324: Mismatching allocation and deallocation
- Added: Digital Mars C/C++ compiler Debug options, Warning options, Optimization options & Exception options to scripted wizard
- avoid unneded quotes in commands, otherwise using of "konsole" unde KDE gets broken, fix for issue coming in with rev 5410
- HexEdit: Implemented search support
- HexEdit: Integrated internal search with normal editor's search history
- HexEdit: (version 0.5 ready)
* Implemented backward search
* Few bugfixes - HexEdit: Fixed crashing internal test cases, caused by using wxProgressDialog from other thread
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem/Win XP problem)
Thank you! I will download and test it!
I just uploaded debian binaries (i386 and amd64) and sources for this morningly :wink: to my repo (see signature).
Build for Ubuntu i386/amd64 can be found here (http://lgp203.free.fr/spip/spip.php?article1)
Best regards, pasgui
I have build this nightly for ALT Linux. The previous nightly works fine, but this nightly crashes when trying to compile any file.
I've installed new nightly and remove ~/.codeblocks directory.
After starting codeblocks, GCC compiler is detected.
I am creating simple C++ file with content:
int main() {return 0;}
After selecting "Build" from menu, I've got "Debug report preview" and C::B crash.
Looks like C::B always crashes when compiling single file, without creating any project.
Building project works fine.
No problem here.
Is there anything helpful in the debug report ?
Quote from: jens on February 15, 2009, 02:38:25 PM
Is there anything helpful in the debug report ?
I don't know - look in the attachment.
[attachment deleted by admin]
After removing all additional plugins the problem disappeared :(
Quote from: dk on February 15, 2009, 02:52:29 PM
After removing all additional plugins the problem disappeared :(
You have the QtWorkbench-plugin installed, right ?
Did you also recompile it, or only the sources shipped with C::B ?
Yes, I've also find just now that the problem is in the qtworkbench plugin.
The latest svn snapshot of qtworkbench plugin (SVN 146, svn checkout http://qtworkbench.googlecode.com/svn/trunk/ qtworkbench-read-only) was recompiled with this nightly. And there were not problems with the previous nightly and the same version of qtworkbench plugin.
Probably, it is the problem of qtworkbench plugin, not C::B.
Bug reported to the qtworkbench developer: http://code.google.com/p/qtworkbench/issues/detail?id=20
I will remove qtworkbench from my build.
Thank you.
the bug came again :
step1: I apply the IDE's language to Chinese.
step2:
Settings -> Environment
Click the OK button.
repeat 3 time, now : click Help Menuitem, will see:
(It didn't occur when use the default language setting )
[attachment deleted by admin]
Ubuntu 7.04 to 8.10 Amd64 tar.gz archive (containing '.deb' installers builds with wx288) can be found here (http://www.esnips.com/web/CodeBlocks) or here (http://www.archive-host.com/compteur.php?url=http://codeblocks.archive-host.com/CB_20090214_802_rev5456_Ubuntu704-810_wx288_amd64tar.gz) (direct link).
There is a compilation error in src/src/prefix.cpp on Fedora Rawhide due the changes (ISO C++ compatibility) in gcc 4.4/glibc-2.9.90, see
http://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=2699&group_id=5358
for a patch
Maybe I found a strange bug in 5432 and 5456.
There is no effect when I set the syntax background color in the syntax highlighting setting panel. :?
Quote from: courage on February 19, 2009, 03:32:10 AM
Maybe I found a strange bug in 5432 and 5456.
There is no effect when I set the syntax background color in the syntax highlighting setting panel. :?
What OS ?
Can you explain exactly what colour you tried to change, that does not work.
I just tried several backgrounds for C++ on linux and there aren't any problems.
Quote from: jens on February 19, 2009, 06:49:04 AM
What OS ?
Can you explain exactly what colour you tried to change, that does not work.
I just tried several backgrounds for C++ on linux and there aren't any problems.
Sorry to not to explain clearly. Setting background color is only effect with system default color in Windows XP, and not effect when setting custom color, even if I delete the original config dir of code::blocks and restart it.
No problem here (on XP SP3 at work) C::B r5458.
I only tried it for C/C++ languages, but that works as expected here.
No problem in my windows xp. See the screenshot.
[attachment deleted by admin]
Can codeblocks editor recognize the preprocess blocks.
I open the save file in both Codeblocks and NotePad++. It seems that NotePad++ works well. See the screen shot below.
[attachment deleted by admin]
Quote from: ollydbg on February 19, 2009, 11:56:05 AM
Can codeblocks editor recognize the proprocess blocks.
I open the save file in both Codeblocks and NotePad++. It seems that NotePad++ works well. See the screen shot below.
Just check "Settings -> Editor -> Folding -> Fold preprocessor commands".
Quote from: jens on February 19, 2009, 11:59:48 AM
Quote from: ollydbg on February 19, 2009, 11:56:05 AM
Can codeblocks editor recognize the proprocess blocks.
I open the save file in both Codeblocks and NotePad++. It seems that NotePad++ works well. See the screen shot below.
Just check "Settings -> Editor -> Folding -> Fold preprocessor commands".
Thank you for your quick help. It works!
Here is the Thread Search problem. （I'm using Windows XP)
In Setting->Editor-> I use "ISO-8859-1" and select "AS fallback encoding".
I open the source code of codeblocks. When I use the Thread Search or context menu->Find occurrence of some words, it will prompt a lot of messages saying many filed can't be opened. See the screen shot below.
Is there something wrong? Thank you!
[attachment deleted by admin]
Quote from: ollydbg on February 20, 2009, 02:33:29 PM
Here is the Thread Search problem. （I'm using Windows XP)
In Setting->Editor-> I use "ISO-8859-1" and select "AS fallback encoding".
I open the source code of codeblocks. When I use the Thread Search or context menu->Find occurrence of some words, it will prompt a lot of messages saying many filed can't be opened. See the screen shot below.
Is there something wrong? Thank you!
me too, me too, me too
Hi,
If my memory is good enough, wxTextFile is used to parse files.
I have no problem if I use UTF8 for encoding.
Some details at this thread (http://forums.next.codeblocks.org/index.php/topic,9075.msg65943.html#msg65943).
I have no time for development for now. The two items on my TODO list are this one and the size optimization for small screens with yesno patch.
Dje
@DJE
I change to UTF-8. After restarting my c::b, but still 6 errors on searching.
I'm using Windows XP English.
Edit:
If I use UTF-8. Then the Tokenizer.cpp can't be shown correctly, nothing was displayed in the editor window. I have report this bug before, and someone suggest using the iso-8859-1. :D
HI, After unchecking "Allow only one running instance" in Setting -> General settings .
I found that I can still run one instance of c::b. (windows xp)
Is this a bug?
Thanks.
Quote from: ollydbg on February 21, 2009, 04:48:36 PM
HI, After unchecking "Allow only one running instance" in Setting -> General settings .
I found that I can still run one instance of c::b. (windows xp)
Is this a bug?
Thanks.
Read what the next checkbox right after "Allow only one running instance" does and you understand.
Quote from: jens on February 21, 2009, 07:05:58 PM
Quote from: ollydbg on February 21, 2009, 04:48:36 PM
HI, After unchecking "Allow only one running instance" in Setting -> General settings .
I found that I can still run one instance of c::b. (windows xp)
Is this a bug?
Thanks.
Read what the next checkbox right after "Allow only one running instance" does and you understand.
Thanks Jens.
So, The next checkbox "Use an already running instand...." should be unchecked to let another c::b running.
Feature need for the 1024*768 screen.
Hi, I think a horizontal Scroll bar is need to show the build output. Because the output string will be truncated. See the screen shot below.
Thank you!
[attachment deleted by admin]
Quote from: ollydbg on February 22, 2009, 07:17:06 AM
Feature need for the 1024*768 screen.
Hi, I think a horizontal Scroll bar is need to show the build output. Because the output string will be truncated. See the screen shot below.
Thank you!
The horizontal scrollbar should appear if you make the column larger. Maybe a quick method to expand it to the longest error message would be desirable. In Windows it can be achieved by double clicking the extender of the column, but not in Linux.
Quote from: Ceniza on February 22, 2009, 07:57:48 AM
Quote from: ollydbg on February 22, 2009, 07:17:06 AM
Feature need for the 1024*768 screen.
Hi, I think a horizontal Scroll bar is need to show the build output. Because the output string will be truncated. See the screen shot below.
Thank you!
The horizontal scrollbar should appear if you make the column larger. Maybe a quick method to expand it to the longest error message would be desirable. In Windows it can be achieved by double clicking the extender of the column, but not in Linux.
Oh, Yes, It's there, and it works.
The mistake is that I just use a windows xp theme that the extender of the column displays the same color as the title of column.
Thank you very much! :D
I add a patch to deal with opencv function prototype. Thanks
See here:
http://forums.next.codeblocks.org/index.php/topic,10162.new.html
Also, I think a opencv template is very interesting.
http://forums.next.codeblocks.org/index.php/topic,3615.0.html
But I'm not sure how to add these template to my code::blocks :(. thanks.
Quote from: Ceniza on February 22, 2009, 07:57:48 AM
Quote from: ollydbg on February 22, 2009, 07:17:06 AM
Feature need for the 1024*768 screen.
Hi, I think a horizontal Scroll bar is need to show the build output. Because the output string will be truncated. See the screen shot below.
Thank you!
The horizontal scrollbar should appear if you make the column larger. Maybe a quick method to expand it to the longest error message would be desirable. In Windows it can be achieved by double clicking the extender of the column, but not in Linux.
Is there a work around for Linux? When I get long compiler error messages I have to copy and paste them into another text editor to read them :(
What about new relize verstion. Was no one since Feb 2008.
Windows NON PCH Build Fix
Index: src/plugins/debuggergdb/debuggeroptionsprjdlg.h
===================================================================
--- src/plugins/debuggergdb/debuggeroptionsprjdlg.h (revision 5471)
+++ src/plugins/debuggergdb/debuggeroptionsprjdlg.h (working copy)
@@ -15,6 +15,7 @@
class cbProject;
class wxListBox;
class DebuggerGDB;
+class CodeBlocksEvent;
class DebuggerOptionsProjectDlg : public cbConfigurationPanel
{
Hmm, I seem to have a problem in this nightly build (5456) on Windows XP (probably there on Linux too).
I can NOT type the greater-than ">" character with a Canadian Multilingual keyboard (Ctrl+Alt+Period).
The default shortcut for "Open include file" conflicts with this. Pretty annoying to have to look around and change that.
Other than that, it's been a while since I saw a new version of Code::Blocks. It looks like it's getting much better and prettier too. Keep up the good work.
Quote from: Grom on February 25, 2009, 07:04:13 PM
What about new relize verstion. Was no one since Feb 2008.
Yeah, what's the problem with releasing a new version? Some people say that Code::Blocks development isn't active... It would be perfect if a new release appeared.
Quote from: blend on March 04, 2009, 09:21:27 AM
Some people say that Code::Blocks development isn't active...
Those are ignorants. Why support them?
Quote from: MortenMacFly on March 04, 2009, 09:55:25 AM
Quote from: blend on March 04, 2009, 09:21:27 AM
Some people say that Code::Blocks development isn't active...
Those are ignorants. Why support them?
We are not ignorants!!! I cannot convince my company to start using C::B only because there are no new versions and there are no updates. Lot of companies and people (specially today) will come with money if you will publish more versions and updates.
Perfect is the enemy of new.
Quote from: Grom on March 04, 2009, 05:23:14 PM
Quote from: MortenMacFly on March 04, 2009, 09:55:25 AM
Quote from: blend on March 04, 2009, 09:21:27 AM
Some people say that Code::Blocks development isn't active...
Those are ignorants. Why support them?
We are not ignorants!!! I cannot convince my company to start using C::B only because there are no new versions and there are no updates. Lot of companies and people (specially today) will come with money if you will publish more versions and updates.
Perfect is the enemy of new.
You
are ignorant, if you do not honour, that all the devs work in their spare time for C::B.
We all have to do our "normal" jobs to live, the most of us have families that need a little time sometimes.
If we are not fast enough for you, just start contributing instead of whining.
Hello everybody,
first of all I must say, that my opinion isn't really worth that much, as I'm not a programmer and not working in a software company at all, but well I'm an architect ( the kind with the bricks and the concrete ) and I even sell some graphics design for a living...
Now my opinion: I think, that many people are slowly changing their mind and shifting to a point of view which goes clearly away from the old hassle of mandatory needing a stable release and better even if it is released at stable intervals of time. I think this is a very old fashion way of seeing it. It dates from times when production was rather cumbersome and large scale and depended on costly infrastructure and material that had to be stock-piled. never the less many decision-makers still think this way. In reality this image is already only a make believe... Even things like consumer goods as cameras for example look to the outside like a stable release, but inside every production lot is very different from the former, thus silently evolving without users even knowing it.
For all the "print" media which nowadays comes as file through internet things like schedules or time lines are also mere cosmetic. Already there are many publications which simply release a new version whenever there is something new to publish. "Younger users" don't have any problem with this. I think everybody could give a similar case from his field of work and experience.
It hasn't anything to do with age neither. A friend of mine is doing artwork in 3D with blender and is very fond of the fast rhythm of releases, even if they are not exactly what one would call "stable releases", they are always work in progress. This friend of mine is 68 years old.
All the crying for stable releases rally is for marketing reasons only. Big companies have to print manuals, do commercials on tv and internet and print media, and they need to present steps to sell them as big improvements of the product (it has to be discussed if they really are) over older version (so, buy the new) or competitive products (buy our product, it has these new cool features). And last but not least: they made us believe, that this is how it has to be, no matter what organisation or company you are. One reason today is clearly to give a disadvantage to small business and to a certain way of producing open source software. But all this is very often only a make believe, a tale...
As long as a software, no matter which revision number it has, complies with what the user needs and expects (the user, not the marketeer), does not introduce sever bugs, does not alter the input and output format with every release, and what ever nuisance we all know and have experienced by may a product ... well, then let it have some much nightlies as it may...
I believe even many marketing dorks will slowly change their mind about this point.
Now for what regards code::blocks:
It is already a very valuable and usable product take any of the last at least twenty nightly builds. It is already used in companies and for teaching and by many private users. It is capable of growing and evolving without great many difficulties, so it will go on like that and keep evolving.
And yes: they are all volunteers, no one gets any money paid for the c::b effort. C::b is done in their private time, but they have families to care for and friends and relatives.
If somebody complains, shall he himself get busy with c::b and contribute where he/she thinks it lack features and appearance. Or only suggest, modestly.
Maybe, as my suggestion, but see above, I'm not a very able programmer to contribute much myself (some of the icons of wxSmith are one of my small adding, when I have some time maybe I can do more), but maybe the c::b devs could consider this idea:
Release the nightlies as updates to whatever version the particular user has installed. Like changing the numbering of c::b from stable 8.02 and many XXXX nightlies to code::blocks VXXXX. A button in the toolbar gets enabled whenever update is available, but it doesn't hassel the user either, he doesn't have to upgrade if he doesn't want to. The nightlies would be like some sort of a diff actually upgrading the installation to the newest nightly. Maybe it would even be the same as now, just a changed number and that the user has the feeling he is only "one click upgrading" his product instead of downloading several files and putting them in some directory and even having to erase some older file ore something "obscure" like that ...
Well, I don't know, but maybe it would quite all these strange people crying for new stables.
But as I said, just a suggestion (ready to forget), and maybe doing so would give too much credit to the complainer style people out there...
Many thanks for your great work and the forum and all your efforts,
regards
nausea
Good post. It explains everything. Those stupid updates make project to be "alive" and bring people, hence volunteers and money. If I will find little bit of time for sure I will contribute. I am 100% sure that companies will start contributing if you will make update plugin. The strategy is simple: Just put to 2 types of updates stable builds and latest features. It is more important then the development. Be sure companies will start contributing. Today nobody has money for a commercial software - it is good time to take off.
Quote from: Grom on March 04, 2009, 05:23:14 PM
Quote from: MortenMacFly on March 04, 2009, 09:55:25 AM
Quote from: blend on March 04, 2009, 09:21:27 AM
Some people say that Code::Blocks development isn't active...
Those are ignorants. Why support them?
We are not ignorants!!!
To clarify: If you don't see that we basically bring a new release witch each nightly that you are indeed ignoring our work. Period.
@nausea: BTW: Nightlys
are updates to 08/02.
Hi Morten,
I wanted to relativate mi post: I myself am very, but very, pleased by your work and absolutely agree with your form of managing the c::b project. I see the nightlies as true updates too. And: I am definitely not one of the c::b developers, nor any "real" programmer at all, I did by no means want to offend anybody or even talk in the name of the c::b developers by posting my opinion :oops: I really hope I did not offend anybody ...
And as to that second point in my post: for me it works perfectly, and so it does for many people out there, to update c::b by downloading and copying some files to my folders and having a working nightly version (well, now I'm even using the svn directly, after succeeding to mitigate some minor problems I had :wink: these I take as learning effort). Implementing something like a one-click-update-to the-last nightly was an idea of which I don't even know how much work it could be and thence if it be justified just to silence the complainer of the week ... :|
Greetings from Asturias
nausea
Quote from: nausea on March 05, 2009, 10:22:37 AM
I really hope I did not offend anybody ...
Don't you worry...
Quote from: nausea on March 05, 2009, 10:22:37 AM
Implementing something like a one-click-update-to the-last nightly [...]
Well - the script to build the installer(s) are in SVN, too. So everybody can create the installation themselves if (s)he likes to have an installer that can also update an old version. It's very easy! For example: On Windows all you need is NSIS, the NSI script file from SVN and a compiled C::B (nightly). It should work right out-of-the-box. in addition the WiKi features a lot help on that topic, too.
Bug? svn build rev 5480 (2009-03-04T10:38:26.560460Z) gcc 4.3.3 Windows/unicode
When build a DLL project, it's create D:\~temp\ps\bin\libgui.dll.a
buf in svn5477, it's D:\~temp\ps\bin\libgui.a
Quote
Be sure companies will start contributing.
They should be contributing right now since the project is already all good to go :D so companies start paying codeblocks developers for all the hardwork all this years :D
Just publish some nighties as 8.2.XXX.
We're using Code::Blocks in production.
I want to vote for just renaming the "nighties" into something like "updates" or whatever, put them in an installer and link to them from the main page via the download link. It will improve CB's popularity of which all will profit.
Quote from: geiermeier on March 10, 2009, 08:56:40 AM
We're using Code::Blocks in production.
I want to vote for just renaming the "nighties" into something like "updates" or whatever, put them in an installer and link to them from the main page via the download link. It will improve CB's popularity of which all will profit.
I agree too, many people shift to other IDEs because they think codeblocks is dead. I like codeblocks and I would like to see more people using it, because it is full-featured, multi-platform, really cool IDE ;)
Quote from: marco_silva85 on March 13, 2009, 03:42:01 PM
Quote from: geiermeier on March 10, 2009, 08:56:40 AM
We're using Code::Blocks in production.
I want to vote for just renaming the "nighties" into something like "updates" or whatever, put them in an installer and link to them from the main page via the download link. It will improve CB's popularity of which all will profit.
I agree too, many people shift to other IDEs because they think codeblocks is dead. I like codeblocks and I would like to see more people using it, because it is full-featured, multi-platform, really cool IDE ;)
The KDE people did not like the results when they released 4.0 of Alpha/Beta grade.
Tim S.
CDB not work now!
Press F7, it's stop.
svn build rev 5481 (2009-03-07T20:42:04.021208Z) gcc 4.3.3 Windows/unicode
Quote from: killerbot on February 15, 2009, 09:00:09 AM
Regressions/Confirmed/Annoying/Common bugs:
- toolbar-images-not-changing-state (is a wx problem/Win XP problem)
This should be fixed by the wxWidgets 2.8.10 release; it was fixed in SVN.
I have not had time to verify the release works and has this fix it it.
Tim S
Quote from: stahta01 on March 18, 2009, 04:13:38 PM
I have not had time to verify the release works and has this fix it it.
It has. :-)
I like the idea of having customizable shortcuts, but seriously, who came up with the default ones? I mean, Ctrl+Delete (which is used to delete a word instead of one character) actually goes to the definition of the word we're trying to delete. That added to the Ctrl+Alt+. which is used in some keyboard languages to create the less-than character. What else? Ctrl+S to create a new file? =P
*goes into options to edit all those shortcuts*
At least we can change them. ; )
EDIT: Wait a minute, I disabled the shortcuts plug-in, but that shortcut is still working? Please, don't tell me you guys hardcoded that Ctrl+Delete shortcut... That would be the lamest "feature" I've seen so far. *goes back to older Code::Blocks version*
Quote from: dje on February 20, 2009, 09:08:33 PM
Hi,
If my memory is good enough, wxTextFile is used to parse files.
I have no problem if I use UTF8 for encoding.
Some details at this thread (http://forums.next.codeblocks.org/index.php/topic,9075.msg65943.html#msg65943).
I have no time for development for now. The two items on my TODO list are this one and the size optimization for small screens with yesno patch.
Dje
Hi, Dje.
Can we solve this problem by enabling encoding detection?
see my new post here:
http://forums.next.codeblocks.org/index.php/topic,10845.msg74221.html#msg74221
Thanks.
hhhmm... i was reading the wxAuiNotebook thread in the dev forum, isn't that update in this release, didn't see it mentioned in the release notes? Or am I missing something...
On the topic of C::B updates, i think it would be cool to have a roadmap, just show what sorts of things are being worked on, and worked toward. Even just for us regulars, and to show other people that stuff is being done.
I use C::B at work too, instead of silly 'ol CW :P
Would actually be really cool to get a dev blog going about wahts being wroked on, like hows the new code completetion code going?