/*
todo
need to choose a way how to interpret config specification for config and build-steps
and for make and IDE generators.
What will be built if build-step specification takes precedence:
For IDE generator no specifying the config results in Debug build (tested with vs and xcode)
commands | make-generator | ide-generator
c then b | noconfig | debug
cd then b | noconfig | debug
cr then b | noconfig | debug
What will be built if config-step specification is remembered:
commands | make-generator | ide-generator
c then b | noconfig | debug
cd then b | debug | debug
cr then b | release | debug*
*: The last option is currently not possible because the configuration is not remembered with
IDE-generator
Also need to decide what to do if someone uploads a NoConfig package which is then downloaded for an
ide generator build
*/
/* todo need to choose a way how to interpret config specification for config and build-steps and for make and IDE generators.
What will be built if build-step specification takes precedence: For IDE generator no specifying the config results in Debug build (tested with vs and xcode)
commands | make-generator | ide-generator
c then b | noconfig | debug cd then b | noconfig | debug cr then b | noconfig | debug
What will be built if config-step specification is remembered:
commands | make-generator | ide-generator
c then b | noconfig | debug cd then b | debug | debug cr then b | release | debug*
*: The last option is currently not possible because the configuration is not remembered with IDE-generator
Also need to decide what to do if someone uploads a NoConfig package which is then downloaded for an ide generator build */