News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

Unofficial Code::Blocks installer for Windows (svn 10408)

Started by ptDev, September 02, 2010, 05:08:35 PM

Previous topic - Next topic

ollydbg

Quote from: oBFusCATed on May 09, 2013, 07:55:04 AM
I hope he won't consider it!
The GDB_MI plugin is not intended for use by users. It is too unfinished!
Which part of the GDB_MI plugin is unfinished. Can you write some texts or guidelines like:
Something is finished, and something is unfinished, so that other user/developer can help to improve. :)
The best place would be in this thread. Thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ptDev

I made a local build, but I'll refrain from distributing the GBD-MI plugin until oBFusCATed tells us it's ready to be tested by more people.

I was making a little UUID tool for C::B today (akin to the "Create GUID" tool for Visual Studio), it'll probably be distributed with the next installer. :)

ollydbg

Quote from: ptDev on May 09, 2013, 07:47:39 PM
I made a local build, but I'll refrain from distributing the GBD-MI plugin until oBFusCATed tells us it's ready to be tested by more people.

Ok, I see.

BTW: Would you like/plan to add some more wxsmith control like wxSTC, wxMathplot in your release? It looks like they were in the C::B SVN, but not released by any distributor. (I'm currently asking the reason here: The reason of not install wxMathplot wxsmith control by default?)
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ptDev

Quote from: ollydbg on May 11, 2013, 05:02:16 PM
BTW: Would you like/plan to add some more wxsmith control like wxSTC, wxMathplot in your release? It looks like they were in the C::B SVN, but not released by any distributor. (I'm currently asking the reason here: The reason of not install wxMathplot wxsmith control by default?)

I did find it strange that after wxSTC was checked in, no additional modules were getting built in the workspace, but then I forgot about this after a while. I'll see if it was a simple oversight. That being the case, I could make a patch.

immm008

great job especially for those who dont know how to build svn version like me,haha ;D
come on!

ptDev

After several months, a new unofficial installer surfaces: Get it here while it's hot! :)

immm008

good job,especially the added offline c++ reference,thanks

Dreamy


ptDev


oBFusCATed

Quote from: Dreamy on October 09, 2013, 11:02:09 PM
Hi. Any chance for a wx 3.0-RC1 build?  ;)
Hm, C::B built with wx3.0 is only for testing purposes and for people who want to improve C::B built with wx3.0. The general users should not use it for their own sake :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Dreamy

That's not so good news, I hoped you switch to 3.0 as soon as it's final.

oBFusCATed

Why? We won't switch probably, but start to support both for some time (probably 1-2 years) then we'll switch.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Dreamy

Well wx 3.0 promises some nice improvements, such as cleaner string handling, GTK+ 3 and Cocoa ports and seems generally cleaner and bugproofed (if such thing ever existed). Maybe I'm just overexcited.

oBFusCATed

Hm, bugproof is a bold claim, in fact C::B runs way worse with wx2.9 than wx2.8.
The really interesting version (if everything goes to plan of course) will be 3.2, there we'll have the feature to move aui windows between notebooks, which is one really needed feature in C::B.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]