User forums > Using Code::Blocks

NewLine spaces in Build Log window

<< < (2/2)

oBFusCATed:

--- Quote from: Tim on August 18, 2021, 10:06:13 pm ---"Such as" is this
compiling process control "hard coded" in c++ or maybe controlled by an
intermediate script? And which script or c++ file to look at first ?

--- End quote ---
Yes, it is hard-coded in the c++. Read the code in src/plugins/compilergcc/
Search for the line "m_PageIndex = msgMan->SetLog(m_pLog);" This adds the logger.
Then you can find all places which write to the logger and see what you can do.

stahta01:
To Tim:

Can you build Code::Blocks from source either an SVN, Git, or tar file?

And, can you use an patch file to change the source code folder from above?

If yes, I might try to find where to edit the code and attach a patch file to your request on sf.net.

Tim S.

Tim:
@: oBFusCATed, Thanks. That's just what I was looking for.

My initial reaction to the code was trauma, followed by the wish to remove my account from
the forum, but after a few minutes It seems I might just need to lie down quietly for a while.

@: Tim S, The simple answer to your questions is no to all, however I looked
here:- https://sourceforge.net/p/codeblocks/code/12176/
and after a few minutes I think I understood the idea of  how the code changes were being
written, and in this particular case why the nullpointer alias was required.

In the first instance I will try and compile a copy of emIDEs' ver 2.20 source code.

Tim B

oBFusCATed:

--- Quote from: Tim on August 19, 2021, 04:35:02 pm ---My initial reaction to the code was trauma, followed by the wish to remove my account from
the forum, but after a few minutes It seems I might just need to lie down quietly for a while.

--- End quote ---
If you're an embedded dev such reaction is probably expected, but C::B in the desktop world is really small and simple project.  8) ;D

Tim:
I found the answer and should have posted this earlier.

From the main menu select "Settings"

From the drop down menu select "Compiler and debugger.."

Select the compiler you wish to modify eg "GNU GCC Compiler"

Select the far right Tab called "Other settings"
(Often hidden so resize dialog or use mini scroll bars)

select "Advanced options"  (Ignore the warning dialog)

select the "Commands" Tab

From the Drop Down called "command:" select in turn each, of the 8 or so options.

while an option is selected, in the box below called "Command line macro"
put the text cursor at the far left side of the box to the left of the first macro (usually starting with a $ (dollar sign)
and press enter. This will add a "New Line" and the existing text macro line will move down 1 line.
(This "New Line"  will be output before each of the "Full command lines".

Tim

Navigation

[0] Message Index

[*] Previous page