Code::Blocks Forums

User forums => Nightly builds => Topic started by: killerbot on May 17, 2009, 10:23:03 am

Title: The 16 May 2009 build (5602) is out.
Post by: killerbot on May 17, 2009, 10:23:03 am
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.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 16 May 2009 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20090516_rev5602_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 16 May 2009 build (5602) is out.
Post by: BCCISProf on May 17, 2009, 12:52:10 pm
How did the files in this release get a timestamp of 10/16/09?

Although the splash screen has the correct date, under help it lists the Build as April 3, 2009?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: killerbot on May 17, 2009, 01:10:32 pm
I have no clue at all .... maybe I screwed something up ....
Will check.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pasgui on May 17, 2009, 02:11:26 pm
Build for Ubuntu i386 can be found here (http://lgp203.free.fr/spip/spip.php?article1)

The size of the codeblocks-dbg package is about 45MB instead of 12MB previously.

Best regards, pasgui
Title: Re: The 16 May 2009 build (5602) is out.
Post by: killerbot on May 17, 2009, 02:22:53 pm
the timestamps of October : apparently the clock of my virtual box is on October already. Corrected it :-)

The about box, not sure why (yet).
Title: Re: The 16 May 2009 build (5602) is out.
Post by: ollydbg on May 17, 2009, 03:47:23 pm
Quote from: BCCISProf on May 17, 2009, 12:52:10 pm
How did the files in this release get a timestamp of 10/16/09?

Although the splash screen has the correct date, under help it lists the Build as April 3, 2009?

Yes, I downloaded this package and found the wrong date either. :D

To killerbot:
Thanks for the new release.
But I feel a little disappointed because several code completion patches were still not included. :(
Though someone said that the good things were never be lost......
Maybe, they were still be testing. :D
Title: Re: The 16 May 2009 build (5602) is out.
Post by: MortenMacFly on May 18, 2009, 08:35:45 am
Quote from: ollydbg on May 17, 2009, 03:47:23 pm
Though someone said that the good things were never be lost......
Maybe, they were still be testing. :D
Why should I lie? It's is like I said. All is covered will still test internally. I even proposed a schedule how we want to apply them. Don't you worry? Next time you are in worries please just read this post of mine. ;-)
Title: Re: The 16 May 2009 build (5602) is out.
Post by: ollydbg on May 18, 2009, 09:58:15 am
Quote from: MortenMacFly on May 18, 2009, 08:35:45 am
Quote from: ollydbg on May 17, 2009, 03:47:23 pm
Though someone said that the good things were never be lost......
Maybe, they were still be testing. :D
Why should I lie? It's is like I said. All is covered will still test internally. I even proposed a schedule how we want to apply them. Don't you worry? Next time you are in worries please just read this post of mine. ;-)

Thanks Morten.
I'm getting a little worried, but after reading your post, it's gone. :D
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 18, 2009, 11:18:02 am
Quote from: pasgui on May 17, 2009, 02:11:26 pm
The size of the codeblocks-dbg package is about 45MB instead of 12MB previously.

This happened due to changes in compatibility level from deprecated 4 to 5.
dh_strip changed behaviour, sorry.

Fixed in svn r5607, I added a contrib-plugins-dbg package and added the debug-version of the codeblocks shared library, that missed in former versions.

Finally I mentioned to upload r5607 of the debian nightlies to my server (see signature).

They are build on lenny-pbuilder and are linked against wxWidgets 2.8.10 from now on.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: coolskyboy on May 19, 2009, 04:50:15 am
I could not download ......only a html file...
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 19, 2009, 06:49:37 am
Quote from: coolskyboy on May 19, 2009, 04:50:15 am
I could not download ......only a html file...
If you mean the links provided by killerbot in the starting post:
click the link you want and on the following site, you get two (really) download links.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 19, 2009, 11:12:21 am
Hello! :P

How can I request to revert access to project settings pages in C::B when using custom makefile?

As you may remember, I use in my plugin C::B project's settings to generate makefile, that is used by make.

I found that it is allowed to change project settings when using custom makefile in the eclipse IDE  8)
But eclipse is not comfortable IDE for me :? and I want use only C::B (but this limit makes use of it complex)

Will wait answer... :shock:
With best regards, critic!
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 19, 2009, 11:22:39 am
Quote from: critic on May 19, 2009, 11:12:21 am
Hello! :P

How can I request to revert access to project settings pages in C::B when using custom makefile?

As you may remember, I use in my plugin C::B project's settings to generate makefile, that is used by make.

I found that it is allowed to change project settings when using custom makefile in the eclipse IDE  8)
But eclipse is not comfortable IDE for me :? and I want use only C::B (but this limit makes use of it complex)

Will wait answer... :shock:
With best regards, critic!
It does not m ake sense in my eyes.
Project settings are normally not used for custom makefiles, because settings are done via the makefile.
If you need special settings for your plugin, you should create an own dialog for that purpose. It's not too difficult I think.

Making the project settings accessible, would make other users believe, that they can change anything via this settings, even if the settings are ignored.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 19, 2009, 11:29:29 am
OK! I'll try do that. Thanks for fast answer. :)
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pingf on May 20, 2009, 04:23:35 am
Quote from: pasgui on May 17, 2009, 02:11:26 pm
Build for Ubuntu i386 can be found here (http://lgp203.free.fr/spip/spip.php?article1)

The size of the codeblocks-dbg package is about 45MB instead of 12MB previously.

Best regards, pasgui
do you have the deb for ubuntu jaunty?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 20, 2009, 11:11:49 am
Why project settings are hidden in custom makefile mode and compiler combobox is not.
This way I can change compiler for custom makefile??? :?
But if I can select the compiler why I can't achieve compiler settings pages???

I think that these things are related! 8)
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 20, 2009, 01:24:14 pm
Quote from: critic on May 20, 2009, 11:11:49 am
Why project settings are hidden in custom makefile mode and compiler combobox is not.
This way I can change compiler for custom makefile??? :?
But if I can select the compiler why I can't achieve compiler settings pages???

I think that these things are related! 8)

You are right, chosing a compiler also dos not make sense.
Maybe it was just forgotten to disable ?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Omnipotent Geass on May 20, 2009, 07:02:27 pm
Thanks for the new release fabulous program!. :D
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pasgui on May 20, 2009, 08:06:41 pm
Quote from: pingf on May 20, 2009, 04:23:35 am
Quote from: pasgui on May 17, 2009, 02:11:26 pm
Build for Ubuntu i386 can be found here (http://lgp203.free.fr/spip/spip.php?article1)

The size of the codeblocks-dbg package is about 45MB instead of 12MB previously.

Best regards, pasgui
do you have the deb for ubuntu jaunty?

The deb are built on hardy and so available from hardy to jaunty.

Best regards, pasgui
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pingf on May 21, 2009, 04:02:39 am
Quote from: pasgui on May 20, 2009, 08:06:41 pm
Quote from: pingf on May 20, 2009, 04:23:35 am
Quote from: pasgui on May 17, 2009, 02:11:26 pm
Build for Ubuntu i386 can be found here (http://lgp203.free.fr/spip/spip.php?article1)

The size of the codeblocks-dbg package is about 45MB instead of 12MB previously.

Best regards, pasgui
do you have the deb for ubuntu jaunty?

The deb are built on hardy and so available from hardy to jaunty.

Best regards, pasgui

but when i double clicked the deb(on jaunty) ,it can't be installed,why?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: witton on May 21, 2009, 04:33:08 am
Removed chinese text.

Only english content allowed !
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Dr.Optix on May 21, 2009, 05:34:00 am
Idk why this dude posted in chinese anyway here is what is said (google translate):

Quote
   
How to download the most recent period can not be the case? Find a slightly better speed of the server you

[Removed non-english content.]
Title: Re: The 16 May 2009 build (5602) is out.
Post by: ollydbg on May 21, 2009, 05:50:59 am
Quote from: Dr.Optix on May 21, 2009, 05:34:00 am
Idk why this dude posted in chinese anyway here is what is said (google translate):

Quote
   
How to download the most recent period can not be the case? Find a slightly better speed of the server you

Google translate gives a really wrong translation. :D

He just want to get an alternative faster server to download the nightly build package, since he can't access to the current server for several days.

[Removed non-english content.]
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pasgui on May 21, 2009, 08:36:10 am
Quote from: pingf on May 21, 2009, 04:02:39 am
but when i double clicked the deb(on jaunty) ,it can't be installed,why?

Which message did you get ? Do you update your source list file (http://lgp203.free.fr/spip/spip.php?article2&lang=en (http://lgp203.free.fr/spip/spip.php?article2&lang=en)) with the distname equal to jaunty.

Regards, pasgui
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 21, 2009, 10:43:31 am
Hello  :)

I think that developers can improve functionality of IDE by modification of build system:
make available to choose build steps (not pre- or post-build steps)

For example,

The "user_build_step" can use some funcs from plugins (or simply activate some compiler plugin - it may be qt_plugin, for example)

I seen this in CodeLite IDE. It's great idea, I think. :P
Title: Re: The 16 May 2009 build (5602) is out.
Post by: pingf on May 22, 2009, 05:29:56 am
Quote from: pasgui on May 21, 2009, 08:36:10 am
Quote from: pingf on May 21, 2009, 04:02:39 am
but when i double clicked the deb(on jaunty) ,it can't be installed,why?

Which message did you get ? Do you update your source list file (http://lgp203.free.fr/spip/spip.php?article2&lang=en (http://lgp203.free.fr/spip/spip.php?article2&lang=en)) with the distname equal to jaunty.

Regards, pasgui
THX a lot,
now it works,
but when i download the wx-2.8 header in the shell mode ,it always show that the size doesn't match,
i have down it directly from the website.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: blockn102 on May 22, 2009, 09:11:50 am
At revision 5607. Ubuntu 9.04. wxWidgets 2.8 from Synaptic Package Manager.

Code
./configure --with-wxdir=/usr/include/wx-2.8 --with-wx-config=/usr/bin/wx-config --enable-contrib
make

make[3]: *** [tinywxuni.lo] Error 1

Code
In file included from ../../../src/include/sdk_common.h:120,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/pipedprocess.h:31: error: ‘wxTimerEvent’ has not been declared
../../../src/include/pipedprocess.h:32: error: ‘wxIdleEvent’ has not been declared
../../../src/include/pipedprocess.h:36: error: ‘wxTimer’ does not name a type
In file included from ../../../src/include/sdk_common.h:125,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/editormanager.h:126: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:131: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:132: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:133: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:134: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:135: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:136: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:137: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:138: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:139: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:140: error: ‘wxCommandEvent’ has not been declared
../../../src/include/editormanager.h:141: error: ‘wxUpdateUIEvent’ has not been declared
../../../src/include/editormanager.h:142: error: ‘wxTreeEvent’ has not been declared
../../../src/include/editormanager.h:143: error: ‘wxTreeEvent’ has not been declared
../../../src/include/editormanager.h:144: error: ‘wxTreeEvent’ has not been declared
../../../src/include/editormanager.h:166: error: ‘wxCommandEvent’ has not been declared
In file included from ../../../src/include/sdk_common.h:127,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/projectmanager.h:375: error: ISO C++ forbids declaration of ‘wxTreeCtrl’ with no type
../../../src/include/projectmanager.h:375: error: expected ‘;’ before ‘*’ token
../../../src/include/projectmanager.h:380: error: expected `;' before ‘wxMenu’
../../../src/include/projectmanager.h:442: error: ‘wxTreeItemId’ has not been declared
../../../src/include/projectmanager.h:443: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:444: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:445: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:446: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:447: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:448: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:449: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:450: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:451: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:452: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:453: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:454: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:455: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:456: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:457: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:458: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:459: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:460: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:461: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:462: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:463: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:464: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:465: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:466: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:467: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:468: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:469: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:470: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:471: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:472: error: ‘wxTreeItemId’ does not name a type
../../../src/include/projectmanager.h:473: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:474: error: ‘wxTreeEvent’ has not been declared
../../../src/include/projectmanager.h:475: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:476: error: ‘wxCommandEvent’ has not been declared
../../../src/include/projectmanager.h:477: error: ‘wxUpdateUIEvent’ has not been declared
../../../src/include/projectmanager.h:478: error: ‘wxIdleEvent’ has not been declared
../../../src/include/projectmanager.h:484: error: ‘wxTreeItemId’ has not been declared
../../../src/include/projectmanager.h:487: error: ISO C++ forbids declaration of ‘wxTreeCtrl’ with no type
../../../src/include/projectmanager.h:487: error: expected ‘;’ before ‘*’ token
../../../src/include/projectmanager.h:488: error: ‘wxTreeItemId’ does not name a type
../../../src/include/projectmanager.h:503: error: ‘wxTreeItemId’ does not name a type
In file included from ../../../src/include/sdk_common.h:128,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/menuitemsmanager.h:12: error: expected initializer before ‘*’ token
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ was not declared in this scope
../../../src/include/menuitemsmanager.h:12: error: typedef ‘CMPFUNC_wxArrayMenuItemsList’ is initialized (use __typeof__ instead)
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ was not declared in this scope
../../../src/include/menuitemsmanager.h:12: error: ‘pItem1’ was not declared in this scope
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ was not declared in this scope
../../../src/include/menuitemsmanager.h:12: error: ‘pItem2’ was not declared in this scope
../../../src/include/menuitemsmanager.h:12: error: ISO C++ forbids declaration of ‘_wxArrayMenuItemsList’ with no type
../../../src/include/menuitemsmanager.h:12: error: expected ‘;’ before ‘&’ token
../../../src/include/menuitemsmanager.h:12: error: expected `;' before ‘_wxArrayMenuItemsList’
../../../src/include/menuitemsmanager.h:12: error: ISO C++ forbids declaration of ‘_wxArrayMenuItemsList’ with no type
../../../src/include/menuitemsmanager.h:12: error: expected ‘;’ before ‘&’ token
../../../src/include/menuitemsmanager.h:12: error: expected `;' before ‘_wxArrayMenuItemsList’
../../../src/include/menuitemsmanager.h:12: error: ISO C++ forbids declaration of ‘_wxArrayMenuItemsList’ with no type
../../../src/include/menuitemsmanager.h:12: error: expected ‘;’ before ‘&’ token
../../../src/include/menuitemsmanager.h:12: error: expected `;' before ‘int’
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ has not been declared
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ has not been declared
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ has not been declared
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ has not been declared
../../../src/include/menuitemsmanager.h:12: error: ‘CMPFUNC_wxArrayMenuItemsList’ has not been declared
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ does not name a type
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ does not name a type
../../../src/include/menuitemsmanager.h:12: error: ‘_wxArrayMenuItemsList’ does not name a type
../../../src/include/menuitemsmanager.h:34: error: ISO C++ forbids declaration of ‘wxMenuItem’ with no type
../../../src/include/menuitemsmanager.h:34: error: ‘wxMenuItem’ declared as a ‘virtual’ field
../../../src/include/menuitemsmanager.h:34: error: expected ‘;’ before ‘*’ token
../../../src/include/menuitemsmanager.h:36: error: ISO C++ forbids declaration of ‘wxMenuItem’ with no type
../../../src/include/menuitemsmanager.h:36: error: ‘wxMenuItem’ declared as a ‘virtual’ field
../../../src/include/menuitemsmanager.h:36: error: expected ‘;’ before ‘*’ token
../../../src/include/menuitemsmanager.h:37: error: ISO C++ forbids declaration of ‘wxMenuItem’ with no type
../../../src/include/menuitemsmanager.h:37: error: ‘wxMenuItem’ declared as a ‘virtual’ field
../../../src/include/menuitemsmanager.h:37: error: expected ‘;’ before ‘*’ token
In file included from ../../../src/include/sdk_common.h:129,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/scriptingmanager.h:222: error: ‘wxCommandEvent’ has not been declared
../../../src/include/scriptingmanager.h:223: error: ‘wxCommandEvent’ has not been declared
In file included from ../../../src/include/sdk_common.h:130,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/toolsmanager.h:37: error: ‘wxCommandEvent’ has not been declared
../../../src/include/toolsmanager.h:38: error: ‘wxIdleEvent’ has not been declared
../../../src/include/toolsmanager.h:42: error: ‘wxCommandEvent’ has not been declared
In file included from ../../../src/include/sdk_common.h:139,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/xtra_res.h:21: error: invalid use of incomplete type ‘struct wxXmlResourceHandler’
../../../src/include/xtra_res.h:18: error: forward declaration of ‘struct wxXmlResourceHandler’
../../../src/include/xtra_res.h:25: error: ‘wxXmlNode’ has not been declared
../../../src/include/xtra_res.h:33: error: expected ‘,’ or ‘...’ before ‘&’ token
../../../src/include/xtra_res.h:34: error: ISO C++ forbids declaration of ‘wxArtClient’ with no type
../../../src/include/xtra_res.h:34: error: default argument missing for parameter 2 of ‘wxBitmap wxToolBarAddOnXmlHandler::GetCenteredBitmap(const wxString&, int)’
In file included from ../../../src/include/sdk_common.h:141,
                 from ../../../src/include/sdk_precomp.h:13,
                 from tinywxuni.cpp:1:
../../../src/include/infowindow.h:29: error: ‘wxDialog’ does not name a type
../../../src/include/infowindow.h:64: error: expected class-name before ‘{’ token
../../../src/include/infowindow.h:65: error: ISO C++ forbids declaration of ‘wxTimer’ with no type
../../../src/include/infowindow.h:65: error: expected ‘;’ before ‘*’ token
../../../src/include/infowindow.h:81: error: ‘wxTimerEvent’ has not been declared
../../../src/include/infowindow.h:82: error: ‘wxMouseEvent’ has not been declared
../../../src/include/infowindow.h:83: error: ‘wxMouseEvent’ has not been declared
make[3]: *** [tinywxuni.lo] Error 1
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 22, 2009, 09:19:29 am
I think that using intermediate makefile in building is more universal (but, is slower).
And this concept allows to change engine that generates makefile.
I understand that it is not easy to do this, and can be another way to decide this problem (this problem only with Qt) - this only thoughts.

Good luck!
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 22, 2009, 10:53:58 am
Quote from: critic on May 21, 2009, 10:43:31 am
Hello  :)

I think that developers can improve functionality of IDE by modification of build system:
make available to choose build steps (not pre- or post-build steps)

For example,
  • native_makefile_gen_build_step or user_build_step (to generate makefile)
  • make_build_step (for_example, to run mingw32_make -f makefile)
  • run_step (to run target executable)

The "user_build_step" can use some funcs from plugins (or simply activate some compiler plugin - it may be qt_plugin, for example)

I seen this in CodeLite IDE. It's great idea, I think. :P
Quote from: critic on May 22, 2009, 09:19:29 am
I think that using intermediate makefile in building is more universal (but, is slower).
And this concept allows to change engine that generates makefile.
I understand that it is not easy to do this, and can be another way to decide this problem (this problem only with Qt) - this only thoughts.

Good luck!

Do I understand correctly, that you want the C::B build management be changed to use makefiles instead of our own build-system ?

I think this will not happen.

Nevertheless, feel free to provide any patches.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: geiermeier on May 25, 2009, 11:14:42 am
Quote from: jens on May 20, 2009, 01:24:14 pm
Quote from: critic on May 20, 2009, 11:11:49 am
Why project settings are hidden in custom makefile mode and compiler combobox is not.
This way I can change compiler for custom makefile??? :?
But if I can select the compiler why I can't achieve compiler settings pages???

I think that these things are related! 8)

You are right, chosing a compiler also dos not make sense.
Maybe it was just forgotten to disable ?

The compiler settings also specify the make executable.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 25, 2009, 11:23:11 am
Quote from: geiermeier on May 25, 2009, 11:14:42 am
Quote from: jens on May 20, 2009, 01:24:14 pm
Quote from: critic on May 20, 2009, 11:11:49 am
Why project settings are hidden in custom makefile mode and compiler combobox is not.
This way I can change compiler for custom makefile??? :?
But if I can select the compiler why I can't achieve compiler settings pages???

I think that these things are related! 8)

You are right, chosing a compiler also dos not make sense.
Maybe it was just forgotten to disable ?

The compiler settings also specify the make executable.
Thanks !
I have absolutely overseen this  :oops:

But I had a really hard week, much too much work  :?  :)

Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 25, 2009, 01:33:12 pm
Jens, excuse me for this confusion -> :oops:
I understood my mistake.

Another question:
why developers of C::B selected wxWidgets instead of Qt. I think that latter is too much powerful?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: MortenMacFly on May 26, 2009, 08:42:36 am
Quote from: critic on May 25, 2009, 01:33:12 pm
why developers of C::B selected wxWidgets instead of Qt. I think that latter is too much powerful?
The time C::B development started (years ago!) QT was not an option. In addition: We don't see any serious limitation when using wxWidgets. Do you?
Title: Re: The 16 May 2009 build (5602) is out.
Post by: critic on May 27, 2009, 07:50:50 am
I never worked with wxWidgets before (The only my project with wxWidgets - QtHelper plugin for C::B). :(
This topic is clear.

Why don't you provide the latest snapshots of C::B's codecompletion plugin with nightly builds (for testing) or it is in the state that not allows this?

This problem is more important then Qt integration with C::B.  :shock:

As for the rest CodeBlocks is the best C++ IDE for me (it very friendly!!!) :P
Title: Re: The 16 May 2009 build (5602) is out.
Post by: MortenMacFly on May 27, 2009, 08:30:03 am
Quote from: critic on May 27, 2009, 07:50:50 am
Why don't you provide the latest snapshots of C::B's codecompletion plugin with nightly builds (for testing) or it is in the state that not allows this?
The issue for me is that the CC mods are based on the wxAUI branch which is not trunk. Maybe if killerbot offers to provide both: The wxAUI branch and the trunk version as nightly I could think of integrating it. The issue is clear: We don't want to make many changes at a time as this usually introduces errors hard to track. So the schedule is: 1.) Testing wxAUI (which everybody can do - the more do the faster we get a stable branch). IMHO it is already very stable and I am working with it on a daily basis but only under Windows. 2.) Merging wxAUI to trunk so everybody gets the benefits through nightlies 3.) Creating a CC branch to start testing the CC improvements. 4.) Merging CC improvements to branch.
You may ask: Why don't you do it? Well - the reason is simple: Although I have written this several times now I get no feedback and nobody is willing / has the time to help. So I am basically kind of stuck. :(
In fact it creates a bizarre situation for me: It's getting  more and more difficult to sync my local mods (which are not only wxAUI and CC) with trunk and the wxAUI branch. :lol:
Title: Re: The 16 May 2009 build (5602) is out.
Post by: ollydbg on May 27, 2009, 08:50:03 am
@MortenMacFly
Some simple patches like variable name replacement(my patch several days ago)can be done separately. If people(like me) want to give help, but their patches were delayed a long time, they may lose their motivation and interest to support. :D
Title: Re: The 16 May 2009 build (5602) is out.
Post by: MortenMacFly on May 27, 2009, 09:21:30 am
Quote from: ollydbg on May 27, 2009, 08:50:03 am
but their patches were delayed a long time, they may lose their motivation and interest to support. :D
I know and I feel very sorry about that. But see: We are also getting "bitten" if we apply features instead of doing a release... So whatever we do we can't make it right and people will complain. That's how it is and that's how it always will be. This is very frustrating for us, too - believe me.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: achromicia on May 27, 2009, 09:36:45 am
Any possibility that someone could host/upload the CB package to a 3rd party for me. When I attempt to download this package it sits at 6kb/s and then dies out at about 2MB downloaded and the second link doesn't seem to work at all. Perhaps it's because of my location, who knows.

Thanks in advance too.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: stahta01 on May 27, 2009, 09:43:09 pm
Quote from: achromicia on May 27, 2009, 09:36:45 am
Any possibility that someone could host/upload the CB package to a 3rd party for me. When I attempt to download this package it sits at 6kb/s and then dies out at about 2MB downloaded and the second link doesn't seem to work at all. Perhaps it's because of my location, who knows.

Thanks in advance too.

I suggest building from SVN; that is the way I did the nightly while having a dialup connection.

Tim S
PS: Code::Blocks 8.02 is on sf.net
http://sourceforge.net/projects/codeblocks/
Title: Re: The 16 May 2009 build (5602) is out.
Post by: achromicia on May 28, 2009, 09:29:07 am
Good point. Sad that I didn't think of it before - thanks mate.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Loaden on May 30, 2009, 04:40:46 am
CDB unwork!
When press F7, it's not update the state.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: PsYhLo on May 30, 2009, 11:31:26 am
Code
Making all in propgrid
make[5]: Entering directory `/home/psyhlo/devel/cb-src/src/plugins/contrib/wxSmith/propgrid'
/bin/bash ../../../../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -I./contrib/include -DWXMAKINGLIB_PROPGRID -DwxPG_USE_WXMODULE=0 -Ulinux -Uunix  -O2 -ffast-math -DCB_AUTOCONF -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT advprops.lo -MD -MP -MF .deps/advprops.Tpo -c -o advprops.lo `test -f './contrib/src/propgrid/advprops.cpp' || echo './'`./contrib/src/propgrid/advprops.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -I./contrib/include -DWXMAKINGLIB_PROPGRID -DwxPG_USE_WXMODULE=0 -Ulinux -Uunix -O2 -ffast-math -DCB_AUTOCONF -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT advprops.lo -MD -MP -MF .deps/advprops.Tpo -c ./contrib/src/propgrid/advprops.cpp  -fPIC -DPIC -o .libs/advprops.o
./contrib/src/propgrid/advprops.cpp:538: error: prototype for ‘wxFontPropertyClass::wxFontPropertyClass(const wxString&, const wxString&, const wxFont&)’ does not match any in class ‘wxFontPropertyClass’
/usr/include/wx-2.8/wx/propgrid/advprops.h:316: error: candidates are: wxFontPropertyClass::wxFontPropertyClass(const wxFontPropertyClass&)
/usr/include/wx-2.8/wx/propgrid/advprops.h:320: error:                 wxFontPropertyClass::wxFontPropertyClass(const wxString&, const wxString&, const wxFontPropertyValue&)
./contrib/src/propgrid/advprops.cpp: In member function ‘virtual bool wxFontPropertyClass::OnEvent(wxPropertyGrid*, wxWindow*, wxEvent&)’:
./contrib/src/propgrid/advprops.cpp:628: error: no matching function for call to ‘wxFontData::SetInitialFont(wxFontPropertyValue&)’
/usr/include/wx-2.8/wx/cmndata.h:106: note: candidates are: void wxFontData::SetInitialFont(const wxFont&)
make[5]: *** [advprops.lo] Error 1
make[5]: Leaving directory `/home/psyhlo/devel/cb-src/src/plugins/contrib/wxSmith/propgrid'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/psyhlo/devel/cb-src/src/plugins/contrib/wxSmith'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/psyhlo/devel/cb-src/src/plugins/contrib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/psyhlo/devel/cb-src/src/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/psyhlo/devel/cb-src/src'
make: *** [all-recursive] Error 1

ubuntu 9.04

Code
wx-config --version-full
2.8.10.1

Code
gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)

revision 5612

Title: Re: The 16 May 2009 build (5602) is out.
Post by: stahta01 on May 30, 2009, 12:07:44 pm
@PsYhLo

Code
/usr/include/wx-2.8/wx/propgrid/advprops.h:316: error: candidates are: wxFontPropertyClass::wxFontPropertyClass(const wxFontPropertyClass&)
/usr/include/wx-2.8/wx/propgrid/advprops.h:320: error:                 wxFontPropertyClass::wxFontPropertyClass(const wxString&, const wxString&, const wxFontPropertyValue&)

Try renaming the folder propgrid to propgrid-save inside folder /usr/include/wx-2.8/wx
Note: wxWidgets 2.8 does not have propgrid with it in nearly all cases.

Tim S
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 30, 2009, 12:18:03 pm
Quote from: PsYhLo on May 30, 2009, 11:31:26 am
Code
Making all in propgrid
/usr/include/wx-2.8/wx/propgrid/advprops.h:316: error: candidates are: wxFontPropertyClass::wxFontPropertyClass(const wxFontPropertyClass&)

ubuntu 9.04

Code
wx-config --version-full
2.8.10.1

As far as I know wxPropertyGrid is not part of wxWidgets < 2.9.
Where do you get your wxWidgets from ?

Is it a ubuntu-version or is it the version from apt.wxwidgets.org ?

Tim's solution should work.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: PsYhLo on May 30, 2009, 12:53:20 pm
Quote from: stahta01 on May 30, 2009, 12:07:44 pm

Try renaming the folder propgrid to propgrid-save inside folder /usr/include/wx-2.8/wx
Note: wxWidgets 2.8 does not have propgrid with it in nearly all cases.

Tim S

it works

Quote from: jens on May 30, 2009, 12:18:03 pm

As far as I know wxPropertyGrid is not part of wxWidgets < 2.9.
Where do you get your wxWidgets from ?

Is it a ubuntu-version or is it the version from apt.wxwidgets.org ?

Tim's solution should work.
from apt.wxwidgets.org
Title: Re: The 16 May 2009 build (5602) is out.
Post by: Jenna on May 30, 2009, 05:09:53 pm
Quote from: PsYhLo on May 30, 2009, 12:53:20 pm
from apt.wxwidgets.org

I just looked into the Contents file (i386 and amd64) for jaunty jackalope, and wxPropertyGrid should not be included.
Title: Re: The 16 May 2009 build (5602) is out.
Post by: PsYhLo on May 31, 2009, 10:21:35 am
but the folder is there
Code
/usr/include/wx-2.8/wx/propgrid
don't know maybe from old installation my jaunty is from upgrade from intrepid
Title: Re: The 16 May 2009 build (5602) is out.
Post by: stahta01 on June 01, 2009, 01:17:24 am
Quote from: PsYhLo on May 31, 2009, 10:21:35 am
but the folder is there
Code
/usr/include/wx-2.8/wx/propgrid
don't know maybe from old installation my jaunty is from upgrade from intrepid

I was guessing that it was wxPython related issue.

Tim S