I have started running into cases where I have C++ projects which depend on D static lib's.
In the solution dependency configuration, I can configure the C++ exe project to depend on the VisualD project, but that doesn't setup for automatic linkage of the lib like C++ lib projects.
Is it possible for VisualD static lib projects to automatically link to C++ exe projects like usual C++ solutions?
It seems that when I build the C++ exe project, even though the solution see's a dependency on the VD project, it doesn't actually trigger a rebuild of the D project, I need to manually right-click and build the VD project to cause it to be built.
Comment #1 by turkeyman — 2015-09-22T05:06:01Z
**VS2013, VD 0.3.42
Comment #2 by turkeyman — 2015-10-15T23:50:52Z
I just ran into this again yesterday, and came to post the issue, but realised I already have ;)
Comment #3 by r.sagitario — 2015-10-16T06:48:58Z
Sorry, haven't checked bug reports in a while..
Building the D project as a dependency seems to work for me, but adding the library as an automatic linker input does not.
I suspect this needs the D project to be added as a "Reference" in the VC project, but it's not selectable there.
Comment #4 by turkeyman — 2015-10-16T08:30:25Z
Yeah, that's right. The build is correctly triggered as a dependency, but the lib isn't given to the linker.
Comment #5 by r.sagitario — 2017-01-24T07:51:41Z
This should work when building the library using a VC project. Implementing this for Visual D projects would mean patching VC *.target files, not sure if it is worth it...
Comment #6 by turkeyman — 2017-01-24T09:18:00Z
Probably not, we should aim for feature parity and deprecate the old projects...
Comment #7 by turkeyman — 2018-05-10T06:57:14Z
I'm closing this, because it's supported by the new project system.