Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Switching "Full compiler log" to On by default?

(1/3) > >>

oBFusCATed:
I want to make the change, in order to save lots of support round trips like:

Case1:

--- Quote ---user: my project doesn't compile
support: paste the full log
user: pastes the short log
support: I said paste the full log, to enable it do 1,2,3
user: pastes the log

--- End quote ---

Case2:

--- Quote ---user: debugging doesn't work - executable doesn't have symbols
support: read on the wiki about the needed options for proper debugging
user: I've already read it, my settings are fine
support: paste the full log for debugger and compiler
user: pastes the wrong logs
support: I said paste the full log, to enable it do 1,2,3
user: pastes the log
support: but you still have -g or -s, even -O2 is there

--- End quote ---

Anyone against this change must have extremely convincing reason to stop me doing it.
I'm going to do the change in a week or two.

stahta01:
Sounds great.

I was thinking of submitting this one line patch, for the GCC compiler, myself.

Tim S.

ollydbg:
@OBF
I agree with you, let's set the "full compiler log" by default.

killerbot:
good idea, for me it is one of the first thing I do on a new cb install ;-)

Pecan:
Oh yeah.

For all my support clients, I patch CB to make sure Full Logging is *On*, else it wastes hours getting them to turn it on, then recreating their error.

Navigation

[0] Message Index

[#] Next page