On 22 January 2014 08:33, Walter Bright <[email protected]> wrote:
> On 1/21/2014 1:38 AM, Manu wrote: > >> I suspect that VisualD is either executing the VS2010 linker, even though >> I'm >> running VS2012, or maybe it's trying to link the VS2010 libs instead of >> the 2012 >> libs? >> > > This should be easy to verify one way or the other. Check the paths in the > config files. Worst case, delete the VS2010 libs and executables (or simply > rename the directory they're in). > It's not so simple, because VisualD attempts to override the paths in the config files, it gets complicated and I have no clear view where the paths used actually come from. The reason is, it's common to have many versions of Visual Studio installed in parallel on the same machine, so while working with VisualD, the libs+linker that DMD should be using is the one that belongs to the *active VS environment*; sc.ini should be ignored, it is only configured for one particular VS upon installation, so it's wrong every time you change environment (often). Perhaps the problem here is that sc.ini isn't being ignored; it seems to be configured to point to VS2010... ...yes, seems to be the case. I amended my sc.ini file to point to the VS2012 stuff and it works much better. Only one link error: 1>libcpmtd.lib(stdthrow.obj) : error LNK2019: unresolved external symbol _CrtDbgReportW referenced in function "void __cdecl std::_Debug_message(wchar_t const *,wchar_t const *,unsigned int)" (?_Debug_message@std@@YAXPEB_W0I@Z) Strange.. I wonder where that's supposed to come from :/ So, VisualD should be ignoring sc.ini as I understand it, but it seems that it's not... Rainer?
