Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: pozzugno on December 17, 2010, 12:46:08 pm

Title: Showing relative paths in "Build messages"
Post by: pozzugno on December 17, 2010, 12:46:08 pm
My compiler outputs warnings and errors with the full/absolute pathname for each file.
Of course this pathname is shown in "Build messages" frame of C::B.

How can I convert the absolute to the relative pathname against the main project
directory?
Title: Re: Showing relative paths in "Build messages"
Post by: oBFusCATed on December 17, 2010, 01:43:11 pm
What do you need this feature, for?

Probably to fix this you'll need to modify the code.
Title: Re: Showing relative paths in "Build messages"
Post by: mirai on December 17, 2010, 03:54:26 pm
IMO, full paths are probably uncomfortable because they can be much longer than relative paths and may simply not fit in a window while they do contain redundant information that only brings confusion instead of help.
Title: Re: Showing relative paths in "Build messages"
Post by: Jenna on December 17, 2010, 04:00:07 pm
You can try to uncheck "Settings -> Compiler and debugger... -> Global compiler settings -> [the compiler you use] -> Other settings -> Advanced options... -> Others -> Use full Paths for source files (GDB workaround):".

But it can break debugging in some cases.
Title: Re: Showing relative paths in "Build messages"
Post by: pozzugno on December 17, 2010, 04:53:25 pm
IMO, full paths are probably uncomfortable because they can be much longer than relative paths and may simply not fit in a window while they do contain redundant information that only brings confusion instead of help.

Yes, that is my reason too :-)
Title: Re: Showing relative paths in "Build messages"
Post by: pozzugno on December 17, 2010, 04:54:18 pm
You can try to uncheck "Settings -> Compiler and debugger... -> Global compiler settings -> [the compiler you use] -> Other settings -> Advanced options... -> Others -> Use full Paths for source files (GDB workaround):".

Great, that works... :-)

But it can break debugging in some cases.

Oh, I'm not interested in debugging.