Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on September 04, 2010, 10:48:10 pm

Title: The 04 September 2010 build (6570) is out.
Post by: killerbot on September 04, 2010, 10:48:10 pm
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.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_wx2810_gcc441.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc441.7z

The 04 September 2010 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20100904_rev6570_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 04 September 2010 build (6570) is out.
Post by: seb_seb0 on September 05, 2010, 03:05:08 pm
Hello,

unfortunately, the wxSmith bug is not solved (colours & font editors in wxPropertyGrid not displaying image).

I have however found a fix for the wxsMyColourPropertyClass.
The problem come from a change in name of a virtual method :
   from virtual
Code: [Select]
wxSize GetImageSize() const;   to
Code: [Select]
virtual wxSize OnMeasureImage(int item = -1)  const;
I have created a new method OnMeasureImage, and now it works !
See patch attached.

Hopefully it will always be that simple for all others regressions in wxSmith.

Regards,

Sebastien

PS: it is written in the wxWidgets doc:

Quote
virtual void wxPGProperty::OnCustomPaint  ( wxDC &  dc, 
  const wxRect &  rect, 
  wxPGPaintData &  paintdata   
 )   [virtual]

Override to paint an image in front of the property value text or drop-down list item (but only if wxPGProperty::OnMeasureImage is overridden as well).
Title: Re: The 04 September 2010 build (6570) is out.
Post by: ahui886 on September 06, 2010, 03:05:40 am
Thanks!
code:blocks is becoming better and better.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: eckard_klotz on September 09, 2010, 12:58:54 pm
Hello Everybody.

I'm a user of the cppcheck-plugin. The tool itself works. But I'm missing a posibility to configure it.

1. Since I don't have the admin-rights to install cppcheck I've copied a ready installed package from an other computer to my system. It works, but I have to search the tool every-time when i want to start it. Ii there a possibility to set the location in the environment-configuration of code::blocks?

2. If I load the code::blocks project of cppcheck and start cppcheck to testst its own sources I can click on one message,  code::blocks opens the file and jumps to the asosiated code-line. If I do the same in my project, I have to search the code-line by my self. How do I have to configure my project to activate the 'find by' click feature?

3. I want to suppress some messages. I can see that cppcheck will be started with an file named 'CppCheckInput.txt'. I think that this file can be used for configuring the tool. But where is it? Or How can I tell code::blocks to use my own one?

Best Regards,
                   Eckard Klotz.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: oBFusCATed on September 09, 2010, 02:01:05 pm

3. I want to suppress some messages. I can see that cppcheck will be started with an file named 'CppCheckInput.txt'. I think that this file can be used for configuring the tool. But where is it? Or How can I tell code::blocks to use my own one?
This file is auto generated and it is used to specify which files should be checked. I think it can't be used for error suppression...
Title: Re: The 04 September 2010 build (6570) is out.
Post by: killerbot on September 09, 2010, 02:02:08 pm
cppcheck plug-in currently is not configurable, but it would be good idea (it already crossed our mind) to configure the path for it so it can find the cppcheck executable.

That input file is generated on the fly, for providing the input files, it is not reusable.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: MortenMacFly on September 09, 2010, 02:08:22 pm
1. Since I don't have the admin-rights to install cppcheck I've copied a ready installed package from an other computer to my system. It works, but I have to search the tool every-time when i want to start it. Ii there a possibility to set the location in the environment-configuration of code::blocks?
This you can actually solve if you put the executable to your path or in the path where codeblocks.exe is located. Alternatively expand the PATH environment variable to the path where your cppcheck.exe is.

However, surely the plugin could be enhanced to offer at least some configuration options.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: eckard_klotz on September 09, 2010, 06:41:15 pm
Hello Everybody.

Thanks for the quick reaction. I learned the plug-in is still under development and there is somebody who is interested in ideas to define new features. That's great.

Has anybody an idea why the cppcheck-project is able to activate the 'find by click' feature I described (and why my project is not)?

Quote
2. If I load the code::blocks project of cppcheck and start cppcheck to testst its own sources I can click on one message,  code::blocks opens the file and jumps to the asosiated code-line. If I do the same in my project, I have to search the code-line by my self. How do I have to configure my project to activate the 'find by' click feature?

Best regards,
                   Eckard Klotz.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: MortenMacFly on September 09, 2010, 07:42:56 pm
Has anybody an idea why the cppcheck-project is able to activate the 'find by click' feature I described (and why my project is not)?
No, this works for me. Can you send a stripped sample project where it does not? Is it probably Makefile based (although this still should work)?!
Title: Re: The 04 September 2010 build (6570) is out.
Post by: emptymind on September 10, 2010, 12:47:13 pm
When i use abbreviation, new line symbols '\n' just printing in editor. It was working fine before.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: ChaiAo on September 10, 2010, 03:34:44 pm
Excuse me, but I have question.

What's the different between "build (6570)" and "build (6570) DEBUGGER BRANCH version" please?
I have downloaded "Code::Blocks 10.05" which displayed on index.
Please tell me which patch should I have?
"build (6570)" or "build (6570) DEBUGGER BRANCH version"

Thanks a lot.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: MortenMacFly on September 10, 2010, 04:22:27 pm
What's the different between "build (6570)" and "build (6570) DEBUGGER BRANCH version" please?
http://forums.codeblocks.org/index.php/topic,13170.msg88486.html#msg88486
....read the last sentences.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: ChaiAo on September 11, 2010, 03:13:59 pm
What's the different between "build (6570)" and "build (6570) DEBUGGER BRANCH version" please?
http://forums.codeblocks.org/index.php/topic,13170.msg88486.html#msg88486
....read the last sentences.

Thanks a lot.
But why doesn't Mr. killerbot put them together?
Title: Re: The 04 September 2010 build (6570) is out.
Post by: ptDev on September 11, 2010, 04:09:43 pm
What's the different between "build (6570)" and "build (6570) DEBUGGER BRANCH version" please?
http://forums.codeblocks.org/index.php/topic,13170.msg88486.html#msg88486
....read the last sentences.

Thanks a lot.
But why doesn't Mr. killerbot put them together?

The debugger branch will be merged with the trunk as soon as it becomes stable. The "Debugger Branch" releases are meant precisely for testing towards this end.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: ChaiAo on September 12, 2010, 01:13:51 am
OK. Thank you!
 :)
Title: Re: The 04 September 2010 build (6570) is out.
Post by: eckard_klotz on September 13, 2010, 06:33:59 pm
Hello Everybody.

Especialy to Morten: sory for my late reply.

Quote
Quote
Has anybody an idea why the cppcheck-project is able to activate the 'find by click' feature I described (and why my project is not)?
No, this works for me. Can you send a stripped sample project where it does not? Is it probably Makefile based (although this still should work)?!


I added a special test-project as zip-file. It contains 2 simple sources in the src-folder and several code::blocks projects in different folder-levels. If I activate the projects in the sub-folder "CppCheck\CppCheck\prj" or in the sub-folder "CppCheck\CppCheck\prj\CppCheck"  I'm not able to find the location associated to the cppcheck-message by click. The other 2 projects are able to find the location by click. Could it be path-problem?

Best Regards,
                    Eckard Klotz.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: killerbot on September 21, 2010, 06:57:24 pm
I have downloaded, I will try to have a look at it this week.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: killerbot on September 21, 2010, 09:24:24 pm
I checked it.
It is not a CB issue, it seems it is an issue in cppcheck it self.

This is the result of calling cppcheck manually on the command line :
Code: [Select]
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck/CppCheck/prj> cppcheck --verbose --all --style ../../src/test.cpp
Checking ../../src/test.cpp...
[src/test.cpp:7]: (style) Unused variable: ReturnValue
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck/CppCheck/prj>
As you can see : cppcheck is giving back an incorrect path  : [src/test.cpp:7]

Similar when we go even one level deeper :
Code: [Select]
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck/CppCheck/prj/CppCheck> cppcheck --verbose --all --style ../../../src/test.cpp
Checking ../../../src/test.cpp...
[../src/test.cpp:7]: (style) Unused variable: ReturnValue
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck/CppCheck/prj/CppCheck>

Basically it boils down to : when the directory where cppcheck is invoked is at a deeper level then the sources to check, things start to go wrong.
The first 2 cases in your example zip file were 1 level higher, or at the same level

Code: [Select]
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck> cppcheck --verbose --all --style ./src/test.cpp
Checking ./src/test.cpp...
[./src/test.cpp:7]: (style) Unused variable: ReturnValue

Code: [Select]
[email protected]:~/Projects/TryOuts/Test_CppCheck/CppCheck/CppCheck> cppcheck --verbose --all --style ../src/test.cpp
Checking ../src/test.cpp...
[../src/test.cpp:7]: (style) Unused variable: ReturnValue


created a bug report for it with cppcheck : https://sourceforge.net/apps/trac/cppcheck/ticket/2059
Title: Re: The 04 September 2010 build (6570) is out.
Post by: eckard_klotz on September 22, 2010, 12:56:29 pm
Hello Killerbot.

Thanks for your fast checking.

Best Regards,
                   Eckard Klotz.

Title: Re: The 04 September 2010 build (6570) is out.
Post by: killerbot on September 23, 2010, 09:05:43 am
and more good news, the guys of cppcheck fixed the bug. So it will be available in cppcheck 1.45

Quote
Version 1.45 is planned to be released on October 10th

So we just have to wait a few more weeks, of you can get their sources out of git, and compile it yourself ...
Title: Re: The 04 September 2010 build (6570) is out.
Post by: MortenMacFly on September 23, 2010, 05:51:27 pm
Thanks for your fast checking.
Seems I missed this post (and the rmeinder :-(). I just saw killerbot did it. Sorry for that.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: eckard_klotz on September 23, 2010, 07:02:06 pm
Hello Killerbot and hello Morten.

I think you and the other developer make a great job and currently you have a lot do do with codecompletion an debuger. Thus it's OK if my problem has lower priority.

By the way, it is right that I'm not able to load up a file as my example while submitting a bug-report.

Best Regards,
                     Eckard.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: MortenMacFly on September 23, 2010, 09:46:21 pm
By the way, it is right that I'm not able to load up a file as my example while submitting a bug-report.
Yes, but you can point to relevant information /archives in the forums in the bug report. That's very convenient, usually.
Title: Re: The 04 September 2010 build (6570) is out.
Post by: killerbot on October 11, 2010, 08:44:17 am
and more good news, the guys of cppcheck fixed the bug. So it will be available in cppcheck 1.45

Quote
Version 1.45 is planned to be released on October 10th

So we just have to wait a few more weeks, of you can get their sources out of git, and compile it yourself ...

Cppcheck 1.45 is out, and I have tested our test cases, and all work fine now. Thumbs up for the cppcheck guys :-)