User forums > Using Code::Blocks
CodeBlocks sucks
bcc32x:
^ Too long, I've read all but I'm too tired to reply in details. I'm very sick now. Perhaps I would try C::B when you release a new major version, not now. I uninstalled it.
My problem is not compiler or linker because if I copy the full command like of, gcc, g++ to terminal and it run fine (miraculously). Only inside C::B it has problem, this is C::B error, don't blame the compiler.
About the compiler, your shipped compiler can't compile normally Win32++ sample source, despite it's all TDM-based but DevC++ TDM 4.9.2 works fine, your 5.1.0 fails.
I've to use latest 8.1.0 mingw64 with win32 thread and sjlj exeption handling to make the source compilable under C::B. At first it give me trouble about cc1plusplus crash then I realized since version 8 gcc default to c++11, I've to add std=c++98 and it worked fine. Again, miraculously with DevC++ the same compiler the same sample code without any tuning it compiled fine despite giving many warning because incompatible between c++98 and c++11. This made me to think, C::B hates me :(
The dll I used is written in delphi (very old before embarcadero empire now mircofocus aquirerd) then I ported to Lazarus Free Pascal. FPC and GCC use the same binutils and their objects file are compatible, event dwarf debug info fpc fully supported.
It is my purpose to code mainly in my language delphi and done the least on C/C++ side so I use a dll. My app is console based. About Win32++, I just played with it but don't use it, I prefer RAD tool of Lazarus than writing resource file myself.
oBFusCATed:
--- Quote from: bcc32x on October 04, 2018, 09:25:54 am ---You told me study the xml based build file of C::B and add new update compiler myself.
--- End quote ---
Probably I've told you this about the Borland's compiler, but here you're complaining that we're shipping TDM's MinGW and you don't need to do any editing to install any other MinGW!!! You just need to setup the toolchain paths using the provided UI.
If you want to get the Borland's compliers working in C::B you should provide patches. Or you should find someone who is interested in doing the patches for you.
This is how open source works.
oBFusCATed:
--- Quote from: bcc32x on October 04, 2018, 09:58:02 am ---^ Too long, I've read all but I'm too tired to reply in details. I'm very sick now. Perhaps I would try C::B when you release a new major version, not now. I uninstalled it.
--- End quote ---
Well done you've wasted the time of multiple people, I guess you've achieved your goal.
bcc32x:
--- Quote from: oBFusCATed on October 04, 2018, 12:16:04 pm ---
--- Quote from: bcc32x on October 04, 2018, 09:25:54 am ---You told me study the xml based build file of C::B and add new update compiler myself.
--- End quote ---
Probably I've told you this about the Borland's compiler, but here you're complaining that we're shipping TDM's MinGW and you don't need to do any editing to install any other MinGW!!! You just need to setup the toolchain paths using the provided UI.
If you want to get the Borland's compliers working in C::B you should provide patches. Or you should find someone who is interested in doing the patches for you.
This is how open source works.
--- End quote ---
If I want you to add a branch new all new all different compiler... but, I asked the developers (many, not just you) if they can update the Borland 5.5 template to support Borland 10. The work is trivial, replace bcc32.exe with bcc32c.exe and add rc.exe from Visual Studio template to replace brcc32.exe because Borland abandoned brcc32.exe. If I can do myself, well, I hate xml, I'll not ask. I ask for someone willing to help me, I don't ask you, stop telling me to "do my own patch".
I complain your default shipped TDM-GCC because it's broken and like you said, it's too easy to add another MinGW why you don't bundle the new MinGW already? Indeed it's not fast like you said, you've to provide the MinGW installation dir and remove all of the mingw32- prefix to only left gcc, g++ not mingw32-gcc or mingw32-g++. It takes time. You've to do this everytime you open a new profile of C::B or install new C::B on other mates' machines. It's a very unnecessary step and inconvenient.
bcc32x:
--- Quote from: oBFusCATed on October 04, 2018, 12:18:36 pm ---
--- Quote from: bcc32x on October 04, 2018, 09:58:02 am ---^ Too long, I've read all but I'm too tired to reply in details. I'm very sick now. Perhaps I would try C::B when you release a new major version, not now. I uninstalled it.
--- End quote ---
Well done you've wasted the time of multiple people, I guess you've achieved your goal.
--- End quote ---
What is my goal, huh? Making people to think me as bad guy or troller, spammer pleased you? I hope you pleased.
The time I post the snippet above to reproduce the problem, I already removed C::B, how could I give you build log?
It's very straight forward. Download freepascal compiler and type fpc LibTest.pas then you've the dll, I provided step by step what I do.
Don't ask me to download again, reinstall C::B again just to see the same error again.
You think only your time is precious?
It has wasted me more then 10 hours search over the net because I don't want to ask on this forum. I didn't talk with any other devs but only you. I dislike you from the first sight and I don't want to talk with you. You don't have to please me or anyone, do it your way, but I've the right to say I don't like you and I want to avoid you!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version