Alexander Grund
Alexander Grund
Suppose I have the following class: ``` struct Foo{ virtual void before(); virtual void do(); virtual void after(); }; ``` With the sequence approach I can make sure, those functions...
After trying ./configure and `bazel build -c opt //tensorflow_networking/mpi:all` I get the error ``` ERROR: Skipping '//tensorflow_networking/mpi:all': while parsing '//tensorflow_networking/mpi:all': error loading package 'tensorflow_networking/mpi': Unable to find package for @org_tensorflow//tensorflow/core:platform/default/build_config.bzl:...
### Environment and version details Github Actions "Windows 2022" image. ### Describe your use case Building Boost with `toolset=clang-win` results in a failure: > '"C:\\Program Files (x86)\\Windows Kits\\10\\bin\x64\mt.exe"' is not...
### Brief problem description I was using something like `boost.locale.std boost.locale.icu` together with `--abbreviate-paths` and noticed failures as - `./b2 --abbreviate-paths boost.locale.std=off` - `./b2 --abbreviate-paths boost.locale.icu=off` created the same folders...
### Brief problem description `:W` is supposed to "turn a cygwin path into a Win32 path". However it does not do that. ### Actual behavior summary It only does anything...
### Environment and version details * Operating System+version: Windows * Shell: PowerShell ### Brief problem description To collect coverage data on Windows it is required to (e.g.) use a wrapper...
A user did a portfile (build definition of some sort) for Haiku and noticed that although GCC 13 is being used Boost.Config unconditionally defines C++11 defect macros: https://github.com/boostorg/config/blob/boost-1.83.0/include/boost/config/platform/haiku.hpp#L19-L22 As [reported](https://github.com/boostorg/locale/issues/191#issuecomment-1694695004)...
For non-Win32 platforms BOOST_SYMBOL_IMPORT is defined to nothing which is wrong: https://gcc.gnu.org/wiki/Visibility > Symbol visibility is "default" by default but if the linker encounters just one definition with it hidden...
https://github.com/boostorg/container/commit/d5a830434eb68b9fc65cfbc99572a96e4ee0f70a replace the usage of std:: exceptions by new, custom ones which resulted in quite a few critics, e.g. on reddit: https://www.reddit.com/r/cpp/comments/mskpfp/boost_c_libraries_v1760 I have to agree and would suggest to...
Currently there are defines like `BOOST_LOCALE_ENABLE_CHAR16_T` to enable `char16_t` and similar for others. I find that a bit... difficult. We have `BOOST_NO_CHAR16_T` and similar to detect the availability automatically. So...