[boost.cobalt] Cobalt not building with b2 on Windows
Hi everyone, It's my understanding that Cobalt is *not* a header-only library, yet it seems that it is not built as part of the b2 build. I'm building Boost with b2 on Windows (MSVC 2022, version 19.41) and it seems that Cobalt is not being built properly. I am using the following command line: b2 --toolset=msvc-14.3 --build-type=complete architecture=x86 address-model=64 --stagedir=stage -j 8 As far as I can tell, this works correctly for all libraries except Cobalt. While b2 does list cobalt as part of the "Component configuration" listing in the output: - atomic : building - charconv : building - chrono : building - cobalt : building [...] But I get neither binaries nor a folder cmake/boost_cobalt* with this. It also seems that the Cobalt binaries are not part of the distribution at https://sourceforge.net/projects/boost/files/boost-binaries/. Am I doing something wrong? Is Cobalt supposed to be part of the b2 build or is there another way to consume the non-header-only parts of the library? Best regards, Andreas
Andreas Weis wrote:
Hi everyone,
It's my understanding that Cobalt is *not* a header-only library, yet it seems that it is not built as part of the b2 build.
I'm building Boost with b2 on Windows (MSVC 2022, version 19.41) and it seems that Cobalt is not being built properly. I am using the following command line:
b2 --toolset=msvc-14.3 --build-type=complete architecture=x86 address-model=64 --stagedir=stage -j 8
As far as I can tell, this works correctly for all libraries except Cobalt. While b2 does list cobalt as part of the "Component configuration" listing in the output:
- atomic : building - charconv : building - chrono : building - cobalt : building [...]
But I get neither binaries nor a folder cmake/boost_cobalt* with this.
Cobalt is a C++20 library, so you'd need to add `cxxstd=20` to your command line.
On 8/24/2024 12:36 PM, Peter Dimov via Boost wrote:
you'd need to add `cxxstd=20` to your command line.
That did the trick, thank you very much! Regarding the pre-built Windows binaries: Would it make sense to build these for 20 as well? Otherwise Cobalt will not be available to people using Boost via the pre-built binaries (and I think Cobalt is currently the only library with that problem). It's not clear to me who exactly maintains those builds, but I guess the maintainers are also following this list? Best regards, Andreas
participants (3)
-
[soda-pressed] -
Andreas Weis -
Peter Dimov