Martin Kinkelin

I was pretty sure dub always defines `DC`: https://github.com/dlang/dub/blob/ead1edac76547bec597b9ea68d3b7c62b7425828/source/dub/generators/generator.d#L1005

Ouch, looks like the testsuite fails due to dub's own `dub.selections.json` in its repo root...

I understand this is a pretty big breaking change and might not land that easily, possibly having to resort to some environment variable to control it. The obvious usage is...

> Why is that? Seems to make it more complicated. Instead I would either error out or change parent dub.selections.json, possibly interactively asking for the latter. The number one reason...

Just 3 points OTOH: 1) Link dependencies will probably need to be adapted. For a dependency tree: ``` root project - A (dynamic lib) - B (static lib) ``` compiling...

For DMD, there are much bigger blockers for proper Windows DLL support, it would need something like LDC's `-fvisibility=public` and `-dllimport=all`, and then some druntime upstreamings for a druntime/Phobos DLL....

> > Another thing that came to mind is that a DLL dependency and its outputs should probably be copied to the root project's output dir, if they aren't already....

Yep, this was almost certainly introduced by #2259. > If you convert it to executable, using the older dub, does it still exhibit this behavior? I assume you meant the...

> However, as for dynamic libraries as dependencies, this is a capability that I do want. This makes picking and choosing for distributing (say frameworks) as binaries much easier. The...

I think trying to represent a framework, i.e., multiple projects, as a single dub project is a) not intended, and b) extremely exotic.