Compiler policies

[egoslave]

Hi, I wanted to set global compiler policies (debug & release), but the dropdown list is empty and disabled. The settings are being applied fine, just cannot find a way to set different policies.

I'm using CB 8.0.2 standalone and MinGW 5.1.4 files. I remember the policies were available when I used a CB-MinGW bungle a while ago, so I'm probably just missing something.

Can you please be so kind to hint me on this?

[Jenna]

Please be more specific.

What options do you want to set where ?
Which dropdown lists are empty and disabled ?

[egoslave]

I just want to set separate policies for debug [-g] and release [-s] targets for g++.
The dropdown Policy in Settings > Compiler and debugger > Global compiler settings is empty and disabled.

It had Debug and Release profiles in the CB+MinGW combo version, but not in the CB standalone.
Please pardon if that wasn't clear from the beginning, I'm up for too long, and thought it was.

[Jenna]

I just want to set separate policies for debug [-g] and release [-s] targets for g++.
The dropdown Policy in Settings > Compiler and debugger > Global compiler settings is empty and disabled.

It had Debug and Release profiles in the CB+MinGW combo version, but not in the CB standalone.
Please pardon if that wasn't clear from the beginning, I'm up for too long, and thought it was.

I think you mixed this up with the project settings.
There you can have different build-targets for debug and release or whatever you want.
But in the dropdown-lists for the policy are disabled in global compiler settings, because they do not make sense there, and that did not change since 8.02-release.

By the way the dropdown-list only changes the order of the applied option-sets (global project options and target options) and which option-set (global or target) should be applied at all.

[egoslave]

I just thought — since the dropdown is there — you can manage global (per compiler) target policies, and switch between local & global ones.

Not that it's vital, just thought it's broken (and imagined it was working in the other release).

Thank you for your time, jens, have a good day.