Skip to content

Boost: remove USE_CONFIG_FROM_BOOST hunter option, remove old #784

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

NeroBurner
Copy link

Remove the option USE_BOOST_CONFIG. It is now essentially always enabled.

Remove all Boost versions older than 1.72, as the old versions don't supply a BoostConfig.cmake file yet.

Remove the code and templates to create a BoostConfig.cmake with Hunter.

Update the examples and remove the -useBoostConfig example folders.

Fixes: #723

@NeroBurner NeroBurner self-assigned this May 30, 2025
@NeroBurner NeroBurner added the enhancement New feature or request label May 30, 2025
@NeroBurner
Copy link
Author

@hjmallon could you review this PR please

@NeroBurner NeroBurner requested a review from hjmallon May 30, 2025 10:03
Remove the option `USE_BOOST_CONFIG`. It is now essentially always
enabled.

Remove all Boost versions older than 1.72, as the old versions don't
supply a `BoostConfig.cmake` file yet.

Remove the code and templates to create a `BoostConfig.cmake` with
Hunter.

Update the examples and remove the `-useBoostConfig` example folders.

Fixes: #723
@NeroBurner NeroBurner force-pushed the boost_always_use_config branch from b49e35a to 507e02a Compare June 2, 2025 14:48
@NeroBurner
Copy link
Author

rebased on current master to get the check_urls toolchain

@hjmallon
Copy link

hjmallon commented Jun 2, 2025

Sorry I have changed jobs and no long use Hunter. @JamesEggleton may be able to find someone to review it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should Hunter Boost move to USE_CONFIG_FROM_BOOST ON as default?
3 participants