First there is the project name strangeness. When creating a "new" project codeblocks insists in making a new project in a new (or existing) directory with the same name as the project name. Somehow this don't fit in my brain and I always end up with an extra directory level when using the "project wizard". Quite annoying, but I can work around it by manually moving / renaming some files.
After some more experiments I discovered that codeblocks insists on selecting some compiler which is hidden 3 levels deep in one of the menu's. Even after you have told it to use an external makefile it insists on using the inernal settings ???This is used to find the make executable and to provide some form of code completion.
This made me loose the last shred of confidence in what codeblocks does to my source code to make a binary and I gave up and uninstalled codeblocks.C::B does nothing to your source code. It is not a compiler, but an ide. It just runs what you've told it to run...
In the project wizard there could have been a selection for makefile (& scons & cmake &...) based projects.Cmake has special generators for codeblocks and they work relatively fine. (there is a lot that needs to be improved, but they are usable)
Once you have used a makefile, attempts to compile anything without a makefile result in a number of warnings. The only way I have found of solving this is to reinstall CB. If you need both perhaps it is possible to install 2 versions of CB.then my first reacton is: WTF kind of crappy @#$%^& is this?
C::B does a whole lot more than "nothing" with source files. As an IDE it invokes a compiler with a whole lot of configurable options to make object files, and seeing on the command line output that the compiler / options are nowhere near what's in my makefile does not generate a warm fuzy feeling in my belly.
If C::B could startup in < 1s to edit a simple text file...This is annoying, but requires quite a lot of effort to improved.
Yet another confusion:makes sense.... you reply to the last post, not to the first, so you can read it fast. Not everything is confusing ;) sometimes it is also convenience...
When replying to a post, the order of all posts in this tread swap around.
QuoteYet another confusion:makes sense.... you reply to the last post, not to the first, so you can read it fast. Not everything is confusing ;) sometimes it is also convenience...
When replying to a post, the order of all posts in this tread swap around.
https://xkcd.com/1172/
I have created a ticket for one point of your critique, that i think is really point.
https://sourceforge.net/p/codeblocks/tickets/652/
With the ticket it won't get lost, and if the devs are ok to support it, i will "find" some "time" to implement it, after i have done all the other todos (many related to uC as it seems to be your main purpose)
Edit: All of the settings went away that I thought needed grayed out under Project Compiler settings; including some that I thought should not go away. So, I am confused on what to do.i really don't want to clutter this topic, and we probably should open a new topic for discussion, but i was talking about the settings:
I just realized the problem is in the global compiler settings.I don't understand what you are talking about? If a custom make file is used EVERY setting of compiler executable (linker and so) on SHOULD be ignored. Only the "make" program should work.... Can you elaborate more? Am i on the wrong path here?
I think the solution should consider have a compiler used only for makefiles.
QuoteEdit: All of the settings went away that I thought needed grayed out under Project Compiler settings; including some that I thought should not go away. So, I am confused on what to do.i really don't want to clutter this topic, and we probably should open a new topic for discussion, but i was talking about the settings:
Project->Settings->project settings->Object names generation (is not grayed out, but should be)
Project->Settings->Build targets->Output filename (should be grayed out)
ecc...
Project->Build options->Compiler settings->Compiler flags (should be grayed out)
Project->Build options->Compiler settings->Other compiler options (should be grayed out)
ecc...QuoteI just realized the problem is in the global compiler settings.I don't understand what you are talking about? If a custom make file is used EVERY setting of compiler executable (linker and so) on SHOULD be ignored. Only the "make" program should work.... Can you elaborate more? Am i on the wrong path here?
I think the solution should consider have a compiler used only for makefiles.
For a lot of (especially for Open Source) projects it is mandatory that they are buildable from the commandline (and scripts).
/bin/avr/gcc/make -f makefile build
/bin/avr/gcc/make -f makefile program