Submit a feature request.
That still will not solve the problem because gcc 3.4 outputs its messages from inside build\msw folder but C::B expects messages relative to its project-file which is 2 folders below. Since it is an external makefile how can C::B figure what's going on.
I don't get it with the GCC people. It's like they are out there to make all our lives hell. CB is not the only one with this problem. KDevelop and dev_c++ have the same problem. Some smart ass person decided to change the output of GCC and who cares about all these thousand of man work hours out there. Hell, most common practice on the gnu world is a recursive makefile system, where root makefile invokes child makefiles. Now how can an IDE figure that out if the relative folder is constantly changing?
"Look Mom, I just busted all these IDE lazy bastards to bits. I'm so full of myself" That’s grate change the only API interface with gcc, stdin/stdout, bust all users out there and "make a command line switch?" "No, your kidding, us? We are the GCC overlords we rule the world, haven't you herd?"
Oof that felt gooood. It is my opinion that GCC is the one single bad thing in OSS that is constantly wasting all our time over and over again. There must come up an alternative
Free life
Boaz Harrosh