[boost] update to 1.87.0 #42678

miyanyan · 2024-12-13T02:34:01Z

Changes comply with the maintainer guide.
SHA512s are updated for each updated download.
The "supports" clause reflects platforms that may be fixed by this new version.
Any fixed CI baseline entries are removed from that file.
Any patches that are no longer applied are deleted from the port's directory.
The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
Only one version is added to each modified port's versions file.

miyanyan · 2024-12-13T02:37:01Z

there's no 1.87.0 release for boost-compatibility, so I keep it as 1.86.0

Cheney-W · 2024-12-13T08:26:07Z

Regarding the boost-build port, it requires manually updating the SHA512 value in the portfile.cmake.

Cheney-W · 2024-12-13T09:43:59Z

Below ports should do the same thing as boost-build.

boost-graph-parallel
boost-mpi
boost-property-map-parallel

The line 31 of scripts/boost/generate-ports.ps1 should be removed.

miyanyan · 2024-12-13T11:17:23Z

Below ports should do the same thing as boost-build.
boost-graph-parallel
boost-mpi
boost-property-map-parallel
The line 31 of scripts/boost/generate-ports.ps1 should be removed.

thanks

miyanyan · 2024-12-14T09:10:59Z

@Cheney-W asio removed some deprecated facilities, see https://www.boost.org/doc/libs/1_87_0/doc/html/boost_asio/history.html, and this caused some ports build failed。

for https://github.com/glynos/cpp-netlib, it has been archived by the owner on Apr 3, 2020, should we still need to support it?

dg0yt · 2024-12-15T06:29:47Z

ports/boost-iostreams/portfile.cmake

 set(FEATURE_OPTIONS "")
 include("${CMAKE_CURRENT_LIST_DIR}/features.cmake")
+if (VCPKG_LIBRARY_LINKAGE STREQUAL "static")
+    list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd_static")


Suggested change

list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd_static")

list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd")

if it is necessary at all. This target is always created.

thanks, I changed to

if (BOOST_IOSTREAMS_ENABLE_ZSTD) list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd") endif()

@dg0yt there's an error when vcpkg install avro-cpp:x64-windows-static:

CMake Error at D:/installed/x64-windows-static/share/boost_iostreams/boost_iostreams-targets.cmake:60 (set_target_properties): The link interface of target "Boost::iostreams" contains: zstd::libzstd but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. Call Stack (most recent call first): D:/installed/x64-windows-static/share/boost_iostreams/boost_iostreams-config.cmake:67 (include) D:/a/_work/1/s/scripts/buildsystems/vcpkg.cmake:859 (_find_package) D:/installed/x64-windows-static/share/boost/BoostConfig.cmake:67 (find_package) D:/installed/x64-windows-static/share/boost/BoostConfig.cmake:128 (boostcfg_find_component) D:/installed/x64-windows-static/share/boost/vcpkg-cmake-wrapper.cmake:3 (_find_package) D:/a/_work/1/s/scripts/buildsystems/vcpkg.cmake:813 (include) D:/downloads/tools/cmake-3.30.1-windows/cmake-3.30.1-windows-i386/share/cmake-3.30/Modules/FindBoost.cmake:610 (find_package) D:/installed/x64-windows-static/share/boost/vcpkg-cmake-wrapper.cmake:3 (_find_package) D:/a/_work/1/s/scripts/buildsystems/vcpkg.cmake:813 (include) CMakeLists.txt:77 (find_package)

config-x64-windows-static-out.log

but if I changed to

if (VCPKG_LIBRARY_LINKAGE STREQUAL "static") list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd_static") endif()

it works well, seems target zstd::libzstd not work when build static?
boost_iostreams-targets.txt
zstdTargets.txt

feliwir · 2025-03-20T11:18:33Z

@ras0219-msft, @AugP, @BillyONeal, and I discussed this today and reached the following outcomes:
* cpp-netlib: Delist.

* websocketpp: Delist.

* freeopcua: Delist.

* quickfast: Delist.

* hazelcast-cpp-client: Delist.

* nghttp2-asio: Delist.
These delistings imply the following delistings as well:
* autobahn

* socket-io-client

* bitserializer

* etcd-cpp-apiv3

* microsoft-signalr

* signalrclient

* tgbot-cpp: They just did a new release 2 days ago, the existing Boost update PR uses the patch upstream already merged so I think we can merge that.

* functions-framework-cpp: The patch is so tiny I think we should just take it.

* hareflow: The patch is so tiny I think we should just take it.

* qwtw: The patch is so tiny and straightforward I think we should just take it.

* cpprestsdk: We can't delist due to high user counts.

* azure-storage-cpp: We can't delist due to high user counts.
@BillyONeal All of these are deprecated or dead.

@ras0219-msft
* we can remove websocket feature in cpprestsdk and change supports for cpprestsdk to avoid the boost dependencies (windows only)
Delisting websocketcpp will break the "websocket" feature in cpprestsdk. That feature should be removed and cpprestsdk's supports expression should be modified to not trigger boost dependencies which should resolve to windows only.

I'd reconsider the WebSocket++ removal, since this breaks many (including our) VCPKG setup

BillyONeal · 2025-03-20T19:43:52Z

@feliwir

I'd reconsider the WebSocket++ removal, since this breaks many (including our) VCPKG setup

Then someone needs to actually maintain WebSocket++. This is not vcpkg's choice: We can't leave Boost out of date forever, and we can't become maintainers for every downstream project that is unmaintained and no longer compiles.

feliwir · 2025-03-20T19:48:47Z

@BillyONeal
WebSocket++ recipe had an option to not link in any dependencies. We were using this anyways since we are not using boost::asio.
I propose making this the default behavior

BillyONeal · 2025-03-20T19:55:19Z

WebSocket++ recipe had an option to not link in any dependencies.

I don't see an obvious way to remove the boost dependency in:

https://github.com/zaphoyd/websocketpp/blob/1b11fd301531e6df35a6107c1e8665b1e77a2d8e/CMakeLists.txt#L176-L245

We have no objection to bringing it back if it can be made to compile. But relying on networking bits which have been unmaintained for 5+ years is probably a bad idea either way.

[A community user raised that the `vcpkg` instructions no longer work](https://hazelcastcommunity.slack.com/archives/C015Q2TUBKL/p1743010446548399). Specifically, `vcpkg` delisted Hazelcast when upgrading to Boost `1.87` - microsoft/vcpkg#42678. As such an version of `vcpkg` must be used that _does_ contain Hazelcast. Tested locally on a fresh environment via Docker: ``` docker run --interactive --tty --rm --platform linux/amd64 ubuntu:latest bash -c "apt-get -y update && apt-get install -y curl git build-essential zip unzip tar pkg-config && git clone https://github.com/microsoft/vcpkg --branch 2025.02.14 && ./vcpkg/bootstrap-vcpkg.sh && ./vcpkg/vcpkg install hazelcast-cpp-client[openssl] --recurse" ``` > Successfully downloaded hazelcast-hazelcast-cpp-client-v5.3.0.tar.gz This is a _workaround_ until the client can be relisted.

Nick7K · 2025-05-22T05:18:16Z

The problem with this unilateral decision is that cpprestsdk relies on websocketpp to provide WebSocket functionality.

cpprestsdk is used by a LOT of vcpkg users.

BillyONeal · 2025-05-22T17:26:44Z

The problem with this unilateral decision is that cpprestsdk relies on websocketpp to provide WebSocket functionality.

It isn't 'unilateral'. A lot more vcpkg customers use boost than use cpprestsdk. Integrity of the registry is more important than any individual thing in the registry.

cpprestsdk is used by a LOT of vcpkg users.

cpprestsdk is effectively unmaintained, and the websockets part is built on websocketspp which has been unmaintained for even longer. vcpkg can't effectively become the new upstream when one of the ~2500 things in the registry decides they don't want to do it any more.

Nick7K · 2025-05-22T17:31:12Z

The problem with this unilateral decision is that cpprestsdk relies on websocketpp to provide WebSocket functionality.

It isn't 'unilateral'. A lot more vcpkg customers use boost than use cpprestsdk. Integrity of the registry is more important than any individual thing in the registry.

cpprestsdk is used by a LOT of vcpkg users.

cpprestsdk is effectively unmaintained, and the websockets part is built on websocketspp which has been unmaintained for even longer. vcpkg can't effectively become the new upstream when one of the ~2500 things in the registry decides they don't want to do it any more.

Fair enough.

I do see websocketpp is being updated - https://github.com/zaphoyd/websocketpp/pull/1164

BillyONeal · 2025-05-22T22:47:43Z

I do see websocketpp is being updated - zaphoyd/websocketpp#1164

Wow, indeed, back from the dead. We would of course love to put this back if it can compile with current Boost.

[A community user raised that the `vcpkg` instructions no longer work](https://hazelcastcommunity.slack.com/archives/C015Q2TUBKL/p1743010446548399). Specifically, `vcpkg` delisted Hazelcast when upgrading to Boost `1.87` - microsoft/vcpkg#42678. As such an version of `vcpkg` must be used that _does_ contain Hazelcast. Tested locally on a fresh environment via Docker: ``` docker run --interactive --tty --rm --platform linux/amd64 ubuntu:latest bash -c "apt-get -y update && apt-get install -y curl git build-essential zip unzip tar pkg-config && git clone https://github.com/microsoft/vcpkg --branch 2025.02.14 && ./vcpkg/bootstrap-vcpkg.sh && ./vcpkg/vcpkg install hazelcast-cpp-client[openssl] --recurse" ``` > Successfully downloaded hazelcast-hazelcast-cpp-client-v5.3.0.tar.gz This is a _workaround_ until the client can be relisted.

reitowo · 2025-05-26T10:36:50Z

Why websocketpp is removed from vcpkg?

BillyONeal · 2025-05-27T23:45:59Z

Why websocketpp is removed from vcpkg?

Because it can't be built with current versions of Boost. It's effectively unmaintained at this point. If upstream would fix it to build with current Boost we would put it back.

reitowo · 2025-05-28T02:08:21Z

Oh, ok. I just want to say I was using it in manifest mode, after updating baseline in vcpkg.json, it just throw a git error that says invalid tree object or something, not very clear, spent some time debugging it.

BillyONeal · 2025-05-29T23:26:36Z

Oh, ok. I just want to say I was using it in manifest mode, after updating baseline in vcpkg.json, it just throw a git error that says invalid tree object or something, not very clear, spent some time debugging it.

Improving the error message is a reasonable issue to report if you have a repro

reitowo · 2025-05-31T06:56:18Z

Here's a repro: #45778 (Not sure if it is duplicated to any existing issue)

miyanyan added 3 commits December 13, 2024 10:27

[boost] update to 1.87.0

cf7d102

[boost-build] remove port-version

0528dc1

[boost] update versions

2c0933a

MonicaLiu0311 assigned Cheney-W Dec 13, 2024

Cheney-W added the category:port-update The issue is with a library, which is requesting update new revision label Dec 13, 2024

miyanyan added 2 commits December 13, 2024 10:58

[boost] add boost-parser

ead9f37

[boost] update versions

9ffae9c

MonicaLiu0311 mentioned this pull request Dec 13, 2024

[Boost] update to <1.87.0> #42666

Closed

Cheney-W marked this pull request as draft December 13, 2024 09:44

[boost-build] update hash

6faac32

miyanyan added 3 commits December 13, 2024 19:25

Update generate-ports.ps1

a62fd37

[boost] update mpi hash

9dfd371

[boost] update mpi versions

e2ea7a1

miyanyan added 7 commits December 14, 2024 17:16

[cpp-netlib] fix asio build error

358df85

[websocketpp] fix asio build error

d873cdd

Update use-asio-iocontext.patch

55cb7f1

[freeopcua] fix asio build error

b65b400

update versions

82ace77

[boost-iostreams] fix zstd build error when static

72aa707

[boost] update versions

d3a2deb

dg0yt reviewed Dec 15, 2024

View reviewed changes

miyanyan added 4 commits December 15, 2024 18:27

[boost-iostreams] update portfile.cmake

6bb6664

[wt] fix asio build error

5133034

update versions

f468110

[cpp-netlib] fix asio build error

28e1d7e

miyanyan mentioned this pull request Mar 30, 2025

[New Port Request] <websocketpp> #44640

Closed

Mengna-Li mentioned this pull request Apr 1, 2025

[<websocketpp>] <The library port is not available in ports of vcpkg > #44729

Closed

mprather mentioned this pull request Apr 5, 2025

Roadmap for SignalR-Client-Cpp project dotnet/aspnetcore#61342

Closed

JackPGreen mentioned this pull request Apr 10, 2025

Update vcpkg instructions hazelcast/hazelcast-cpp-client#1272

Merged

LilyWangLL mentioned this pull request Apr 11, 2025

[websocketpp] Add new port #44973

Closed

11 tasks

miyanyan mentioned this pull request Apr 13, 2025

[asio] Updates asio to 1.32.4 #44969

Closed

17 tasks

reitowo mentioned this pull request May 31, 2025

Removal of a vcpkg port fails manifest configuration when using builtin-baseline after removal commit. #45778

Open

cricri32 mentioned this pull request Jul 2, 2025

Compatibility fixes for Boost 1.87 zaphoyd/websocketpp#1164

Open

maisonsmd mentioned this pull request Aug 3, 2025

[New Port Request] Socket.IO Client #44899

Closed

BillyONeal mentioned this pull request Nov 3, 2025

[hazelcast-cpp-client] Add new port #48090

Merged

11 tasks

miyanyan deleted the boost-1.87.0 branch November 21, 2025 03:16

	list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd_static")
	list(APPEND FEATURE_OPTIONS "-DBOOST_IOSTREAMS_ZSTD_TARGET=zstd::libzstd")

[boost] update to 1.87.0 #42678

[boost] update to 1.87.0 #42678

Uh oh!

Conversation

miyanyan commented Dec 13, 2024

Uh oh!

miyanyan commented Dec 13, 2024

Uh oh!

Cheney-W commented Dec 13, 2024

Uh oh!

Cheney-W commented Dec 13, 2024

Uh oh!

miyanyan commented Dec 13, 2024

Uh oh!

miyanyan commented Dec 14, 2024

Uh oh!

dg0yt Dec 15, 2024

Choose a reason for hiding this comment

Uh oh!

miyanyan Dec 15, 2024

Choose a reason for hiding this comment

Uh oh!

miyanyan Dec 22, 2024

Choose a reason for hiding this comment

Uh oh!

feliwir commented Mar 20, 2025

Uh oh!

BillyONeal commented Mar 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

feliwir commented Mar 20, 2025

Uh oh!

BillyONeal commented Mar 20, 2025

Uh oh!

Nick7K commented May 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BillyONeal commented May 22, 2025

Uh oh!

Nick7K commented May 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BillyONeal commented May 22, 2025

Uh oh!

reitowo commented May 26, 2025

Uh oh!

BillyONeal commented May 27, 2025

Uh oh!

reitowo commented May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BillyONeal commented May 29, 2025

Uh oh!

reitowo commented May 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

BillyONeal commented Mar 20, 2025 •

edited

Loading

Nick7K commented May 22, 2025 •

edited

Loading

Nick7K commented May 22, 2025 •

edited

Loading

reitowo commented May 28, 2025 •

edited

Loading

reitowo commented May 31, 2025 •

edited

Loading