User forums > Using Code::Blocks

CodeBlocks sucks

(1/9) > >>

bcc32x:
I don't want to use strong words, but it sucked hard. Your Project Build Option is a disaster, very very stupid and poor engineered (broken by design). Many many hours I spent on the Net just to see other people with the same problem as me but none solved because they gave up on you and try something other. I don't care if you ban me or shut me up by delete this thread, I'm already used with totalitarian and censorship in my country. But your developers are too arrogant,  unacceptable. You don't realize your position on the IDE market, you think you're the best!

My Problem in details, it's my last post, don't ask me provide logs or something else because it's too obvious and reproducible:

1.The project build option is broken by design. Just change the build option many times (search directory, linker setting...) and save properly for the sake of the child target (Debug and Release) not updated, causing unnecessary and nonsense errors. They're not syncing, when you change the global you expect the child to change accordingly, it does not!

And it's very hard to use a dll on this IDE. I've successfully used this dll with DevC++. Sadly, DevC++ is dead, this stupid IDE the only alternative for me lightweight enough for my old machine. Five hours, finally I given up and write this post.

The dll is a Delphi compile dll with header I wrote by hand. Imagine: LibTest.dll and LibTest.h. It's imposible to specify your linker setting to add the dll, rather I've to follow mingw.org's tutorial to use dlltool to create a .def file and produce a .a file (LibTest.a and LibTest.def). When properly add LibTest.a to linker and add appropriate search directory path (it's too stupid, all the LibTest.* already in the project root directory!, why I've to add my current working project dir to search dir? why it's not default searched?) the same stupid error a appears everytime: ld something: can't find -lLibTest.a. Ironically, when I copied the same command line of gcc and g++ to cmd.exe it's worked right!!!

2. Why you continue to build and distribute CodeBlocks with the broken and discontinued TDM-GCC? I don't understand, MingGW-64 is up and much more updated. When using your shipped GCC 5.1.0 it failed to compile my code, both a sample Win32++ project and, uhm, std::to_string is not a member of... Ironically, DevC++'s TDM-GCC 4.9.2 and latest MingW64 all compiled fine!!!

3. Is this IDE dead? The main page codeblocks.org down continuously, very rarely I can access it and read post on this forums, I did search, searched very well indeed, but can't find the solution because your IDE is indeed broken, it makes a very simple task become complicated.

4. Please remove support for ancient compiler like Borland 5 but rather support Borland 10! Drop VC2003 but support VC2015. It's the way any sane human would do. It's very simple to add because you already have the template, but you didn't. The same answer "add it yourself", I hate it, if I can do it, I will not ask. I'm the type of people if I can do it, I will contribute back.

5. Why do you offer a Windows version but keeps Linux in mind? The f*ckin SpellChecker plugin which I disabled everytime I launch a new profile of CodeBlocks expect path separator to be / but not \ so it's keep complains missing dictionary.

6. Please update your project template. It sucks. Why make thing confused? Dynamic Link Library (C++ only!!!), Shared Library (where is my dll.h but only main.c?) and Static Library (dll.h ?), too much, too confused.

7. Code suggestion way better than DevC++ but it has a very annoyed bug, it randomly stopped working after sometime. The only way to restore it is delete %AppData%CodeBlocks and re-setup every thing (compiler option, debuggers, editor...) again.

raynebc:
I switched to Code::Blocks because DevC++ became so broken it was practically unusable, we're talking constant program crashes.  C::B has some faults, but it is quite stable and I rarely have any issues with it that are more than minor annoyances.

killerbot:
as for 1, can you give steps to reproduce ?

as for 2 : we are going to step up to a new compiler, though we do not consider ourselves as compiler distributors

as for 3 : forum to me always accessible, main page I don't visit that much off course.

as for 4 : the old borland stuff is in there from the past, and hasn't been removed, since it still works, question is, is anybody still using that, probably, but in very low numbers for sure. As for the newer versions, no idea, I gave up on borland the moment c++11 came, are they up to par with that or even c++14/17, I have no idea, if they are not, and the compiler is not free, I would not spend time on it.

as for 5 : this should be fixed, wx should provide this abstraction of the path separator for us

as for 6 : please make your suggestions how you would define each template

as for 7 : this is a hard job, we need to wrap around things like clan for that, just simple parsing can not do the job anymore


Please elaborate on "Your Project Build Option is a disaster, very very stupid and poor engineered (broken by design)", because this sentence is f*** useless, it does not say what is wrong. This is generic blabla bullshit from your side. It is the same as the world sucks, ok great, but what do you want to be fixed ? Should we launch a nuclear rocket so the world explodes and the problem is solved by design. Should I hire a "gun for hire" to shoot complaining people, because when they are all dead no more complaints and we consider then there are no complaints that all is perfect? If you give specific information on what is broken, or certain flows that could be improved or are flawed, then we have something to work on.


And we do not consider ourselves to be the best, we are very aware we are a little niche player, and in certain use cases we are very well suited compared to bigger bloated systems.

oBFusCATed:
3. The site/forum problem are relatively new and local problem starting with today the problem should be fixed.

raynebc:
Forum load times are better for me at least during the last couple visits.

Navigation

[0] Message Index

[#] Next page