-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[boost-uninstall] Add port to easily uninstall all boost components #12851
[boost-uninstall] Add port to easily uninstall all boost components #12851
Conversation
The correct way to do this is to make all ports depend on boost-build because that is the only way to generate the config.cmake in the future |
@Neumann-A It is not obvious to use boost-build, and the remaining two ports are also providing other configuration files. |
What about uses of boost that only need the headers and therefore don't need to build boost.build? |
@BillyONeal also applies to header only. Think of boost.build as boost.cmake. boost.build just defines install rules and one of the rules is to install configs. Since boost has a header target in cmake it requires to generate a config for it. |
Co-authored-by: Daniel Marshall <[email protected]>
We may need to add a new keyword |
This is fine because it doesn't cause 'damage' but it would be nice to solve this more generally, such as one of the following solutions:
@JackBoosY Do you want to try one of those or just merge this for now? |
@BillyONeal Just merge this PR temporary would be okay. |
Thanks for your contribution! |
…icrosoft#12851) Co-authored-by: Daniel Marshall <[email protected]>
Since boost contains three additional installation function ports(
boost-build
,boost-vcpkg-helpers
,boost-modual-build-helper
), removing all boost components requires the following three steps:./vcpkg remove boost-vcpkg-helpers --recurse
./vcpkg remove boost-modular-build-helper
./vcpkg remove boost-build
Add a port to easily uninstall all boost components using the following command: