User forums > Using Code::Blocks
Possible flaw in C::B build system
mirai:
I think I found a flaw in Code::Blocks build system.
While trying to fix a recent bug about relative file paths found in cbp2make, I was playing around with a test dummy project supplied by the reporter. After reproducing the bug the next thing I tried is checking how C::B is compiling this project and I found that it puts all object files for sources in upper directories to the same "root" object directory. But what if a project is big and there are few files with different content, but with just the same file names? I added another .cpp file to the project with the same name to another directory. When at least one of such files is higher in directory tree and is referenced by a relative path, C::B fails to build the project, but, if both files are not above the project file (same level or below) then everything works perfectly.
Aside from telling that one should not create such projects intentionally I would suggest to make corrections to C::B build system. I would try fix this by replacing ".." in relative paths with something like underscores as an easiest way to put mistakenly interfering files apart in object files' directory.
What do C::B devs think about this problem?
oBFusCATed:
Post a demo project...
mirai:
Test projects: https://sourceforge.net/apps/mantisbt/cbp2make/file_download.php?file_id=2&type=bug
p.s. Sorry for broken link :)
MortenMacFly:
--- Quote from: mirai on May 10, 2012, 03:03:02 pm ---Test projects: https://sourceforge.net/apps/mantisbt/cbp2make/file_download.php?file_id=2&type=bug
--- End quote ---
There I see:
Issue 0 not found.
???
MortenMacFly:
--- Quote from: mirai on May 10, 2012, 03:32:21 pm ---Argh... I've uploaded the file to a wrong issue and then moved it to the right one... Here's the link: https://sourceforge.net/apps/mantisbt/cbp2make/file_download.php?file_id=1&type=bug
--- End quote ---
Mmmmh... that did change it to this message:
APPLICATION ERROR #1100
Issue 0 not found.
Navigation
[0] Message Index
[#] Next page
Go to full version