User forums > General (but related to Code::Blocks)

Promoting Code::Blocks

<< < (3/4) > >>

David Perfors:

--- Quote from: ybx ---Some people could be distracted...
--- End quote ---
That could be true, but we need to get people who could tell us where the bugs are  :lol:
So let advertise ;)

rickg22:
I agree. If we wait until 1.0 to adverstise, what happens if someone finds a bug when it's too late?

Yury Benesh (aka ybx):

--- Quote from: mandrav ---
--- Quote ---I think it's too early to advert C::B, it's pretty buggy and unstable and there's no support for separate debug/release/... configurations...
--- End quote ---

Huh?  :shock:
Are you sure you 're talking about Code::Blocks???
Buggy and unstable???
No debug/release configurations???

 :roll:  :?:

Yiannis.
--- End quote ---


ooops! Did I just not find them??? Then, it's a reason to write a readme.txt at least. SO how to add different configurations to the same project, e.g. ANSI Debug, ANSI Release, UNICODE Debug, UNICODE Release and to run BATCH BUILD to produce only UNICODE Release and ANSI Release, for instance, like in MSVC++ ?

rickg22:
Wait a second. When you say "debug/release", you mean for OTHER PROJECTS, right? :? (confused)

mandrav:

--- Quote ---ooops! Did I just not find them???
--- End quote ---

The "configurations" as they 're called in msvc, are the build targets in C::B. At least that's my understanding, not having used msvc. But since msvc projects are imported correctly, along with their "configurations", I 'm pretty sure it's the same thing.


--- Quote ---it's pretty buggy and unstable
--- End quote ---

I still don't understand this assumption. I work with C::B all day, every day and I can tell immediately if it becomes unstable at some point in development. Also, immediately, I work on "stabilizing" it again...
I 'm not trying to say that it has no bugs whatsoever, but not the kind of bugs that would crash and burn it...

Yiannis.

Navigation

[0] Message Index

[#] Next page

[*] Previous page