Acknowledged
over 1 year ago

project.optimization directive in monkey.jungle is ignored when set in compiler options to anything but default

Normally I want my compiler options always set to optimization level "Slow" and only for projects where I'm getting issues I would like to override it to another level, but the project.optimization level is completely ignored when it's not set to default level in the compiler settings. 

If I want to fix this situation I have to:

- set compiler options optimation level to default

- in every project add a monkey.jungle option to set project.optimization = 3  

- in the problem projects set project.optimization level to another value

This is far from developer friendly.

monkey.jungle directions should always override general compiler settings 

(and yes I know you'll be throwing in the command line parameters argument, but that's a (very) poor excuse... Please implement this properly so that we can set our preferred level of optimization at a monkey c extension setting level and override where needed in the project jungle file. A similar problem exist for type level directive.)

  • WARNING: An optimization level was specified both at the command line and in a jungle file. The jungle file specification will be ignored.

    I agree that this is a bit awkward, and would be more useful if the priority would be the other way around, so we could have a default set in VSC but have the ability to override it on a per app base.