1

My code compiles and links just fine on PC #1 using VS 2013 Pro. It fails linking on PC #2 using VS 2013 Community Edition. The failure is three unresolved externals from Advapi32.lib -- CryptAcquireContextW, CryptReleaseContext, and CryptGenRandom.

This leads to several key questions:

  1. Why doesn't VS 2013 warn you when it can't find a library that's on the linker input line?
  2. Why is Advapi32.lib unavailable in the Community Edition?
  3. What can one do to fix this problem?

Thanks.

Bungles
  • 1,969
  • 2
  • 25
  • 54
  • It is usually required to install a Windows SDK for the targeted Windows version. When installed, It provides additional libraries. – David Ching Jun 04 '15 at 04:12
  • Thanks David. I tried that and it's definitely a good idea, but it caused a bunch of duplicate symbol and header issues that I'd probably spend a fair amount of time resolving. Luckily (this time) I didn't need to do so. – Bungles Jun 04 '15 at 18:59

0 Answers0