Actually the lack of this feature hurts visual studio workflow as visual studio having unified solution debug/release is forced to use a single path for both per project generation.
There is a workaround for visual studio using non flatten projects, but this feature may give an unified an kmake "idiomatic" way to do it.
Actually the lack of this feature hurts visual studio workflow as visual studio having unified solution debug/release is forced to use a single path for both per project generation.
There is a workaround for visual studio using non flatten projects, but this feature may give an unified an kmake "idiomatic" way to do it.