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.
library LibTest;
{$mode objfpc}{$H+}
uses
SysUtils, ctypes;
function DoubleIt(InParam: cint32): cint32; cdecl;
begin
Result:= InParam * 2;
end;
exports
DoubleIt;
end.// too lazy to write header guard so let it is
#include <stdint.h>
int32_t __cdecl DoubleIt(int32_t InParam);
// copy from DevC++ project (successfully build and run) so expect the same for C::B but it isn't
#include <stdio.h>
#include <stdlib.h>
#include "LibTest.h"
/* run this program using the console pauser or add your own getch, system("pause") or input loop */
int main(int argc, char *argv[]) {
printf("Double Of %d : %d\n", 3, DoubleIt(3));
system("PAUSE");
return 0;
}2. thanks, I like you more than mr. obfuscated who told me "do it yourself".What have I told you?
3. I'm on South East Asia, your whole domain codeblocks.org and it child reported by issitedownrightnow almost constantly down, many time down for more than 7 days, I can only access it a very short time a day like 1 hours but later revisit it down again, make me thing, is this site DDoS-ed?You have to contact your service provider to see why it is blocking codeblock.org. Just keep in mind that the site had problems for the last one-two weeks. If the complains are from this period, then it was a global problem. It was an exception, not the rule. The problem should be fixed and everything should be back to normal.
2. thanks, I like you more than mr. obfuscated who told me "do it yourself".What have I told you?3. I'm on South East Asia, your whole domain codeblocks.org and it child reported by issitedownrightnow almost constantly down, many time down for more than 7 days, I can only access it a very short time a day like 1 hours but later revisit it down again, make me thing, is this site DDoS-ed?You have to contact your service provider to see why it is blocking codeblock.org. Just keep in mind that the site had problems for the last one-two weeks. If the complains are from this period, then it was a global problem. It was an exception, not the rule. The problem should be fixed and everything should be back to normal.
All the file are in project root folder: C:\LibTest (LibTest is the C::B project).Then add a "." in Project->Build options->Select your project on the left->Search paths->Compiler
(WTF? Why I've to add it to search dir, isn't it obviously must be searched by default?)That is your opinion. Mine is an other. For example in java it takes automatically some predefined files from some folder and i needed like 100h to find out why it always took the wrong file. It simply had an build in automatic search algorithm. This annoyed me like hell. Better the user has to tell where to search. So he always knows what is going on.
Can't add LibTest.dll from Linker setting but choose All file to add it anyway, failed: can't find LibTest.dll!What is the exact error? There you have to differentiate:
dlltool -z LibTest.def --export-all-symbol LibTest.dllAbout this, you have to know that this is a mingw thing. Nothing to do with codeblocks. Also it is a language c/c++ thing. You can not mix different compiler and languages and think this is easy to handle... Every language uses different name mangling, different file formats for libraries, different call conventions ecc...
dlltool -d LibTest.def -l LibTest.a
Follow someone on this forum to add this .def file to linker, either by choose All file like as the dll or other linker option (also on this forum, not bookmarked so don't have the link and don't care to search again because too tired)
Failed: can't find LibTest.def!
Add the LibTest.a file to linker (accepted), expect anything to be right but again: failed, can't find LibTest.a!
I even try to add all the file to project itself but still not find LibTest!!!The IDE does not complain, the compiler complains...
WTF! Does this IDE blind or too stupid to see the file I wonder?
I like DevC++ makefile based than your xml based, in my opion xml is evil, I'm plain text fan.then go the makefile route:
make -f Makefile TARGETNAMEMy sentence is not useless, there really problem of out-of-sync between your global project build option and it child Debug and Release, it's very easy to reproduce, you change search directory or liker setting of the global, the first time it sync-ed to the child, the second or third or *th time it doesn't, you have to go the each child and change again, very time consuming: like, you remove a dir from search dir to point to new dir, the child still keep old dir so compiler started errors.I use codeblocks on a daily basis and never encountered this. Codeblocks uses basically this hierarchy to set paths and compiler options:
Global compiler settings->Project settings->Target settingsAppend target options to project optionsis the default, but there are many more policies..
´wx-config --libs´You have to restart codeblocks if something changes...
You told me study the xml based build file of C::B and add new update compiler myself.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.
^ 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.Well done you've wasted the time of multiple people, I guess you've achieved your goal.
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".You told me study the xml based build file of C::B and add new update compiler myself.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.
^ 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.Well done you've wasted the time of multiple people, I guess you've achieved your goal.
What is my goal, huh? Making people to think me as bad guy or troller, spammer pleased you? I hope you pleased.You started with the unproductive aggression.
The time I post the snippet above to reproduce the problem, I already removed C::B, how could I give you build log?Reinstall CodeBlocks for example?
It's very straight forward. Download...
if they can update the Borland 5.5 template to support Borland 10. The work is trivial,Sadly this is not trivial for me:
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.See staps 1..2 above
I complain your default shipped TDM-GCC because it's brokenit was not broken at time the devs build the shipment. At this time it was the State of the art...
why you don't bundle the new MinGW already?Building, uploading a new bundle is A LOT more work then going to
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++.I do not understand this sentence. I do not think the mingw installation was changed in any part...
It has wasted me more then 10 hours search over the net because I don't want to ask on this forum.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
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.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...
Other complains of me remains,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).
1) Create a new c++ projectIf 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...
2) Go to Project->Build options->Search directories...
ecc...
I complain your default shipped TDM-GCC because it's broken
I complain your default shipped TDM-GCC because it's broken
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.
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.
I complain your default shipped TDM-GCC because it's broken
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.
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 >:(
isitdownrightnow claims this forum is down even now as I am posting. Clearly the forum is up and running, but potentially some ISPs are interfering with its access.
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.
That's strange, because std::to_string works if you turn on c++11 or newer flag. There might be some differences or bugs in other platforms (or 32 vs. 64 bit) though. But if that's the case then use another compiler for the features you need. You can shout at the compiler or IDE all you want, it doesn't help compiling the program. There is a kind of a problem when you use new C++ features, because lack of compiler support in older versions. You simply have to think about it when choosing the IDE/compiler for your project before you do anything else.
I complain your default shipped TDM-GCC because it's broken
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.
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 >:(
You need to enable -std=c++11 option to use std::to_string(). It is not enabled by default but one can easily enable it from Project > Build options > Compiler settings Bundled compiler may not be state of the art but not absolutely broken either.
There were issues with forum and website access. I also faced difficulty accessing forum.
Regarding your other issues - I'm sure some of them, if not all, can be solved as long as you explain them correctly. You need to help us to help you.
I read this thread because I always find it amusing (sort of...) when people complain aggressively about free software. (The horrible usage "sucks" suggests that the OP is a young person, which is consistent with the entitled tone of the post.)The only problem is CodeBlocks is dead, I mean there are no releas since very long, but about the rest I agree.
CodeBlocks is not perfect, but it is still bloody terrific, and I'm very grateful to the developers.
Dead would mean there is no development. There was a nightly build from earlier this month.Already had that discusion, nightly builds are really something only for a smal comunity with advanced programming skills. So let say so for the small comunity, mentioned befor, CodeBlocks is still alive, but but for the rest it´s dead.
nightly builds are really something only for a smal comunity with advanced programming skills
You forgot, that nightly builds contain no compiler, so you need to do all that anoing stuff, to make CodeBlocks worck with the compiler you have and that compiler must be installed to.Quotenightly builds are really something only for a smal comunity with advanced programming skills
If merging three zips in a folder needs "advanced programming skills" something is really dead, probably a brain.
You forgot, that nightly builds contain no compiler, so you need to do all that anoing stuff, to make CodeBlocks worck with the compiler you have and that compiler must be installed to.Quotenightly builds are really something only for a smal comunity with advanced programming skills
If merging three zips in a folder needs "advanced programming skills" something is really dead, probably a brain.
If merging three zips in a folder needs "advanced programming skills" something is really dead, probably a brain.That about sums up my thoughts on it. It's not like you have to build it from source code, which actually is more complicated. My MinGW installation can't even do it, it crashes during the build process.
Wait, my english is really really bad, but doesn´t the word nightly build mean, that I have to build it?If merging three zips in a folder needs "advanced programming skills" something is really dead, probably a brain.That about sums up my thoughts on it. It's not like you have to build it from source code, which actually is more complicated. My MinGW installation can't even do it, it crashes during the build process.
It's not hard to have a real compiler installation that is in your PATH environment variable. If you can't manage that, you need to grapple more with intermediate computer usage before worrying about software development.
Wait, my english is really really bad, but doesn´t the word nightly build mean, that I have to build it?No, YOU do not have to build it (at least for major OS)... Nightly means they are build "during the night". There are provided "official" builds for windows, and some user provide "unofficial builds" for debian and mac... So you can simply download them (for major OS)...
Like I said my english is very bad, so misunderstandings can be expected.QuoteWait, my english is really really bad, but doesn´t the word nightly build mean, that I have to build it?No, YOU do not have to build it (at least for major OS)... Nightly means they are build "during the night". There are provided "official" builds for windows, and some user provide "unofficial builds" for debian and mac... So you can simply download them (for major OS)...
[Edit:] You could at least try to read the nightly forum. An i NEVER have seen any "nightly build" that you have to build yourself...