Skip to content

Update Boost to 1.84.0, 1.85.0 and 1.86.0 #775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Apr 29, 2025
Merged

Conversation

tnixeu
Copy link

@tnixeu tnixeu commented Feb 20, 2025

  • I've followed this guide
    step by step carefully. Yes

Some toolchains are broken. The used toolchains should be probably be updated at some time, because most of them are quite old.

I used the commits from the PRs #758 and #759 in order to update the boost versions. In separate commits I have made the necessary change in order to support the newer libs.

Boost::process for v2 became now a library. Because of this I moved the examples to a different folder.

I am a bit unsure about boost::predef. It is listed as a lib, does not seem to be built as a lib. I have added it as a lib because otherwise it would be "built" for each boost module.

I did not update to boost 1.87.0 because it was further modularized and need more work.

@NeroBurner NeroBurner added the package:update Add a new version to an existing package label Feb 20, 2025
Copy link

@NeroBurner NeroBurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the updated packages, smaller nitpicks with copyright and the link to the old archived hunter-gate repo

@tnixeu
Copy link
Author

tnixeu commented Apr 16, 2025

I have applied your suggestions and moved them to the corresponding commits. As suggested I edited the copy right for new files but not for generated files.

@hjmallon
Copy link

Should we implement the switch to USE_CONFIG_FROM_BOOST by default here?

#723

@NeroBurner
Copy link

Should we implement the switch to USE_CONFIG_FROM_BOOST by default here?

#723

Yes we should move, and now is the perfect time with the CMake minimum version increase. No please not here. Please create a PR and I'll merge it right after this one! 🙇

@NeroBurner
Copy link

please update this PR with the updated CMake 3.10 minimum requirement #769

kryachkov and others added 7 commits April 29, 2025 11:25

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
* Add example for boost::conbalt
* Add Boost::cobalt to test matrix
* Add example for Boost::redis
* Add Boost::redis to test matrix

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
* Add example for Boost::charconv
* Add Boost::charconv to test matrix
…ocess

Renaming because the Boost::process lib in Boost became a lib for v2
* Add example for Boost::predef
  * It seems something changed about Boost::predef in 1.86.0. It is listed as a lib but not build as a lib.
* Add Boost::predef to test matrix
* Add Boost::process to test matrix
* Add example for v2 of Boost::process
  * Boost::process changed in the 1.86.0 release.
    * v1 is header only
    * v2 is a library
@tnixeu
Copy link
Author

tnixeu commented Apr 29, 2025

please update this PR with the updated CMake 3.10 minimum requirement #769

I changed all 3.5 to 3.10 in my PR.

Copy link

@NeroBurner NeroBurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package:update Add a new version to an existing package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants