User forums > Using Code::Blocks
CodeBlocks sucks
bcc32x:
The problem with linking the dll I solved on my mate's computer. Create a subdir and add this dir to search dir instead of the project's root, select the dll anyway (choose all file) and it's ok. I'm sorry you good guy because it's my bad, I don't want to be troller and spammer or any kind of bad guy here. Other complains of me remains, though. Please revisit it and if you can fix it in the next major release. I'm looking for it. Now I'm happy with DevC++. I'll quit this forum a time.
oBFusCATed:
--- Quote from: bcc32x on October 04, 2018, 01:36:25 pm ---What is my goal, huh? Making people to think me as bad guy or troller, spammer pleased you? I hope you pleased.
--- End quote ---
You started with the unproductive aggression.
--- Quote from: bcc32x on October 04, 2018, 01:36:25 pm ---The time I post the snippet above to reproduce the problem, I already removed C::B, how could I give you build log?
--- End quote ---
Reinstall CodeBlocks for example?
As you've said it:
--- Quote from: bcc32x on October 04, 2018, 01:36:25 pm ---It's very straight forward. Download...
--- End quote ---
8) ::) :P ;D
BlueHazzard:
--- Quote --- if they can update the Borland 5.5 template to support Borland 10. The work is trivial,
--- End quote ---
Sadly this is not trivial for me:
1) Download the compiler
1.1) Register to download the compiler (sry, this is a no go for me, i hate registrations)
1.2) Setup the compiler and let spam your system with registry entries and other things (This is also a thing i don't like, spamming my PATH variable)
2) Download VR resource compiler
2.1) Register at microsoft (ugh...)
2.2) Download the full msvc build environment (UGHUGHGUH)
2.3) Install the full msvc build environment (TOTAL NO GO FOR ME, because i have only ~6GB of space left on my hardwarei do not want to waste it for microsoft)
3) Research the command lines
4) Research the error messages and write a regex parser for it (i am not that good ad regexp)
5) Setup codeblocks
6) Test all
I think step 1->2 you have already done (the big NO GO for me). So if you provide us with the command line the compiler needs we will tell you exactly how to set up codeblocks to accept it
If you tell us the error messages we will tell you how to set up the error parser
If all works on your machine, we will tell you how to provide a patch to upstream so we can incorporate it to codeblocks...
--- Quote ---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.
--- End quote ---
See staps 1..2 above
--- Quote ---I complain your default shipped TDM-GCC because it's broken
--- End quote ---
it was not broken at time the devs build the shipment. At this time it was the State of the art...
--- Quote --- why you don't bundle the new MinGW already?
--- End quote ---
Building, uploading a new bundle is A LOT more work then going to
Settings->Compiler->Toolchain executables->Compiler installation directory
--- Quote ---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++.
--- End quote ---
I do not understand this sentence. I do not think the mingw installation was changed in any part...
--- Quote ---It has wasted me more then 10 hours search over the net because I don't want to ask on this forum.
--- End quote ---
You could have minimized this time to 1h if you have asked... As you see i try to provide a easy Step to step quide to any of your problems and questions
--- Quote ---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.
--- End quote ---
Nice for you! Provide us with the command line and we tell you step by step how to set it up in codeblocks. Don't blame codeblocks if you don't know how to use it. We are here to provide you with help... As I said above codeblocks is complex and you need time to learn it...
--- Quote ---Other complains of me remains,
--- End quote ---
I am still not fully aware of this problems... If you are talking about the compiler problems: the next release will contain an up to date compiler (if any).
If you are talking about the non functioning path settings you have to provide a more detailed description to reproduce. The steps you described work for me as far as i understand. I think we both are not native english speaker, so the language barrier is going between us also, so please try to use as easy and simple steps as possible. The best way would be something like this:
--- Quote ---1) Create a new c++ project
2) Go to Project->Build options->Search directories...
ecc...
--- End quote ---
If you are talking about the dll wizard: If you select "c" at the beginning of the wizard, it will create a c dll like you need, if you select c++ it will generate a c++ library. I tested this at the moment, and all works as expected. If you have found something different please post it here...
Krice:
--- Quote from: bcc32x on October 04, 2018, 01:26:03 pm ---I complain your default shipped TDM-GCC because it's broken
--- End quote ---
It does work, but the default C++ support is not C++11, it's older. You can turn on C++11 in compiler settings (project-build options-compiler flags), and even 14, but I think 14 is experimental in that version of TDM. But when you turn on "have gcc follow C++11 standard" flag things like std::to_string does work. Usually what happens is that compilers or IDEs or any tools or programs aren't broken, you are. Fix yourself and trust me, you'll become a better person and a better programmer.
bcc32x:
--- Quote from: Krice on October 04, 2018, 10:45:51 pm ---
--- Quote from: bcc32x on October 04, 2018, 01:26:03 pm ---I complain your default shipped TDM-GCC because it's broken
--- End quote ---
It does work, but the default C++ support is not C++11, it's older. You can turn on C++11 in compiler settings (project-build options-compiler flags), and even 14, but I think 14 is experimental in that version of TDM. But when you turn on "have gcc follow C++11 standard" flag things like std::to_string does work. Usually what happens is that compilers or IDEs or any tools or programs aren't broken, you are. Fix yourself and trust me, you'll become a better person and a better programmer.
--- End quote ---
No it not works: 'to_string' is not a member of 'std'
You should check c++ std status on GNU site: https://www.gnu.org/software/gcc/projects/cxx-status.html
The default TDM compiler really sucks. Don't blame everything on me. Don't try to teach me what to do what not to do, I don't care.
This forums really sucks. I can't even access it (even when not logged in) from google search result. isitdownrightnow.com always gives server down for more than ~7 days or not responding blah blah. You should reverse your words. Check yourself first, check this forums, not checking me. I spent time to search before ask. I didn't intended to waste time of anyone, just because I'm afraid and I'm very dislike mr. obfuscated attitude (which I see arrogant and childish, impolite) so I tried to avoid him. You know, he's the most active here aside from bluehazzard, when you post a new pic it's very likely he will be the one answering you, which I would rather have 0 reply than his answer >:(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version