@jeromecoutant i'm currently working on this Please check #328

@brondani could you please give some hints on how to fix the buildmgr-cov ?

done, please check the new tools/projmgr/test/data/TestSolution/test.target_options.cproject.yml

I have changed all options names as following OPT_DEBUG, OPT_WARNINGS, OPT_OPTIMIZE

I added a comment there as suggested

after the translation controls options addition (ie. optimize, debug, warnings), I have started supporting them into projmgr and buildmgr while doing that I had some notes which I need to share with you:

• WarningsType enum AC5-like is only valid for AC6 compiler, thus I suggest either to remove it from the standart or add a mention in the documentation saying it's for AC6 only
• OptimizeType
  • I can agree that debug means the lowed optimization possible + plus adding more debug info into the generate ELF file. thus I'm wondering if it is worth replacing it by none and we can use the debug options to add debug information

    if optimize=none
        if debug=on
            use -Og
        else
            use -O0
        endif
    endif
    

  • max is not clear for me:
    • for AC6 it should be linked to LTO: but is it -Omin (minimal size) or -Omax (best performance)
    • what about AC5 does it implies using Cross-Module Optimization ? and the same question as for AC6, is it using -Ospace -O3 or -Otime -O3
    • IAR does not have equivalent for -Omax optimization, but it does have max performance aka -Ohs --no_size_constraints
    • so I can retain the question does this max optimization targets size or performance ?
  • current enumeration values are debug, size, speed and max Comparing these values against to possible compilers optimization options, I'm wondering if it is worth adding low, medium and high values mirroring respectively -O1, -O2 and -O3
• options precedence: options could come from csolution/cproject and also from build-type/target-type
  • while implementing #328 I avoided to do silent override of options, but the options merger should be discussed and implemented.

@brondani there was a bug on tools/projmgr/schemas/common.schema.json related to WarningsType I will come back with another fix for codecov

@brondani I have added more commits to propagate the options to CMakeLists.txt now I working on supporting these options on IAR.cmake

then for the time being let's keep this as is without overriding as you suggested, let's move this discussion to #179

@brondani I'm wondering if this is the correct build type container ? I have been thinking about the case when there is options like "optimize" in the csolution and not in the cproject IMO this should be propagated here as well. even more, if optimize is specified in both csolution (optimize: size) and cproject(optimize: speed), then I think "speed" should override "size" optimization

@brondani I have added a test that I expect it to cover this code chunk.

@brondani we still have to propagate this to CMakeLists.txt and manage it in .cmake files