Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: pabristow on May 05, 2016, 03:39:29 pm

Title: Order of compile options in global project and target options
Post by: pabristow on May 05, 2016, 03:39:29 pm
I understand that the order of compiler (and linker?) options (and thus which is the final option used "For options of the same specificity, the last one takes effect.") can be controlled by appending project or prepending or using only target or project.

and that there may also be global compiler settings.

Are any global compiler settings always last on the list and will therefore always override any project or target options?

Is this also true of  "Other compiler options"?

Thanks  Paul
 

Title: Re: Order of compile options in global project and target options
Post by: oBFusCATed on May 05, 2016, 03:53:46 pm
The global compiler options are always first and it is rarely a good idea to put something there.