unresolved external symbol BCrypt*** with ninja and clang-cl

[boostorg]

unresolved external symbol BCrypt*** with ninja and clang-cl

[Lastique]

Yes, see #68 (comment).

I don't know if clang-cl supports auto-linking, but if it does consider creating a pull request for https://github.com/boostorg/config/blob/develop/include/boost/config/auto_link.hpp.

[jeking3]

Some information I found:
http://releases.llvm.org/3.6.2/tools/docs/UsersManual.html

clang supports the Microsoft #pragma comment(lib, "foo.lib") feature for automatically linking against the specified library. Currently this feature only works with the Visual C++ linker.

I would also like to see an additional CI build job added that forces b2 to use clang-cl and link dynamically in order to prove this fix. This is something I could roll into all of the CMT repos eventually, since the appveyor.yml is repository-specific there is no easy way to update them all, but we could start here.

[jeking3]

I was able to reproduce this in a CI build job.

https://ci.appveyor.com/project/jeking3/uuid/builds/24529878/job/sgb58e1rq28pbhmu