unresolved external symbol BCrypt*** after upgrading to boost 1.67

[boostorg]

unresolved external symbol BCrypt*** after upgrading to boost 1.67

[Lastique]

@daef You need to link with bcrypt.lib from Windows SDK.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa375377(v=vs.85).aspx

@jeking3 Maybe we could add a #pragma comment for MSVC to link the library automatically?

[pmahend1]

Adding bcrypt.lib for additional dependencies solved it

[sagarjha]

I had the same issue with vcpkg messing up boost's linking.
I fixed it by defining BOOST_UUID_FORCE_AUTO_LINK by using the compiler options.

[mathstuf]

Hmm. The CMake targets should probably export this information (rather than relying on autolinking). Cc: @pdimov

[pdimov]

I think that this has been resolved in Boost 1.78 (boostorg/boost_install#54) by no longer setting BOOST_ALL_NO_LIB in the CMake configuration files.

[daef]

Thanks @Lastique - that did the trick. If there's an update on the #pragma comment I'd happily remove the explicit reference thou :)

[jeking3]

It is supposed to autolink bcrypt.lib unless you disable that boost feature. Is that the case?

…

On Mon, May 7, 2018, 9:56 AM mnml_ ***@***.***> wrote: Thanks @Lastique <https://github.com/Lastique> - that did the trick. If there's an update on the #pragma comment I'll happily remove the explicit reference thou :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#68 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALOdbYBfpiMO4rnE3voEWzScPgmN9xUqks5twFKNgaJpZM4T07bo> .

[jeking3]

My guess is that your project uses BOOST_ALL_NO_LIB and therefore you need to add bcrypt.lib to your library list manually. If that's not the case please let me know @daef - thanks.

[daef]

The only thing I use is BOOST_ALL_DYN_LINK

[jeking3]

Then it should link automatically based on the code at https://github.com/boostorg/uuid/blob/develop/include/boost/uuid/detail/random_provider_bcrypt.ipp#L17. I'll reopen for now.

[jeking3]

We haven't seen any further reports of this, so I suspect it was environmental. I am going to close this out.

[pkoller]

I just had the same issue

[ras0219-msft]

This is caused by vcpkg disabling the boost autolink feature (because the libraries are installed with names incompatible with boost's autolink).

I'll see how we can resolve this downstream in vcpkg with microsoft/vcpkg#4481.

[Lastique]

@ras0219-msft Just wanted to point you to the documentation of macros recognized by autolink infrastructure:

https://github.com/boostorg/config/blob/develop/include/boost/config/auto_link.hpp#L15

For example, if your installed libraries simply omit mangling, you may be able to just define BOOST_AUTO_LINK_NOMANGLE instead of disabling autolinking completely.

[Be-ing]

We haven't seen any further reports of this, so I suspect it was environmental. I am going to close this out.

I am also encountering this with Boost 1.72 on Windows (not using vcpkg) using find_package with the Boost CMake config file. As far as I can tell there haven't been any changes to fix this.