One is not necessarily dependent on the other. I'm thinking library + executable tool or library + unit test executable. Can it be done?
On Wed, 13 Nov 2013 11:40:15 GMT, Atila Neves wrote:
One is not necessarily dependent on the other. I'm thinking library + executable tool or library + unit test executable. Can it be done?
You can use multiple configurations or separate packages, but a single "dub build" will always produce a single target binary, so it needs to be executed for each configuration separately.