🔒 Locked
CodeBlocks issues
Advertisement
Original Post
Anyone here using Code::Blocks? I've noticed that sometimes if I change a file it will comple the whole god damn project, which is not necesary, and it's a big waste of time. DevCPP has some option like: "build faster but imperfect dependencies" which works most of the time. Is there something like that in Code::Blocks?
Quote:I use Code::Blocks, and it's never unnecessarily recompiled my "whole god damn project" because of a little change, except when the change was in some header file that was (recursively) included in all the files being recompiled. (and I changed something that had no impact on most of the files recompiled, thus making it unnecessary)
Original post by Raduprv
Anyone here using Code::Blocks?
I've noticed that sometimes if I change a file it will comple the whole god damn project, which is not necesary, and it's a big waste of time.
DevCPP has some option like: "build faster but imperfect dependencies" which works most of the time. Is there something like that in Code::Blocks?
Generally, it's hard to determine what files #including a header are actually impacted by a change to that header (you'd basically have to analyze the contents of the entire compilation unit), so all C and C++ build systems (at least the ones I know of) assume that if a file or anything it #includes is more recent than the corresponding object file, it needs to be recompiled. The general workaround is to put less stuff together in your headers, and only #include the stuff you really need.
If you have a better idea on how to handle this, don't hesitate to suggest it, if it's a good idea and can be implemented in Code::Blocks, you just might convince someone to do so [wink].
It happens when I modify a few C files, it will compile far more C files. I THINK it might compile the files that call a function in the file that was modified, but I am not exactly sure.
I don't know of a better way to do it, but apparently the DevCPP guys found one (which is, I think, only compile the file that changed, and if you have problems just recompile the whole god damn thing manually).
I don't know of a better way to do it, but apparently the DevCPP guys found one (which is, I think, only compile the file that changed, and if you have problems just recompile the whole god damn thing manually).
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement