You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, only a subset of Boost is provided to the guest for building. When any guest lib/util uses a feature of Boost not in the subset, or the version of Boost is upgraded, one must recreate the subset using correct tooling that sometimes has issues. This process is inconvenient.
Suggested Resolution
The original purpose for doing this was to keep the size down to a minimum, but, once all the "doc" folders have been recursively deleted, and only the required libraries to build are listed in the CMake file, the size is quite manageable.
As an additional benefit, this process reuses the host copy of Boost.
Problem Statement
Presently, only a subset of Boost is provided to the guest for building. When any guest lib/util uses a feature of Boost not in the subset, or the version of Boost is upgraded, one must recreate the subset using correct tooling that sometimes has issues. This process is inconvenient.
Suggested Resolution
The original purpose for doing this was to keep the size down to a minimum, but, once all the "doc" folders have been recursively deleted, and only the required libraries to build are listed in the CMake file, the size is quite manageable.
As an additional benefit, this process reuses the host copy of Boost.
See https://github.com/moralismercatus/crete-dev/tree/2d6a025229a61a6bb1c07da401d06c30fd67dcb4/front-end/guest/lib/boost for inspiration.
The text was updated successfully, but these errors were encountered: