Different targetName based on buildType

[llucenic]

What are the limitations that a dub project cannot have specified different targetName-s (and also other parameters) based on build type (e.g. debug or release)? I have read something about forward-compatibility, however I do not understand the design decision(s). Could you please shed some light on the topic? Or what are possible workarounds for a use case where I want to package both debug and release version of an executable?
Thank you very much.

[llucenic]

Can anybody answer my question?

[s-ludwig]

I think there is no fundamental problem that would preclude this, it's mainly been a simpler implementation/specification the way it is. However, the fact that configurations and build type definitions are orthogonal to each other makes this a bit difficult to define in a nice way. The easiest approach would be to just be able to define a prefix/suffix in the build type instead of the full target name/path. Otherwise there would have to be a syntax that allows to define a different name/path for each combination of configuration and built type.

Configurations are probably the best workaround right now, so the package would be built once as dub build -b release -c app_release and once as dub build -b debug -c app_debug.

[jondegenhardt]

I'd find this useful also. I'm trying to setup PGO builds using LDC. First step is to create an instrumented build. Generating it with an alternate name seems logical.