boost
boost copied to clipboard
boostorg
Super-project for modularized Boost
If I build boost with `--layout=tagged` the flag `BOOST_AUTO_LINK_TAGGED` will not be set. e.g.: `libboost_chrono-variant-mt-x64-shared.cmake` ``` set_target_properties(Boost::chrono PROPERTIES INTERFACE_COMPILE_DEFINITIONS "BOOST_CHRONO_DYN_LINK" ) ``` Information from documentation: ``` BOOST_AUTO_LINK_NOMANGLE: Specifies that we...
Hopefully github will draw a line through each of these as/if they get closed so one can see an overview of progress. When/if they are all closed, build tooling ought...
Hi, I would like to build boost libraries without documentation files. with only header files and .so libraries. I have tried ./b2 --help or ./bootstrap --help but can't find any...
I tried "bcp disjoin_sets.hpp output" - and the command does not give any error and leave the output directory empty. Perhaps this can be fixed? (Version 1_73_0 - OS Ubuntu...
We use [bazel](https://bazel.build) to build a lot of stuff and using it makes development a lot easier. Do you think we could perhaps integrate https://github.com/nelhage/rules_boost rules into boostorg?
Boost can be downloaded from Bintray and SourceForge, but There is nothing in the Boost 1.71.0 directory in SourceForge: https://sourceforge.net/projects/boost/files/boost/1.71.0/ If Bintray reaches its monthly download limit and becomes unavailable...
When I try to checkout tag boost-1.72.0 in super-project and update all submodules I see that libs/spirit is on the boost-1.72.0.beta1 tag. Looks a bit awkward =)
The original code use `python -c "import sys; print(sys.prefix)"` which did not show actual directory for include file. The proper way is `python -c "from sysconfig import get_paths as gp;...
As the boost is great seat of libraries, people would like to use it as much as possible. But, in projects where the risk analysis is required, the users need...
We are concerned about the authority of boost as recently arised trade issues between US and the rest of the world (especially China). We are looking forward to get your...
