On 1/21/2014 7:05 PM, Manu wrote:
I don't think there's any maybe's about it, I amended sc.ini to point to the
VS2012 paths instead of the original 2010 paths, and VisualD immediately started
working fine within VS2012 (except for the CRT problem I bugged separately).
Are you suggesting I; revert sc.ini to its original VS2010 configuration, then
remove the VS2010 paths so VD can't find it, and see if it then tries the 2012
paths as a fallback?

I was only suggesting ways to verify which linker it was executing and which libraries it was linking against.

Reply via email to