User forums > Nightly builds
The 16 May 2009 build (5602) is out.
Jenna:
--- 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)
--- End quote ---
You are right, chosing a compiler also dos not make sense.
Maybe it was just forgotten to disable ?
--- End quote ---
The compiler settings also specify the make executable.
--- End quote ---
Thanks !
I have absolutely overseen this :oops:
But I had a really hard week, much too much work :? :)
critic:
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?
MortenMacFly:
--- 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?
--- End quote ---
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?
critic:
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
MortenMacFly:
--- 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?
--- End quote ---
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:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version